Implement the Reporting API for Later Influence

The Later Influence Reporting API provides programmatic access to campaign performance data, creator metrics, and social media analytics, allowing you to pull it into  reporting tools like Looker, Microsoft BI, Oracle Analytics Cloud, SAP Analytics Cloud, Tableau, and more. 

Authentication

Authentication is handled via JWT (JSON Web Tokens). To make API requests, your developer exchanges a clientId and clientSecret for a temporary access token. That token is then  passed as a Bearer token on all API requests to prove authorization.

Step 1 - Generate an Access Token

curl -sS -X POST "https://reporting.api.later.com/oauth/token" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "<YOUR_CLIENT_ID>",
    "clientSecret": "<YOUR_CLIENT_SECRET>"
  }'

Response:

{
  "jwt": "<JWT>"
}

Use the returned jwt value as Authorization: Bearer <jwt> on all subsequent requests.

Tokens expire after 24 hours. Your app should request a new token before expiry, or when it receives a 401 Unauthorized response.

Token error codes:

Usage & Examples

The v2 Reporting API is organized around a data hierarchy: Instance → Campaign → Platform / Creator / Post. Use the table below to find the endpoint that matches the level of granularity your reporting needs.

Which Endpoint Should I Use?

Example 1 - List Instances

Every request to a performance endpoint requires at least one instanceId. Use this call to retrieve the IDs associated with your credentials.

curl -sS -G "https://reporting.api.later.com/v2/instances" \
  -H "Authorization: Bearer <JWT>" \
  --data-urlencode "pageNumber=1" \
  --data-urlencode "pageSize=50"

{
  "data": {
    "instanceIds": ["instance_abc", "instance_def"]
  },
  "pagination": {
    "page": 1,
    "pageSize": 50,
    "totalPages": 1,
    "totalItems": 2
  }
}

Example 2 - Campaign Performance

Retrieve campaign-level metrics sorted by estimated ROI.

curl -sS -G "https://reporting.api.later.com/v2/campaigns/performance" \
  -H "Authorization: Bearer <JWT>" \
  --data-urlencode "startDate=2025-01-01" \
  --data-urlencode "endDate=2025-01-31" \
  --data-urlencode "instanceIds=<YOUR_INSTANCE_ID>" \
  --data-urlencode "pageNumber=1" \
  --data-urlencode "pageSize=10" \
  --data-urlencode "sortProperty=estimatedRoi" \
  --data-urlencode "sortDirection=DESC"

Example 3 - Creator Performance

Retrieve individual creator metrics within a date range.

curl -sS -G "https://reporting.api.later.com/v2/creators/performance" \
  -H "Authorization: Bearer <JWT>" \
  --data-urlencode "startDate=2025-01-01" \
  --data-urlencode "endDate=2025-01-31" \
  --data-urlencode "instanceIds=<YOUR_INSTANCE_ID>"

Example 4 - Paid Media Metrics

Paid metrics are available on the campaigns/performance, platforms/performance, and posts/performance endpoints. Look for fields with the paid prefix:

Migration from v1

If your team currently uses the legacy Mavrck API (api.mavrck.co), use this section to plan your migration to v2. 

Base URL Change

Route-by-Route Mapping

What to Update in Your Implementation

1. Update the base URL from api.mavrck.co to reporting.api.later.com
2. Replace all v1 route paths with their v2 equivalents (see table above)
3. Update response parsing - v2 returns a structured envelope: { "data": {}, "pagination": {} }
4. Remove reporting-group logic - this concept is replaced by campaign and platform filtering in v2
5. Add new fields to your pipeline - paid metrics (paidImpressions, paidCpm, etc.), creator data, and post-level data are all new and available immediately after migration

Reporting Options

The v2 API offers significantly more flexibility than v1 for filtering, grouping, and querying data.

Date filtering: Set startDate and endDate on any performance endpoint. Switch between dateBasis=performanceDate (when the metric was recorded) and dateBasis=postDate (when the content was published) to control how dates are applied.

Time-series granularity: Use GET /v2/instances/performance-over-time with a granularity parameter set to day, week, month, quarter, or year.

Multi-instance support: Pass multiple instanceIds values to aggregate data across several Later Influence workspaces in one call. Omit instanceIds entirely to return data across all instances your credentials have access to.

Sorting and pagination: All list endpoints support sortProperty, sortDirection, pageNumber, and pageSize for full control over result ordering and volume.

Platform filtering: Filter results by social platform (Instagram, TikTok, YouTube, Facebook, and more) on most performance endpoints.

Paid vs. organic: Organic metrics use plain field names (impressions, engagements). Paid metrics always use the paid prefix (paidImpressions, paidEngagementRate).

API Documentation

The full v2 Reporting API documentation is available at:

docs.reporting.api.later.com

The interactive API Reference - with live request examples, full parameter details, and downloadable OpenAPI specs - is at:

docs.reporting.api.later.com/api-reference