Commerce
BigCommerce OAuth
BigCommerce app installation posts a code, scope, and store context to the app callback; it is not a normal user-entered authorization-code form.
Manual / specialised flowProvider docs
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- clientId and clientSecret
- registered auth callback URL
- installation callback code
- scope and store context
- signed load/uninstall payloads
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
BigCommerce app installation posts a code, scope, and store context to the app callback; it is not a normal user-entered authorization-code form.
Required inputs
- clientId and clientSecret
- registered auth callback URL
- installation callback code
- scope and store context
- signed load/uninstall payloads
Troubleshooting
- The store context returned during installation identifies the authorized store and must be retained.
- App install, load, uninstall, and user-removal callbacks have separate validation requirements.
Provider checklist
- Create a BigCommerce single-click app and register its callback URLs.
- Capture code, scope, and context from the installation callback.
- Exchange them at the BigCommerce OAuth token endpoint.
- Validate signed callback payloads before trusting store or user context.