GITHUB
~30 MIN$0PRO SELLER ACCOUNT NO APPROVAL WAIT*
SETUP // ONE TIME // YOUR OWN PRIVATE APP

Get your Amazon API keys.

Claude FBA talks to Amazon through your own private SP-API app — no third-party service ever sees your data, and credentials never leave your machine. Creating the app is free, needs no approval beyond your own seller account, and takes about 30 minutes once.

$python3 scripts/sp_api.py  # the verify step, once keys are in
*PRIVATE DEVELOPER PROFILES ARE USUALLY APPROVED INSTANTLY — SEE STEP 01
// 01 — THE STEPS

Six steps. One time.

Everything happens inside your own Seller Central — the same place you already log into. Nothing here is granted to anyone but you.

01
Become a developer (your own account)

Seller Central → Apps & Services → Develop Apps. First time, Amazon asks for a Developer Profile: choose Private developer (you're building for your own business), answer the data-use questionnaire honestly, submit.

*The one waitProfiles are usually approved instantly or within a day or two. If yours goes to review, everything below waits on it — do this step first, today.

02
Add a new app client

Develop Apps → Add new app client. Name it anything (claude-fba works), API type SP-API, and check these roles:

[REQUIRED]
Product Listing

read + patch listings, A+ read

[REQUIRED]
Inventory & Order Tracking

orders + review solicitations

[REQUIRED]
Pricing

price data

[REQUIRED]
Selling Partner Insights

account / marketplace info

[OPTIONAL]
Brand Analytics

search query performance

Save. The app shows as Draft — that's fine; self-authorization works from draft.

03
Copy your LWA credentials

App row → View under LWA credentials. Copy the Client ID (amzn1.application-oa2-client.…) and Client Secret.

SecurityThese give API access to your store. Never commit them, never paste them into websites or chats. Claude FBA keeps them in a gitignored local file only.

04
Self-authorize → refresh token

App row → Authorize → confirm. Amazon shows a Refresh Token starting with Atzr| — copy it immediately. This token lets the toolkit act as you, on your store only. No third-party OAuth, because there are no third parties.

05
Wire it into Claude FBA
cp scripts/config.example.env scripts/config.env

Fill in the three values from steps 03–04: LWA_CLIENT_ID, LWA_CLIENT_SECRET, SP_REFRESH_TOKEN.

06
Prove it works
python3 scripts/sp_api.py

Exchanges your token and probes all three regions, printing every marketplace you sell in. Copy its output into config.env (SP_REGION, MARKETPLACE_ID) and you're done — every skill and script works from here.

// 02 — IF SOMETHING BREAKS

Four failures. Four fixes.

Every setup problem we've seen maps to one of these.

SYMPTOM
CAUSE & FIX
403 Unauthorized on one endpoint
App is missing that role. Edit the app, check the role, and re-authorize — role changes need a fresh refresh token.
invalid_grant on token exchange
The refresh token was rotated (someone clicked Authorize again). Grab the newest token from the app row.
Auth works, zero marketplaces
App lacks the Selling Partner Insights role.
Develop Apps not visible
You need a Professional selling plan, and the Developer Profile from step 01 must be approved.