Hey guys!
We're building an OAuth integration that uses the Reporting API for campaign and flow performance data. We ran into a not_found error when hitting the reporting endpoints, and wanted to flag a potential source of confusion in the docs.
The issue: The Reporting API overview correctly shows endpoints under the {entity}-values-reports pattern (e.g., /api/campaign-values-reports/). However, some naming in the Reporting reference and the Custom Metrics API overview could lead integrators to infer a /api/reporting/campaign-values/ structure instead.
The correct working endpoints are:
POST /api/campaign-values-reports/(type:campaign-values-report)POST /api/flow-values-reports/(type:flow-values-report)POST /api/form-values-reports/(type:form-values-report)POST /api/segment-values-reports/(type:segment-values-report)
And the corresponding series endpoints:
POST /api/campaign-series-reports/POST /api/flow-series-reports/POST /api/form-series-reports/POST /api/segment-series-reports/
We initially used /api/reporting/campaign-values/ with type reporting-campaign-values, which returned a not_found error. Once corrected to /api/campaign-values-reports/ with type campaign-values-report, everything worked as expected.
We're using API revision 2026-01-15 with OAuth (PKCE).
Question: Was there a revision where the endpoint naming convention changed? If so, a note in the changelog or migration docs would help other integrators avoid this pitfall.
Thanks!
