# Buffer setup for PopMCP

One Buffer personal API key, the Bearer token you paste into PopMCP's Personal API key field.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.buffer.com
- Credentials screen: https://publish.buffer.com/settings/api
- Provider docs: https://developers.buffer.com

## Before you begin

- A Buffer account. Free works, and allows 1 personal key, Essentials 3, Team 5
- The key acts on your own Buffer account and reaches every organization and channel in it
- Personal keys always carry an expiry, so plan to reconnect when it lapses

## Get your credentials

### 1. Open Buffer's API settings

Click the profile icon in the lower-left corner of the dashboard and choose API.

Screen: https://publish.buffer.com/settings/api

### 2. Start a new personal key

Open the Personal Access tab and click + New Key in the Keys section.

Screen: https://publish.buffer.com/settings/api

### 3. Name the key, keep the permissions, pick an expiry

Name the key `PopMCP` and leave every box under Permissions ticked. Set the expiry to 1 year, then click Generate API Key.

Screen: https://publish.buffer.com/settings/api

### 4. Copy the key into PopMCP

Click Copy key in the dialog. Paste the token into PopMCP's Personal API key field and save.

## Fields PopMCP asks for

- Personal API key (apiKey) [required]: Buffer app → Settings → API → Personal Keys tab → + New Key → choose permissions + an expiry → Generate API Key → copy it. Stored encrypted; used server-side only (sent as Authorization: Bearer). The connection is locked to this key's account. Note: a personal key has an expiry (up to 1 year). Reconnect with a fresh key when it lapses.

## Verify

The Buffer connector in PopMCP shows Connected. Asking it to list your channels returns the social accounts you have linked in Buffer.

## Troubleshooting

### 401 Unauthorized

Cause: The key expired, was revoked, or the Authorization header lost the token.

Fix: Create a fresh personal key on Settings then API, and reconnect in PopMCP.

### 429 Too Many Requests

Cause: You crossed one of Buffer's three windows: 15 minute, 24 hour or 30 day.

Fix: The 429 body names the window that was exhausted. Wait it out, or ask Buffer developer support for a higher limit.

### Buffer refuses to create another key

Cause: Your plan's key allowance is used up: 1 on Free, 3 on Essentials, 5 on Team.

Fix: Delete a key you no longer use, or upgrade the plan.

### Posts land on the wrong brand

Cause: The personal key spans every organization on the account.

Fix: Name the channel or organization explicitly in your prompt. The credential cannot be narrowed.

### You want to revoke access later

Cause: Keys and connected clients are managed in two places on the same tab.

Fix: Delete the key under Keys, or remove the entry under Active Integrations, which revokes access straight away.

---

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