Pinterest — how to connect

Creates image Pins on a Pinterest board via the Pinterest API v5 (image required — text-only posts are rejected). Connect with OAuth after adding your Pinterest app's App ID and secret below; the first board in your account is selected automatically and can be overridden per-account.

Pinterest connects via OAuth: you register one developer app to get an App ID and App secret, enter those two values in the integration, then connect each Pinterest account through the OAuth popup.

Before you start

A Pinterest Business account (or a personal account converted to Business) with at least one board already created — the connector auto-selects the first board and publish() fails with "No Pinterest board selected" if none exists
A Pinterest developer app registered at developers.pinterest.com with PINTEREST_CLIENT_ID and PINTEREST_CLIENT_SECRET set in config, and your redirect URI added to the app's allowed redirect URIs
Your app must be approved past Pinterest's Trial access review (typically 1-3 business days) — apps stuck in trial-pending return HTTP 401 'consumer type not supported' on every v5 endpoint, and Pins created while still in Trial are hidden from public view even after a successful publish
A publicly reachable HTTPS image URL for every post — Pinterest only supports the image_url media source (it fetches the URL server-side); localhost, private, or auth-gated image URLs will fail Pin creation since this adapter has no base64 upload fallback

Step by step

1
Create/sign in to a Pinterest developer account
Go to the Pinterest Developers portal and sign in with the Pinterest Business account you'll manage, then create a developer account if you don't have one.
Open
2
Create a new app
From My apps, create (Connect) a new app and give it a name — this generates the app's unique App ID and App secret.
Open
3
Add the redirect URI
In the app's settings, add the exact redirect URI this tool shows you during OAuth connect (it must match character-for-character or authorization will fail).
4
Copy the App ID and App secret into this tool
Paste the App ID into 'App ID' and the App secret into 'App secret' in the Pinterest integration config.
5
Request the required scopes and access tier
Ensure the app requests pins:read, pins:write, boards:read, and user_accounts:read scopes, and apply for Standard (not just Trial) access if you need to publish Pins in production.
6
Connect the account
Click Connect in this tool to run the OAuth flow, approve the requested scopes on Pinterest, and the first board on the account will be auto-selected (overridable per account).

App keys (set once in Settings)

App ID (client ID)
developers.pinterest.com → My apps → your app → "App ID". Needs a Pinterest Business account; add this tool's redirect URI to the app's allowed list.
App secret (client secret)secret
Same app → "App secret". Apply for Standard access (past Trial) or published Pins stay hidden from public view.

Good to know

Trial access is typically read-only for many endpoints; publishing Pins in production generally requires applying for Standard access, which Pinterest reviews (roughly 1-3 business days per community reports).
The redirect URI must match exactly what was registered on the app, or the OAuth callback will be rejected.
The adapter requires an image on every Pin — text-only posts are rejected by the Pinterest API v5.
Only App ID and App secret are needed at the integration/config level; no other per-account credentials are requested by this adapter.

Troubleshooting

OAuth connect succeeds but publish() returns 'No Pinterest board selected (set account.meta.boardId)': finishOAuth only auto-picks the first board returned by GET /v5/boards at connect time; if the account had zero boards then, create a board in Pinterest first, then set account.meta.boardId manually (or reconnect) to the desired board ID.
Every authenticated call (user_account, boards, pins) returns 401 with error code 3, 'Your application consumer type is not supported, please contact support': The app is still in Pinterest's Trial-access review queue — wait for the 1-3 business day approval, or open a ticket in the Pinterest Business developer community if it stalls; the app secret and all v5 endpoints are unusable until Trial is approved.
Pin creation succeeds (id returned) but the Pin never shows up publicly on the account/board: Apps in Trial access can create Pins via the API, but Pinterest keeps Trial-created Pins hidden from public view — confirm the app has moved to Standard (production) access before treating publishes as live.
401/403 'insufficient scope' on /v5/pins or /v5/boards even though the token exchange succeeded: The authorize URL's scope list (pins:read,pins:write,boards:read,user_accounts:read) must match what the app was approved and consented for — disconnect and re-run OAuth so the user re-consents to all four scopes; a token minted before a scope was added won't retroactively gain it.
Publishing (or the background refresh) fails after roughly 30 days with an expired/invalid access token: Pinterest access tokens last ~30 days; refreshAccessToken() uses the stored refresh_token (valid ~1 year) to mint a new one automatically. If no refresh_token was ever captured on connect, or it has expired past its ~1-year window, the operator must fully reconnect the account via OAuth.

