> 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/pinterest.md).

# Pinterest

## OAuth app properties

| Property                | Value                                                                                                                                                                                                                      |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Conditional.** Production use needs *Standard access*. With *Trial access* Pins and boards that the app creates are visible only to their creator, and all users share 1,000 requests per day.                           |
| **Vendor review**       | **Required** twice: Pinterest reviews the request for Trial access before the app can call the API, then the upgrade to Standard access. The upgrade needs a video of the app using the API, including the OAuth flow.     |
| **Review time**         | Not published. Pinterest sends an email with the decision.                                                                                                                                                                 |
| **Users before review** | None before Trial access is approved. In Trial access no user limit is documented, but Pins and boards stay sandboxed.                                                                                                     |
| **App owner**           | A Pinterest account with a verified email address that has accepted the Developer Terms. Pinterest points to a business account for this.                                                                                  |
| **Regions**             | One app works worldwide.                                                                                                                                                                                                   |
| **Client secret**       | No expiry documented. After a reset on **My apps**, existing tokens keep working, but new tokens need the new secret.                                                                                                      |
| **Rate limits**         | Trial: 1,000 requests per day per app (300 for `ads_write` and `org_write`). Standard: 100 requests per second per user per app, plus per-minute category limits per user (for example `org_write` 100, `org_read` 1,000). |
| **Checked**             | 2026-11-13                                                                                                                                                                                                                 |

**Limitations**

* The refresh token expires when it is not used to refresh the access token within 60 days. An account that no flow uses for that long has to be connected again.
* Apps registered on or after 2026-09-14 may get HTTP `403 PINNER_DATA_ACCESS_DENIED` when they read a board or Pin of a user without a business account, unless Pinterest has authorized the app for such users.
* Standard access requests without the OAuth flow in the demo video, or with a login that collects passwords or cookies, are denied.

Sources: [Access tiers](https://developers.pinterest.com/docs/key-concepts/access-tiers/), [Connect your app](https://developers.pinterest.com/docs/getting-started/connect-app/), [Authentication and authorization](https://developers.pinterest.com/docs/getting-started/set-up-authentication-and-authorization/), [Rate limits](https://developers.pinterest.com/docs/reference/rate-limits/). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Pinterest – Connector Configuration

### Step 1: Create a Pinterest Business Account & Access Developer Portal

* Create or upgrade to a Pinterest Business account at [Pinterest Business](https://business.pinterest.com/)
* Navigate to the [Pinterest Developers Portal](https://developers.pinterest.com/)
* Sign in with your Pinterest Business account credentials

> ⚠️ **Note**: You need a Pinterest Business account to access the Pinterest API. Personal accounts cannot create apps.

***

### Step 2: Create Your App

1. **Create a new app**:
   * Go to [My Apps](https://developers.pinterest.com/apps/) in the developer portal
   * Click **"Create app"**
   * Fill in the application details:
     * **App name** (e.g., "My Pinterest Integration")
     * **App description** - Describe what your integration does
     * **Website URL** - Your application's website
     * **Platform** - Select "Web" for most integrations
2. **App Configuration**:
   * **App type**: Choose between "Public" or "Internal"
   * **Linked Business Account**: Link to your Pinterest Business account
   * **App Purpose**: Specify how you'll use Pinterest data

***

### Step 3: Configure OAuth Settings

1. **Navigate to App Settings**:
   * In your app dashboard, go to **"OAuth"** or **"Settings"** section
   * Configure OAuth redirect URIs
2. **Set Redirect URIs**:
   * Add your callback URL in the **"Redirect URIs"** field
   * For Appmixer, set the redirect URI to:

```http
https://[YOUR_API_BASE]/auth/pinterest/callback
```

Example:

```http
https://api.appmixer.com/auth/pinterest/callback
```

3. **Configure Scopes**:
   * Select the permissions your app needs:
     * `read_public` - Read public boards and pins
     * `write_public` - Create public boards and pins
     * `read_secret` - Read secret boards and pins (if authorized)
     * `write_secret` - Create secret boards and pins (if authorized)
     * `read_users` - Read user profile information
     * `write_users` - Update user profile information

***

### Step 4: Copy Your Credentials

After configuring your app, you'll find your API credentials:

* **App ID** (Client ID) - Your application's unique identifier
* **App secret** (Client Secret) - Your application's secret key

⚠️ **Important**: Keep your App Secret secure and never expose it in client-side code!

***

### Step 5: App Review Process

**For Public Apps**:

1. **Submit for Review**:
   * Public apps require Pinterest review before going live
   * Provide detailed use case description
   * Include screenshots and flow documentation
   * Specify which scopes you need and why
2. **Review Requirements**:
   * Your app must comply with Pinterest's API policies
   * Demonstrate legitimate use of requested permissions
   * Show how user data will be handled responsibly

***

### Step 6: Rate Limits

**Rate Limits**:

* Pinterest implements rate limiting per user and per app
* Specific limits depend on your app's approval status and usage
* Rate limit information is included in API response headers

***

### Important Notes

⚠️ **Business Account Required**:

* Only Pinterest Business accounts can create and manage apps
* Personal accounts cannot access the Pinterest API
* Convert your personal account to business if needed

⚠️ **Content Policy**:

* Pinterest has strict content policies and community guidelines
* All programmatically created content must comply with these rules
* Violations can result in API access suspension

⚠️ **Token Management**:

* Access tokens have expiration times
* Implement proper token refresh logic
* Store tokens securely and never expose them

⚠️ **Attribution**:

* Display appropriate Pinterest branding when required
* Follow Pinterest's brand guidelines
* Include proper attribution for Pinterest content

***

### Useful Links

* [Pinterest Developers Documentation](https://developers.pinterest.com/)
* [API Reference](https://developers.pinterest.com/docs/api/v5/)
* [OAuth Guide](https://developers.pinterest.com/docs/getting-started/authentication/)
* [Rate Limits](https://developers.pinterest.com/docs/getting-started/rate-limits/)
* [Pinterest Business](https://business.pinterest.com/)
* [Community Guidelines](https://policy.pinterest.com/community-guidelines)
* [Brand Guidelines](https://business.pinterest.com/brand-guidelines/)

***

## Backoffice configuration

Configuration ID: `appmixer:pinterest` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — the **App ID** of the Pinterest app registered above. Not needed when Pinterest is authenticated through the Appmixer Auth Hub.
* `clientSecret` — the **App secret** of the same app. Not needed with the Auth Hub.

![Pinterest configuration in the Backoffice](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-30714c79c71f71ba3ea12371b896dc6c3f1f9467%2FpinterestImage-1.png?alt=media) ![clientId and clientSecret keys](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-5188f14eed433dce2a00373d33dafc84ccb1ad3c%2FpinterestImage-2.png?alt=media)

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

```bash
appmixer service-config set appmixer:pinterest -u -d '{
  "clientId": "<app id>",
  "clientSecret": "<app 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/pinterest.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.
