Changelog

What is new in Reporting API v2 and this documentation site.


Reporting API v2

Added

  • New endpoint: GET /v2/campaigns — lightweight campaign list with metadata
  • New filters: platformTypes and dateBasis (performance_date | post_date)
  • Paid metrics across all performance endpoints (e.g. paidEngagements, paidImpressions, paidCpe, etc.)
  • Response includes totalItems count in pagination

Updated

  • API host name: https://reporting.api.later.com
  • API routes updated for RESTful consistency (plural resource names, e.g. */network/* to */networks/*)
  • Response envelope: standardized { data, pagination } wrapper
  • Clean IDs: responses only expose public identifiers (instanceId, campaignId, creatorId, postId)
  • Error handling: application/problem+json (RFC 9457) with type, title, and detail

Removed

  • instance/details and instances/details endpoints (use GET /v2/instances instead)
  • reportingGroupIds parameter
  • metrics selection parameter on creators and posts endpoints (V2 always returns all metrics)

Unchanged

  • Authentication flow (OAuth client credentials)
  • Pagination parameters (pageSize, pageNumber)
  • Sorting parameters (sortProperty, sortDirection)

Start at Getting started, then use the API Reference as the source of truth for parameters and response schemas.


Already on Reporting API v1?

v2 uses new paths, response shapes, and error formats. Use Migration from v1 for a route-by-route map and suggested cutover steps. v1 OpenAPI remains available on SwaggerHub and from your environment (for example swagger.later.com/reporting-api or your deployment’s v1 Swagger URL).