Skip to main content
Quotable sends one event type. Every delivery wraps its data in the same envelope; the examples below show the full body your endpoint receives. Fetching the record behind resource.href requires an API key with the read:projects scope.
Older endpoints may still list article.published, article.publish_failed or content.run.finished among their events. Quotable no longer sends these, so you can ignore them.

tracking.run.finalized

Sent when a day’s tracking for a brand has been scored and the results are visible in the app and the API.
The values match the score and mention_rate for the same date in GET /projects/{project_id}/visibility. Call that endpoint for share of voice and the rest of the series.
A run can be scored more than once, for example when late answers arrive and the day is re-scored. Each event carries the latest values, so store them keyed by project_id and run_date and let a newer event overwrite an older one.

Payload versioning

schema_version is 1 for every event. It changes only for an incompatible change to an event’s payload. New fields can be added to data or the envelope at any time without a version change, so ignore fields you don’t recognize.

Next steps

Verify signatures

Prove each delivery came from Quotable before you act on it.

Delivery and retries

Retry schedule, ordering and deduplication.
Last modified on November 18, 2026