Pinterest Platform Credential Setup
Use your own Pinterest app when customer connections should show your brand and consume your Pinterest app's access and quota. Register both UniPost callback URLs before testing either connection entry point.
Fastest route to a first success: create the app in Pinterest Developers, add the callback URL shown on this page, paste the credentials into UniPost, then connect one real test account before you expand scope or review work.
At a glance
| Question | Answer |
|---|---|
| Create the app in | Pinterest Developers |
| UniPost credential card | |
| Client fields to copy | App ID + App Secret |
| Best for | Products connecting customer-owned Pinterest business accounts and boards with their own app identity. |
| App review / approval | Pinterest access tiers control which accounts and data your app can reach. Prove the flow with approved test accounts, then complete the access review required for your production rollout. |
Before you start
- A company-owned Pinterest developer account.
- A Pinterest business account and board you can use for the first connection and publish test.
- Your production privacy-policy and terms URLs for the app submission.
- An internal owner for access review, app credentials, and future secret rotation.
Callback URLs to whitelist
Copy these exactly into the platform developer console. Redirect mismatches are the fastest way to burn time during setup.
https://api.unipost.dev/v1/oauth/callback/pinteresthttps://api.unipost.dev/v1/connect/callback/pinterestFirst working setup
1
Create or open the Pinterest app your company will operate
In Pinterest Developers, use a company-owned app rather than an individual engineer's long-term test app. Record the app owner and current access tier before you wire the credentials into UniPost.
2
Register both UniPost redirect URIs
Add every callback URL listed below exactly. The `/v1/oauth/callback/pinterest` URL serves workspace OAuth, while `/v1/connect/callback/pinterest` serves customer-facing Connect Sessions.
3
Save the App ID and App Secret in UniPost
Open Developer → Platform Credentials, choose Pinterest, and paste the App ID and App Secret. UniPost stores these workspace credentials for new Pinterest OAuth attempts.
4
Test with an account allowed by your current access tier
Start a fresh connection after saving the credentials. If authorization succeeds but account or board access is restricted, confirm the Pinterest app's access tier and approved test-account list before changing the redirect configuration.
5
Run a board and Pin smoke test
After the account appears in UniPost, confirm its boards can be listed and publish one controlled Pin. That validates app access, OAuth, board permissions, and publishing together.
What to paste into UniPost
| Pinterest app field | UniPost field | Notes |
|---|---|---|
| App ID | App ID | Use the identifier shown for the same Pinterest app whose redirects you configured. |
| App Secret | App Secret | Treat it as a production secret and rotate it through the same dashboard row. |
| Redirect URIs | Callback URLs below | Pinterest requires exact matches; register both UniPost connection paths. |
Save the credentials first, then start a fresh connection attempt. Troubleshooting an OAuth flow against stale credentials usually creates false leads.
Connect a Pinterest account through your app
After your Pinterest app credentials are saved, prove the customer-facing flow your own app will use: create an API key, choose the target profile, create a Connect session, send the returned OAuth URL to your end user, then confirm UniPost recorded the managed Pinterest account.
1
Step 1: create your first API key in the dashboard
Open UniPost in the same workspace where you saved the Pinterest credentials, create an API key, and store it immediately. The first key must be created in the dashboard because there is no API key available yet to call POST/v1/api-keys.
2
Step 2: list profiles and copy the `profile_id` you will use for branding
Every workspace gets at least one profile. Start by listing profiles so you can grab the
id for the profile that should own your hosted Connect branding.3
Step 3: patch the profile branding that should show on hosted Connect
With the
profile_id in hand, update the logo, display name, and primary color. This is the fastest way to confirm your hosted Connect surface is reading your own branding instead of UniPost defaults.4
Step 4: create a Pinterest Connect session for your app user
From your backend, create a Connect session with
platform set to pinterest, the target profile_id, and your stable external_user_id. UniPost returns a hosted OAuth URL. Redirect your app user to that URL, or open it inside the connection flow in your own product, so they can authorize their Pinterest account under your platform app.5
Step 5: confirm the managed Pinterest account is visible through the API
After the user completes OAuth, UniPost stores the connected Pinterest account as a managed account tied to your
external_user_id. Verify it through the accounts API; the same user should also appear in the dashboard's Developer App Users view. Use an account allowed by the Pinterest app's current access tier so an access restriction is not mistaken for an OAuth wiring problem.6
Step 6: use that managed account and profile in your first real API workflow
At this point you have the four values you need most often:
API_KEY, profile_id, external_user_id, and the connected Pinterest account_id. From here, list boards and publish a controlled Pin to validate the production workflow end to end.Common blockers
| Blocker | What to do about it |
|---|---|
| Only one callback registered | Workspace OAuth and Connect Sessions use different UniPost paths. Register both URLs even if you plan to launch one entry point first. |
| Access-tier restrictions | A correct OAuth setup can still be limited to approved test accounts until Pinterest grants the access needed for production. |
| App ID naming | Pinterest calls the public identifier an App ID. Store it in UniPost's App ID field; do not substitute an account or board ID. |
Definition of done
- Both UniPost Pinterest callback URLs are registered exactly.
- Pinterest consent shows the intended app identity.
- A permitted Pinterest business account connects successfully.
- Boards can be listed and a controlled Pin can be published.