Smart Search
Natural-language traffic-log search. The platform's AI gateway translates a free-form query ("5xx errors from mobile clients in the last hour") into a structured traffic-log filter, runs it, and returns the matching logs. The response is the same shape as GET /v1/traffic/logs — the AI only chooses the filter; the result set is the ordinary, paginated log list.
Plan-gated: requires the traffic_inspector entitlement and the traffic-inspector read permission. Strict JSON decoding — only query is allowed in the body; any unknown field is rejected.
If the AI can't translate your wording into an actionable filter, the call returns 400 ("Smart search could not understand the request"). Refine your wording or use the structured /traffic/logs endpoint instead.
Request body
Query parameters
?endpoint_uuid= limits it to one endpoint.Deprecated: endpoint_id, rate_limit_rule_id and since_id (integers) and policy_id are still accepted until the sunset. Send endpoint_uuid, rate_limit_rule_uuid, since_uuid and policy_uuid; sending both forms for different objects is a 400 id_uuid_mismatch.
Response (200 OK)
Identical to GET /v1/traffic/logs: the AI-derived filter is applied server-side and the matching page of logs is returned.
logs is an alias of items kept for backward compatibility — they are the same list.{page, page_size, total} — the same numbers nested for clients that read the object form.Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.
Errors
query, unknown body fields (strict decoding), the AI couldn't translate the query into actionable filters, a malformed *_uuid filter, id_uuid_mismatch, or an integer id after the sunset (integer_id_unsupported).traffic_inspector entitlement, or the member lacks traffic-inspector read permission.