Changelog

2026-10-07 — Unsupported media type errors

• POST /oauth/token now documents HTTP 415 (ANL_00415) when the request Content-Type is not application/json. Send credentials as JSON.

2026-09-10 — New reach metrics and clearer authentication errors

• organicReach is now available alongside reach and paidReach, so organic and paid reach can be separated in the same request. Supported on /v2/instances/performance, /v2/instances/performance-over-time, /v2/campaigns/performance, /v2/platforms/performance, /v2/creators/performance, and /v2/posts/performance — and as a sortProperty on the campaigns, platforms, creators, and posts endpoints.
• paidReach is now also available on /v2/instances/performance, joining the campaigns, platforms, creators, posts, and performance-over-time endpoints that already supported it.
• followersAtPostDate can be requested and sorted on for /v2/posts/performance, giving the follower count at the time each post was published.
• POST /oauth/token now returns 401 for any incorrect credentials. Previously some requests with an incorrect clientSecret returned 403. A 403 now always means your credentials were accepted but the client is not permitted.
• Server-side failures return 500 instead of 401, so a transient outage is no longer mistaken for an authentication problem.
• Documentation: Errors & troubleshooting now lists every error code and explains the three causes behind a 403.

All metric additions are additive — existing requests continue to work unchanged, and no changes are required for clients that authenticate successfully.

Already used older versions of Reporting API?

See Migration from old versions for a route-by-route map and suggested cutover steps.

Related pages

• Migration from old versions
• API Reference