Integrations

Later Influence

Connect Later Influence to pull read-only influencer marketing reports on campaign, creator, and post performance.

API credentialsPartner applicationAds & SocialLater Influence API docs

You paste a clientId and clientSecret that Later issues by hand for the Later Influence Reporting API. There is no self-serve console.

Partner application before this connector works

Later's own team must provision Reporting API credentials for your Later Influence instance; there is no self-serve console that issues a clientId/clientSecret.

Typical wait
not published
Cost
Not published. Later documents no separate API fee, and states no pricing or plan requirement for Reporting API access — confirm commercial terms with your Later account team.
Blocked until approved
Everything. The Reporting API is JWT-based: you exchange a clientId and clientSecret for a bearer token, and Later only hands those out on request, so no endpoint (instances, campaigns, platforms, creators, posts) can be called until they arrive.
Works meanwhile
You can read the public docs at docs.reporting.api.later.com and build/test your client against the documented request and response shapes, but no live call will authenticate.

Where to apply: Ask your Later account team, or email the contact named in the Getting Started page of docs.reporting.api.later.com with the subject line 'Reporting API access'. There is no form or developer portal.

  • There is no self-serve signup — a support ticket in the general Later help centre is slower than going through your named account manager.
  • This is the Later Influence (formerly Mavrck) reporting API, not the Later social scheduling product; asking the wrong team wastes days.
  • Multi-instance access (aggregating several Later Influence instances) must be requested explicitly when credentials are issued.
  • Later does not publish a turnaround SLA, so budget for a human email round-trip rather than same-day access.
Setup time
10 min of work, plus a few business days for Later to provision the client
Auth
API credentials
API base URL
https://reporting.api.later.com/v2
Rate limits
120 requests per minute per IP. Over the limit returns 429, and every response carries X-Ratelimit-Limit and X-Ratelimit-Window headers.

Before you begin

  • A Later Influence subscription, formerly Mavrck. The Reporting API does not exist for Later Social scheduling plans
  • A named Later account manager or CSM to raise the request with
  • Reporting API access enabled on your contract. Credentials are issued manually, not generated in-app
  • Read-only expectations. The API reports on campaigns, creators and posts and cannot publish or schedule

Get your credentials

Check that you are on Later Influence

Later's only public API is the read-only Later Influence Reporting API, which returns campaign, creator and post analytics. Confirm your plan with your account team before going further.

Open this screen →

Ask Later for Reporting API access

Email your Later account team, or urvash.chheda@later.com, with the subject Reporting API access. Later provisions an OAuth client by hand and sends back a clientId and a clientSecret.

Open this screen →

docs.reporting.api.later.com/getting-started
Search documentationLater Influence
Reporting API / Getting started

Getting started

Query influencer campaign, creator and post performance from your own systems.

Access is granted by Later. Request credentials through your account team.
What Later sends back
clientId
lat_cid_****7b19
clientSecret
lat_sec_****c204
Instances
3 workspaces

No button anywhere in the Later app mints these values.

Name every instance the client should cover

Tell Later which instances, meaning your Later Influence workspaces, PopMCP should read. List all of them in the same email.

Open this screen →

Test the pair against the token endpoint

POST the clientId and clientSecret as JSON to https://reporting.api.later.com/oauth/token from a terminal. A working pair returns \{ "jwt": "..." \}.

Open this screen →

docs.reporting.api.later.com/authentication
Search documentationLater Influence
Reporting API / Authentication

Authentication

Exchange your client credentials for a short lived JWT.

cURLNodePython
POST /oauth/token
URL
https://reporting.api.later.com/oauth/token
clientId
lat_cid_****7b19
clientSecret
lat_sec_****c204
Send
200 response
jwt
eyJhbGciOi****9f2c
Valid for
12 hours
Header
Authorization: Bearer <jwt>
StatusTypeMeaning
401ANL_00401Invalid, malformed or expired JWT
403ANL_00403Client disabled, or instance outside your set

Run this from a server or terminal. The API sends no CORS headers.

Paste the pair into PopMCP

Put the values in Client ID and Client secret, then click connect.

Connect in PopMCP

Open your workspace, choose Later Influence in the marketplace, and fill in the connect dialog:

FieldWhat to enter
Connection typepresetLater's only public API is the read-only Later Influence Reporting API. It reports on campaign/creator/post analytics; it cannot post or schedule.
Client IDtextIssued by Later alongside your clientSecret. Request Reporting API access from your Later account manager or urvash.chheda@later.com.
Client secretsecretThe secret paired with your clientId. Stored encrypted; used server-side only to mint short-lived Bearer tokens.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against Later Influence immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

PopMCP marks Later Influence as Connected and the instance list populates. The first call it makes is GET https://reporting.api.later.com/v2/instances with a freshly minted JWT.

Troubleshooting

401 with type ANL_00401

Why: The JWT is invalid, malformed or expired. Tokens last 12 hours.

Fix: Re-authenticate against /oauth/token. If it fails immediately after saving, the clientId and clientSecret pair is wrong, so ask Later to re-issue.

403 with type ANL_00403

Why: The credentials are valid but the client is disabled, has no accessible instances, or you asked for an instance outside its set.

Fix: Contact your Later account team to enable the client or add the missing instances to it. Instances cannot be added from the Later app.

403 on /oauth/token plus a CORS policy or Failed to fetch error

Why: The call was made from a browser. The Reporting API is server-side only and sends no CORS headers.

Fix: Test with curl or a backend HTTP client. This is expected behaviour, not an outage.

429 Too Many Requests

Why: More than 120 requests from one IP in a 60-second window.

Fix: Back off exponentially. The X-Ratelimit-Limit and X-Ratelimit-Window headers on every response tell you where you stand.

You expected to schedule or publish posts

Why: The Reporting API is read-only analytics for Later Influence. Later Social scheduling has no public API.

Fix: Use the Later app for scheduling. PopMCP can only read reporting data.

Reference

On this page