Changelog

v1, 2026-09-24

The first version of the EzyInsights Detections API.

Endpoints

• GET /v1/detections/changes: the change stream, every new and changed detection in the order it arrived, from a cursor or from since (at most 31 days ago).
• GET /v1/detections: the current state of the detections first detected in a period of at most 31 days, with filters and a query cursor.
• GET /v1/detections/{id}: one detection, latest version.
• GET /v1/me: the key, its account and subscriptions, where data starts, export gaps and limits.
• GET /v1/schema/detection: the v1 detection, machine-readable (also HEAD).
• POST /oauth/token: access tokens with OAuth 2.0 client credentials.
• GET /v1/health: whether the data is current (also HEAD).

The detection schema v1, for text (wire stories) and images (photos): identity and version, source (the agency's item), strength (score and band), article (the publisher article and publisher), and customer and classification, which are null in this version. Every field is listed in the reference and at GET /v1/schema/detection.

Limits: 120 requests a minute per key, and a daily row allowance per account.

Deprecation policy (proposed)

Adding endpoints, parameters or fields is not a breaking change: it is announced here and made in place, so clients should ignore fields they do not know. Renaming or removing anything, or changing what it means, is a breaking change: it will come as a new version (a new detection schema_version, or a new URL version), announced here with 12 months' notice, during which answers from the old version carry Deprecation and Sunset headers. This policy is still a proposal and will be confirmed here.