Search policy entries
GET /api/workspaces/{workspaceId}/policy-entries/search
Performs a full-text search across policy entries in a workspace. Searches against topic and rule text. An empty query returns no results.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace to search within.
Query Parameters
Section titled “Query Parameters ”Search query to match against policy content.
Example
discountResponses
Section titled “ Responses ”Policy entries matching the search query.
List of policy entries.
A policy entry defines a rule that governs how the AI should behave in specific situations. Unlike KB entries (which provide factual answers), policies specify constraints, guardrails, and behavioral guidelines. For example, ‘Never offer more than 10% discount without manager approval’ or ‘Always ask for an order number before looking up shipping status’. Policies can be created manually or proposed by the learning loop.
object
Unique identifier for the policy entry.
Example
pe1a2b3c-5678-9abc-def0-1234567890abThe tenant this policy belongs to.
Example
a0b1c2d3-4567-89ab-cdef-0123456789abThe workspace this policy is scoped to.
Example
w1a2b3c4-5678-9abc-def0-1234567890abThe topic or domain this policy applies to. Used by the AI to determine which policies are relevant to the current conversation.
Example
discount_authorizationThe policy rule in natural language. This is the instruction the AI follows.
Example
Never offer a discount above 10% without creating an attention item for manager approval. For discounts up to 10%, apply automatically if the customer has placed 3 or more orders.Optional structured conditions that qualify when this policy applies. Can include time-based, value-based, or context-based conditions.
Example
{ "min_order_value": 500, "customer_tier": "gold"}How this policy was created. ‘manual’ means created by a human, ‘learning_loop’ means proposed by the AI after analyzing resolved conversations.
Example
manualConfidence score between 0 and 1, set by the learning loop when proposing policies. Null for manually created policies.
Example
0.85Lifecycle status. Same semantics as KB entry status — only ‘approved’ policies are enforced by the AI.
Example
approvedTimestamp when the policy was created.
Example
2026-02-05T09:00:00.000ZTimestamp when the policy was last updated.
Example
2026-03-18T11:30:00.000Z