REST API
List a subscription's matches
What a subscription did, newest first: each matched event with its state, suppressed_reason, enrichment status, and every delivery attempt.
GET
/v1/subscriptions/:subscription_id/matchesParameters
subscription_idstringrequiredstate"matched" | "enriching" | "ready" | "delivered" | "suppressed" | "budget_exceeded" | "failed" | "cancelled"optionalsincestringoptionalISO date-time: matches created after it
cursorstringoptionallimitintegeroptionaldefault 50 (min 1, max 500)
What your agent reads
The tool description exactly as an MCP client receives it in tools/list — it doubles as the full behaviour of the endpoint.
What a subscription did, newest first: each matched event with its state (matched → enriching → ready → delivered | suppressed | budget_exceeded | failed | cancelled), suppressed_reason (dedupe, daily_limit, budget, repost), enrichment status, and every delivery attempt (http_status, latency, the receiver's response excerpt, error_code). No record cost. Filter by state or `since` (created after); page with cursor.
Over REST, parameters go in the query string.
Errors follow one format.