Pinterest developer docs

Before you start

A Pinterest Business account (or a personal account converted to Business) with at least one board already created — the connector auto-selects the first board and publish() fails with "No Pinterest board selected" if none exists

A Pinterest developer app registered at developers.pinterest.com with PINTEREST_CLIENT_ID and PINTEREST_CLIENT_SECRET set in config, and your redirect URI added to the app's allowed redirect URIs

Your app must be approved past Pinterest's Trial access review (typically 1-3 business days) — apps stuck in trial-pending return HTTP 401 'consumer type not supported' on every v5 endpoint, and Pins created while still in Trial are hidden from public view even after a successful publish

A publicly reachable HTTPS image URL for every post — Pinterest only supports the image_url media source (it fetches the URL server-side); localhost, private, or auth-gated image URLs will fail Pin creation since this adapter has no base64 upload fallback

Step by step

Create/sign in to a Pinterest developer account

Go to the Pinterest Developers portal and sign in with the Pinterest Business account you'll manage, then create a developer account if you don't have one.

Open

Create a new app

From My apps, create (Connect) a new app and give it a name — this generates the app's unique App ID and App secret.

Open

Add the redirect URI

In the app's settings, add the exact redirect URI this tool shows you during OAuth connect (it must match character-for-character or authorization will fail).

Copy the App ID and App secret into this tool

Paste the App ID into 'App ID' and the App secret into 'App secret' in the Pinterest integration config.

Request the required scopes and access tier

Ensure the app requests pins:read, pins:write, boards:read, and user_accounts:read scopes, and apply for Standard (not just Trial) access if you need to publish Pins in production.

Connect the account

Click Connect in this tool to run the OAuth flow, approve the requested scopes on Pinterest, and the first board on the account will be auto-selected (overridable per account).

App keys (set once in Settings)

App ID (client ID)

developers.pinterest.com → My apps → your app → "App ID". Needs a Pinterest Business account; add this tool's redirect URI to the app's allowed list.

App secret (client secret)secret

Same app → "App secret". Apply for Standard access (past Trial) or published Pins stay hidden from public view.

Good to know

Trial access is typically read-only for many endpoints; publishing Pins in production generally requires applying for Standard access, which Pinterest reviews (roughly 1-3 business days per community reports).

The redirect URI must match exactly what was registered on the app, or the OAuth callback will be rejected.

The adapter requires an image on every Pin — text-only posts are rejected by the Pinterest API v5.

Only App ID and App secret are needed at the integration/config level; no other per-account credentials are requested by this adapter.

Troubleshooting

OAuth connect succeeds but publish() returns 'No Pinterest board selected (set account.meta.boardId)'

finishOAuth only auto-picks the first board returned by GET /v5/boards at connect time; if the account had zero boards then, create a board in Pinterest first, then set account.meta.boardId manually (or reconnect) to the desired board ID.

Every authenticated call (user_account, boards, pins) returns 401 with error code 3, 'Your application consumer type is not supported, please contact support'

The app is still in Pinterest's Trial-access review queue — wait for the 1-3 business day approval, or open a ticket in the Pinterest Business developer community if it stalls; the app secret and all v5 endpoints are unusable until Trial is approved.

Pin creation succeeds (id returned) but the Pin never shows up publicly on the account/board

Apps in Trial access can create Pins via the API, but Pinterest keeps Trial-created Pins hidden from public view — confirm the app has moved to Standard (production) access before treating publishes as live.

401/403 'insufficient scope' on /v5/pins or /v5/boards even though the token exchange succeeded

The authorize URL's scope list (pins:read,pins:write,boards:read,user_accounts:read) must match what the app was approved and consented for — disconnect and re-run OAuth so the user re-consents to all four scopes; a token minted before a scope was added won't retroactively gain it.

Publishing (or the background refresh) fails after roughly 30 days with an expired/invalid access token

Pinterest access tokens last ~30 days; refreshAccessToken() uses the stored refresh_token (valid ~1 year) to mint a new one automatically. If no refresh_token was ever captured on connect, or it has expired past its ~1-year window, the operator must fully reconnect the account via OAuth.