Skip to main content
POST
Resolve a gap or create an owner-reviewed improvement

Authorizations

Authorization
string
header
required

A Contact Button scoped bearer key. Send Authorization: Bearer <token>. Token abilities are enforced independently of workspace membership; both checks must pass. REST requires a Sanctum API key. Separately, interactive MCP clients can use registered OAuth applications with PKCE and audience-bound workspace grants; those tokens are not REST credentials.

Headers

Idempotency-Key
string

Optional 8–120 character key for replayable mutations. Send the exact same method, URI, and body on retries; receipts expire after 24 hours.

Required string length: 8 - 120

Path Parameters

workspace
string<uuid>
required
agent
string<uuid>
required
gap
string<uuid>
required

Stable knowledge-gap public ID.

Body

application/json
action
enum<string>
required
Available options:
add_q_and_a,
add_knowledge,
add_rule,
dismiss,
mark_resolved
title
string | null
Maximum string length: 160
content
string | null

Required for Q&A, knowledge, and rule drafts. It is never published or enabled automatically. Q&A creates a draft FAQ Question; the gap stays open until it is published or reviewed.

Maximum string length: 10000

Response

Successful data envelope.

data
any
required
meta
object
required