Interactions
Ingested comments/mentions on the org's content (keyset paginated)
GET
/interactionsAuthorization
bearerAuth AuthorizationBearer <token>
In: header
Query Parameters
kinds?string
channel?string
since?string
cursor?string
limit?integer
Range
1 <= value <= 100Default
20organization?string
Organization slug (OAuth actors with several orgs); API keys imply theirs.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/interactions"{ "items": [ { "property1": null, "property2": null } ], "next_cursor": "string"}{ "error": { "code": "string", "message": "string", "reason": "string", "index": 0, "request_id": "string" }}{ "error": { "code": "string", "message": "string", "reason": "string", "index": 0, "request_id": "string" }}Account-growth report scoped to one channel GET
Previous Page
Reply to an ingested comment or mention POST
Posts a reply under the interaction, as the channel it arrived on. Threading is derived from the stored interaction (its parent is the thread root), so no channel or external id is needed. Costs 1 Ink. Not every provider offers a comment API: read `capabilities.ingestion` on the channel first — false means a reply is impossible there, and this refuses naming the provider.