Changelog
Partner API versions, how versioning works, and how we announce deprecations.
Versioning
All endpoints live under /v1. Changes within v1 only add things. New optional fields, parameters, endpoints, and error codes can appear without notice. So can new values in fields the reference marks as open-ended, such as scopes. Build your client so that it:
- ignores response fields it does not recognize;
- handles an unknown error code by its HTTP status;
- does not depend on the order of fields, or on the order of rows beyond what the docs state.
Breaking changes ship only under a new version path. Before an old version stops working, we post a deprecation timeline here and contact every organization with active tokens.
v1.0.0 (private preview)
First release. Access is turned on per organization.
GET /v1/pingchecks a token.GET /v1/reports/revenuereturns daily gross and net revenue for each publisher, with its primary domain andis_final.- Scope:
reporting:read. - The OpenAPI spec at /openapi/partner-api.yaml.