# SendFox setup for PopMCP

A SendFox personal access token created under Settings > Connections > API tokens, shown once, pasted into PopMCP's Personal access token field.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.sendfox.com
- Credentials screen: https://sendfox.com/account/oauth
- Provider docs: https://help.sendfox.com/category/270-api-integrations

## Approval required before this works

SendFox only issues personal access tokens on a paid plan; sendfox.com/pricing lists the Free plan as 'No API access' and the paid Lifetime and Pro plans as 'Full API access'. There is no application and no review.

- Typical wait: Instant once on a paid plan. There is no review, no application and no developer programme.
- Cost: Any paid SendFox plan qualifies — the one-time Lifetime deal or a Pro subscription. Check sendfox.com/pricing for the current amounts; the Free plan is listed there as 'No API access'.
- Blocked until approved: On the Free plan the API tokens page shows an upgrade prompt instead of the token tools, so no token exists and no endpoint (contacts, lists, campaigns) is reachable.
- Works meanwhile: The API surface is small and fully documented publicly at help.sendfox.com, so requests and payloads can be written against the docs before upgrading.

## Before you begin

- A paid SendFox plan. The API answers HTTP 402 on free accounts.
- Login to the SendFox account that owns the lists, emails and automations PopMCP should manage

## Get your credentials

### 1. Open the API tokens screen

Click your account dropdown in the top-right corner, then go to Settings, Connections, API tokens. The direct link is `sendfox.com/account/oauth`.

Screen: https://sendfox.com/account/oauth

### 2. Create a personal access token

Under Personal Access Tokens click Create New Token, type `PopMCP` in the Name field, and click Create.

Screen: https://sendfox.com/account/oauth

### 3. Copy the token before closing the dialog

Click Copy and paste the token straight into PopMCP. It is a long Laravel Passport string starting `eyJ`, so check the whole value came across.

### 4. Paste it into PopMCP

Paste the token into PopMCP's Personal access token field and click Connect.

## Fields PopMCP asks for

- Personal access token (apiToken) [required]: In SendFox go to Settings → Connections → API tokens (or open https://sendfox.com/account/oauth) → Create New Token, give it a name, and copy it; SendFox shows it only once. It's sent as the Authorization: Bearer header and stored encrypted; used server-side only. Requires a paid SendFox plan.

## Verify

PopMCP shows SendFox as Connected. Asking for your lists or recent emails returns real names instead of a 401 or 402 error.

## Troubleshooting

### 401 Unauthorized

Cause: The token was truncated on paste, or it was deleted from the API tokens page. These tokens run to well over a thousand characters, so a partial copy is easy.

Fix: Return to sendfox.com/account/oauth, click Create New Token, and paste the entire string with no whitespace or line breaks.

### 402 Payment Required

Cause: The account is on the SendFox free plan, where the API is unavailable.

Fix: Upgrade to a paid SendFox plan, then reconnect with the same token.

### The token was never copied

Cause: SendFox displays the value only at creation and cannot show it again.

Fix: Delete that token on the API tokens page and click Create New Token again.

### Errors come back as HTML instead of a readable message

Cause: The request is missing an Accept header, which SendFox uses to decide the error format.

Fix: Nothing to change in PopMCP, which already sends Accept: application/json. If you are testing by hand in curl, add that header.

---

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