> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/buffer.md).

# Buffer

Register a Buffer app client for the Appmixer Buffer connector (OAuth 2 with PKCE).

## OAuth app properties

| Property                | Value                                                                                                                                                                 |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any Buffer user can authorize the app client.                                                                                                                |
| **Vendor review**       | **None.** Buffer's docs describe no review.                                                                                                                           |
| **Review time**         | Not applicable.                                                                                                                                                       |
| **Users before review** | No limit.                                                                                                                                                             |
| **App owner**           | A Buffer account with a verified e-mail address. The plan sets how many app clients it can have: Free 1, Essentials 3, Team 5.                                        |
| **Regions**             | One app works worldwide.                                                                                                                                              |
| **Client secret**       | No expiry documented. You can rotate it in the API settings.                                                                                                          |
| **Rate limits**         | Per app client: 100 requests per 15 minutes, 500 per 24 hours and 15,000 per 30 days, plus 10, 25 and 100 for each authorized Buffer user, counted up to 1,000 users. |
| **Checked**             | 2026-11-13                                                                                                                                                            |

**Limitations**

* All Appmixer users share the limits of one app client. They grow with authorized users only up to 1,000 users.
* Refresh tokens are single-use. If an old refresh token is sent again, Buffer revokes the whole grant and the user has to connect the account again.
* The **Public client** choice cannot be changed later, and permissions that users already granted cannot be removed from the client.

Sources: [Building apps](https://developers.buffer.com/guides/building-apps.html), [Authentication](https://developers.buffer.com/guides/authentication.html), [API limits](https://developers.buffer.com/guides/api-limits.html). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Register the Buffer app client

You need a Buffer account with a verified e-mail address. App clients are created in the Buffer web dashboard, not on a separate developer portal. How many app clients you can create depends on the Buffer plan of the account (Free accounts get one).

1. Sign in to [Buffer](https://buffer.com/) with the account that will own the app.
2. Click the profile icon in the lower left corner of the dashboard and choose **API**, or open [Settings → API](https://publish.buffer.com/settings/api) directly.
3. Open the **App Clients** tab and click **+ New Client**.
4. Under **Info**:
   * **Name**: your users see it on the Buffer consent screen. You can also upload a **Logo** (at least 180×180 px).
   * **Privacy Policy URL**: a publicly accessible URL.
   * Leave **Public client (no client secret)** **unchecked**. The connector is a confidential client: it sends the client secret on every token request and uses it to derive the PKCE code verifier. You cannot change this choice later, so if you created a public client, create a new one.
5. Under **Permissions**, tick the scopes the connector requests (see [Scopes](#scopes)): **accountRead**, **postsRead**, **postsWrite**, **ideasRead** and **ideasWrite**.
6. Under **Redirects**, add `https://<your-appmixer-api>/auth/buffer/callback`. Replace the host with your Appmixer API URL and keep the suffix `/auth/buffer/callback` (for example `https://api.acme.appmixer.cloud/auth/buffer/callback`). The URL has to match exactly. Buffer accepts up to 5 redirect URLs per client.
7. Click **Save Changes**.
8. Copy the **Client ID** and **Client Secret** of the new client. Keep the secret private.

### Scopes

The connector requests these scopes when a user connects an account. All components use the same set, including **Make API Call**:

* `account:read`: read account information. The connector reads the account name shown in Appmixer and validates the token with it.
* `posts:read` and `posts:write`: read posts and the queue, and create, update and delete posts (**Get Post**, **Find Posts**, **Create Post**, **Update Post**, **Delete Post**, the **New Post** and **Post Sent** triggers).
* `ideas:read` and `ideas:write`: read and create ideas (**List Ideas**, **Create Idea**).
* `offline_access`: returns a refresh token. You do not tick it in the dashboard because Buffer adds it automatically.

If the app client is missing a permission, Buffer does not show it on the consent screen, and the components that need it fail. You can add permissions to an existing client later, but you cannot remove permissions that users already granted.

{% hint style="info" %}
**Tokens.** Buffer access tokens expire after one hour, and the connector refreshes them on its own. Buffer refresh tokens are single-use: each refresh returns a new refresh token and invalidates the old one. If an old refresh token is reused, Buffer revokes the whole grant and the user has to reconnect the account.
{% endhint %}

### Rate limits

Buffer counts requests **per app client**, in 15-minute, 24-hour and 30-day windows. The allowance grows with the number of Buffer users who have authorized the app. Because every Appmixer user shares one app client, the connector throttles itself to 100 requests per 15 minutes and 5 requests per second per Appmixer user. Buffer has no webhooks, so the **New Post** and **Post Sent** triggers poll. Set their polling interval as high as your flows allow. See [Buffer API](https://buffer.com/developer-api) for the current limits.

### Useful links

* [Buffer API: Authentication (OAuth)](https://developers.buffer.com/guides/authentication.html)
* [Buffer API: Building apps](https://developers.buffer.com/guides/building-apps.html)
* [How to create your Buffer API key (Registering your app)](https://support.buffer.com/en-us/articles/how-to-create-your-buffer-api-key-ShIgYVwM6j)

## Backoffice configuration

Configuration ID: `appmixer:buffer` (Backoffice → Configuration). See [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how to create a configuration and how its keys reach the connector.

* `clientId`: Client ID of the Buffer app client registered above. Not needed when Buffer is authenticated through the Appmixer Auth Hub.
* `clientSecret`: Client Secret of the same app client. Not needed with the Auth Hub.
* `listCacheTTL`: Optional. How long, in milliseconds, **List Organizations** and **List Channels** cache their results when they load the dropdown options of the other components. Default `120000` (2 minutes).
* `outputFilePrefix`: Optional. File name prefix of the CSV file that **Find Posts**, **List Channels**, **List Ideas** and **List Organizations** create when their output is set to *File*. The file is named `<prefix>-<component name>.csv`. Default `buffer-objects-export`.

You can set the same keys with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:buffer -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/buffer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
