Commerce
Amazon SP-API OAuth
Requires Amazon's SP-API install callback fields and LWA token handling; not supported by the generic OAuth form.
Specialised flow
Manual provider setup
Requires Amazon's SP-API install callback fields and LWA token handling; not supported by the generic OAuth form.
Required inputs
- application_id
- spapi_oauth_code
- selling_partner_id
- LWA client_id and client_secret
- x-amz-access-token for SP-API calls
- 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.
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- application_id
- spapi_oauth_code
- selling_partner_id
- LWA client_id and client_secret
- x-amz-access-token for SP-API calls
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.
Troubleshooting
- Amazon SP-API callbacks use application_id and spapi_oauth_code, not the standard client_id/code pair.
- SP-API resource requests use x-amz-access-token rather than a normal Bearer access token.
Provider checklist
- Capture application_id, selling_partner_id, and spapi_oauth_code from the install callback.
- Exchange the SP-API OAuth code through Login With Amazon token handling.
- Use x-amz-access-token when calling SP-API resource endpoints.
- Validate marketplace, role, and app-review requirements before production use.