Social / Content
Pinterest OAuth
Pinterest production access and available scopes depend on app review and product approval, so the workflow needs approval-aware guidance.
Manual / specialised flowProvider docs
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- appId and appSecret
- registered redirectUri
- approved Pinterest scopes
- authorization code
- sandbox or production environment
Result handling
- Use the checklist to complete provider-specific setup outside the generic form.
- Anonymous OAuth Hub workflows do not store secrets, tokens, or provider payloads.
- 01UnderstandReview why this provider needs a specialized setup path.
- 02CollectGather the required provider-specific fields.
- 03Run setupComplete the provider flow outside the generic OAuth form.
- 04ValidateUse the checklist to confirm token and metadata handling.
Specialised flow
Manual provider setup
Pinterest production access and available scopes depend on app review and product approval, so the workflow needs approval-aware guidance.
Required inputs
- appId and appSecret
- registered redirectUri
- approved Pinterest scopes
- authorization code
- sandbox or production environment
Troubleshooting
- Developer accounts may authorize during testing while other Pinterest users remain blocked until review.
- Request only scopes approved for the app and use the matching environment endpoints.
Provider checklist
- Register a Pinterest app and confirm its current access tier and approved scopes.
- Use the official authorization URL generated for that app environment.
- Exchange the code with the app credentials and exact redirect URI.
- Verify using the current user-account endpoint documented for the API version.