# Apify setup for PopMCP

You end up with one Apify API token that starts with `apify_api_`. Paste it into PopMCP's API token field.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.apify.com/v2
- Credentials screen: https://console.apify.com/settings/integrations
- Provider docs: https://docs.apify.com/api/v2

## Before you begin

- An Apify account. The free plan is enough to mint a token.
- If your Actors belong to an Apify organisation, switch to that account in the Console first. Tokens are per account, so a personal token cannot see organisation Actors.
- Owner access, or the Manage access tokens permission, on an organisation account.

## Get your credentials

### 1. Open Settings, then API & Integrations

Sign in at console.apify.com and click Settings at the foot of the left sidebar. Open the API & Integrations tab.

Screen: https://console.apify.com/settings/integrations

### 2. Create a token for PopMCP

Click Create new token and name it `PopMCP`. Leave Limit token permissions switched off and click Save.

Screen: https://console.apify.com/settings/integrations

### 3. Copy the token value

Click the copy icon next to the new token to copy the full `apify_api_…` string.

### 4. Paste it into PopMCP

In PopMCP, paste the value into API token and save.

## Fields PopMCP asks for

- API token (apiToken) [required]: In the Apify Console open Settings → Integrations (https://console.apify.com/settings/integrations) and copy your Personal API token. It's sent as the Authorization: Bearer header and stored encrypted; used server-side only. No OAuth app or client secret is required.

## Verify

PopMCP's Apify connector shows Connected with your account username, and listing your Actors returns the same ones you see in the Console.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The token was truncated on paste, or it was rotated or expired in the Console.

Fix: Open Settings, then API & Integrations, create a fresh token, and paste the whole apify_api_ string with no surrounding spaces.

### You cannot find the token value again

Cause: Apify shows the complete value at creation and masks it in the list afterwards.

Fix: Delete the token and create a replacement rather than guessing at a partial value.

### 403 Forbidden on one Actor or dataset

Cause: Limit token permissions is on and the scope does not cover that resource.

Fix: Edit the token to include the Actor and its default dataset, or replace it with a full-access token.

### The connector works but sees none of your team's Actors

Cause: The token belongs to your personal account rather than the organisation.

Fix: Switch to the organisation in the Console account switcher, then mint the token from that account's API & Integrations tab.

### 429 Too Many Requests

Cause: More than 60 requests per second against a single resource, or many parallel runs.

Fix: Retry with exponential backoff. The limit applies per resource, not per token.

---

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