SP-API Developer Registration Process

A walkthrough of the Amazon SP-API developer registration process, including navigation path, form fields, security questionnaire handling, and common errors encountered. Derived from a live registration session with ^[1].

Prerequisites

• Access to the Seller Central account as the account owner (not a secondary user). The registration must be initiated from the owner login.
• Pre-written answers to the security questionnaire (see ^[2]).
• Developer contact details: name, email, phone, organization name, and website.

Critical: If the account owner email is defunct or inaccessible, you will not be able to reset the owner password or receive certain notifications. Resolve this before starting if possible — see ^[3].

Navigation Path

1. Log in to Seller Central as the account owner.
2. Click the hamburger menu (☰) in the upper left.
3. Scroll to Apps & Services → click Develop Apps.
4. On the developer portal landing page, select your account from the dropdown.
5. Click Start Setup, then select Build Applications that Use SP-API.
6. Click Apply.
7. Click Setup Solution Provider Account Profile.

Profile Form Fields

Primary Purpose / Use Case: Describe the business purpose in plain language (e.g., "Automated reporting and order management for a private seller account"). This field accepts up to ~1,000 characters.

Role Selection

• Select the API roles relevant to your integration (e.g., Orders, Finances, Inventory, Direct-to-Consumer Shipping).
• Do not select any "Restricted" roles unless your organization has completed a separate Open Banking registration with a national authority. Selecting a Restricted role without an Open Banking Identifier will block submission.

Security Questionnaire

The questionnaire covers organizational security controls. Prepare answers in advance and paste them into each field. Tips from the Doodla Farms session:

• Paste answers from a chat or document; clean up extra whitespace before submitting to avoid character-limit errors.
• Most yes/no questions should be answered Yes for a standard managed-services setup.
• The "List all outside parties" field can be answered None if no third parties have access to Amazon data.
• The "Data retention / breach response" field should specify a timeframe (e.g., less than 31 days).
• The final field asks for the incident management point of contact — provide name and email.

Common Errors & Resolutions

Error 1: Restricted Role Requires Open Banking Registration

Symptom: After clicking Register, an error appears: "Restricted roles contain personally identifiable information (PII). To use restricted roles, complete Open Banking registration…"

Resolution:
1. Scroll back up to the role selection section.
2. Deselect any role marked "Restricted."
3. Re-attempt submission.

Error 2: Missing Open Banking Identifier

Symptom: Even after deselecting Restricted roles, a second error appears: "For Open Banking, please provide your organization identifier (Org ID) issued by the national authority…"

Resolution:
- Enter N/A in the Open Banking Identifier field.
- Re-attempt submission.

Both errors were encountered and resolved during the Doodla Farms registration session. Resolving them in sequence allowed the form to submit successfully.

Submission & Confirmation

• After successful submission, a confirmation email is sent to the developer contact email (not the account owner email).
• Check the Seller Central case log a few days after submission to verify registration status.
• The developer portal may take several days to reflect an approved status.

Related Issues

• ^[4] — If the owner email is inaccessible, password resets fail and certain account actions are blocked. Resolution requires an Amazon support case.
• ^[1] — Client where this process was first documented. Owner email (mark@doodlafarms.com) was defunct at time of registration; a support case was opened to replace it.