Error
A valid request URL is required to generate request examples{
"success": true,
"data": [
{
"conversationId": "conv_9d2f01",
"queryText": "Can I get a Saturday appointment?",
"occurredAt": "2026-07-11T18:04:00.000Z",
"channel": "voice",
"agentId": "agt_4f9c2b7e10a24d51",
"callerNumber": "+14155550142"
}
],
"pagination": {
"page": 1,
"limit": 20,
"total": 1,
"totalPages": 1
}
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}Observe
The exact moments behind a knowledge gap (M4 drill)
The raw unanswered_queries rows folded into a clustered gap (knowledge_gap_id = gapId), newest-first — each carrying the verbatim failing query, when it happened, and the conversation it lives in. This is the data-correct gap drill: the occurrences are PRECISELY linked, so the UI opens the real transcripts behind the gap instead of a phrase search that never matches a caller’s verbatim wording. 404 if the agent or gap is absent/cross-org.
GET
/
agents
/
{agentId}
/
knowledge-gaps
/
{gapId}
/
occurrences
Error
A valid request URL is required to generate request examples{
"success": true,
"data": [
{
"conversationId": "conv_9d2f01",
"queryText": "Can I get a Saturday appointment?",
"occurredAt": "2026-07-11T18:04:00.000Z",
"channel": "voice",
"agentId": "agt_4f9c2b7e10a24d51",
"callerNumber": "+14155550142"
}
],
"pagination": {
"page": 1,
"limit": 20,
"total": 1,
"totalPages": 1
}
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.