Reference
API stability
Endpoint stability communicates compatibility expectations for the public API surface.
Stability levels
Stable endpoints are the default public contract and receive compatible changes within API v1. For endpoints marked Contract may change, review request and response changes before upgrading your integration.
Advanced endpoints are public for integrations that need lower-level control, but they are not the default onboarding path and require closer review when upgrading.
Current endpoint status
This table is generated from the canonical API endpoint model.
| Endpoint | Status |
|---|---|
| POST /v1/browser/activate | stable |
| POST /v1/placements | stable |
| POST /v1/jobs | advanced |
| GET /v1/decisions/{slot_id} | advanced |
| GET /v1/render.js | stable |
| GET /v1/render/{asset_token} | stable |
| POST /v1/beacons | stable |
| POST /v1/consent | Contract may change |
| GET /v1/projects/{client_id}/config | stable |
Changes and versioning
API v1 itself is stable; no version 2 exists today. Compatibility and change-announcement practice are documented on the versioning page.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.