# Later Influence setup for PopMCP

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

- Auth: API credentials
- Setup time: 10 min of work, plus a few business days for Later to provision the client
- API base URL: https://reporting.api.later.com/v2
- Credentials screen: https://docs.reporting.api.later.com/getting-started
- Provider docs: https://docs.reporting.api.later.com/getting-started

## Approval required before this 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.

## 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

### 1. 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.

Screen: https://docs.reporting.api.later.com/getting-started

### 2. 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`.

Screen: https://docs.reporting.api.later.com/getting-started

### 3. 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.

Screen: https://docs.reporting.api.later.com/authentication

### 4. 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": "..." }`.

Screen: https://docs.reporting.api.later.com/authentication

### 5. Paste the pair into PopMCP

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

## Fields PopMCP asks for

- Connection type (connectionType): Later'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 ID (clientId) [required]: Issued by Later alongside your clientSecret. Request Reporting API access from your Later account manager or urvash.chheda@later.com.
- Client secret (clientSecret) [required]: The secret paired with your clientId. Stored encrypted; used server-side only to mint short-lived Bearer tokens.

## Verify

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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/later/