# Attentive setup for PopMCP

You end up with one Attentive API key, minted by a custom app you create, that you paste into PopMCP's API Key field.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.attentivemobile.com/v1
- Credentials screen: https://ui.attentivemobile.com/integrations/custom-app/management
- Provider docs: https://docs.attentive.com/docs/authentication

## Before you begin

- Attentive account with access to ui.attentivemobile.com
- Permission to create custom apps for your Attentive company
- A contact email Attentive can reach you on, which the app form requires

## Get your credentials

### 1. Open the custom app manager

Sign in to Attentive and go to Integrations, then open the Built by you tab on the App Marketplace. You can also jump straight to ui.attentivemobile.com/integrations/custom-app/management.

Screen: https://ui.attentivemobile.com/integrations/custom-app/management

### 2. Name the app and add a contact email

Enter a unique App name such as `PopMCP` and a Contact email Attentive can write to about the integration.

### 3. Set each API to Write, then click Create

Every API starts at No Access. Switch the ones PopMCP needs to Write, then click Create.

### 4. Copy the API key from the modal

Click Copy in the Copy API key modal, then close it with X. Paste the value into PopMCP's API Key field.

## Fields PopMCP asks for

- API Key (apiKey) [required]: In Attentive go to ui.attentivemobile.com → Integrations → Custom apps (Manage custom apps), create a private app, and copy its API key. Sent as an Authorization: Bearer header, stored encrypted, used server-side only. The connection is locked to this key's Attentive company.

## Verify

PopMCP shows the Attentive connection as Connected and a first call returns your own company's subscriber or catalog data rather than a 401.

## Troubleshooting

### 401 Unauthorized

Cause: The key is wrong or truncated, or the custom app was deleted.

Fix: Create a fresh custom app and copy the new key from the modal. Old keys cannot be re-displayed.

### 403 on some tools but not others

Cause: That API was left at No Access when the app was created.

Fix: Open the app under Integrations, Built by you, set the missing API to Write, and reconnect.

### I closed the modal without copying the key

Cause: Attentive shows the key exactly once and never again.

Fix: Delete the half-finished app, create a new one, and copy the key straight away.

### Calls hit the wrong company's data

Cause: The key is bound to the Attentive company that created the app.

Fix: Sign in to the correct company at ui.attentivemobile.com and create the app there.

### No Integrations entry in the sidebar

Cause: Your Attentive role does not include custom app management.

Fix: Ask an Attentive admin to create the app, or email api-tokens@attentivemobile.com.

---

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