Connect Amazon Seller Central (SP-API)

A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.

Short answer: This connects your own Amazon account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Amazon. Only the status word and the order number are.

Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.

This connects your own Amazon account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Amazon. Only the status word and the order number are ever texted back, never names, prices, items or addresses.

TIP: You need about 15 minutes, a computer, and the sign-in for your Amazon account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.

NOTE: This guide was written from Amazon's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Amazon account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.

Who this is for: amazon marketplace sellers. How Amazon gives access: The vendor connects through an authorised app. Follow the steps below to create or authorise it in your own account. What it costs you: Not stated in the pages read; SP-API access for your own seller account is not described as a paid add-on.

Part 1. Get your key from Amazon

Do this on your computer, in a new browser tab, signed in to Amazon.

  1. Sign in to Seller Central as the Primary User of the account.
  2. Open [[the menu > Apps and Services > Develop Apps]].
  3. Register as a developer for a private app if you have not already, choosing the Orders role without buyer personal data.
  4. Create an app and note its LWA client ID and client secret.
  5. Press Authorize app for your own seller account on the Authorize application page.
  6. Copy the refresh token shown once and paste it with the client ID, secret and region into Speakvora.

WARNING: If Amazon asks which permissions to give, tick only the read-only ones: Orders: read (Order Information role, no buyer personal data). Never give write or admin access.

TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.

Part 2. Open the Connect tab in your agent

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
  3. Step 1: press Connect (1)

  4. Under Your apps type Amazon in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Amazon Seller Central (SP-API). A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

4 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. LWA client ID. Shown on your private app in Seller Central under Apps and Services, then Develop Apps.
  2. LWA client secret (secret: it stays on this computer and is never shown again, only the last few characters). Shown with the client ID on your private app (View LWA credentials).
  3. Refresh token (secret: it stays on this computer and is never shown again, only the last few characters). Created when you press Authorize app for your own seller account (Primary User only).
  4. Marketplace region. NA, EU or FE, depending on where you sell.
  5. Part 3: each numbered box is one thing to paste. These are made-up examples.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.

Part 4. Test it

  1. Press the orange Save and test button.
  2. Amazon has no safe read-only check we can run, so nothing is called. The connection is used for real the first time a customer asks about an order, and any problem shows in Activity.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected. (here: *Saved* and the sentence about the first customer)

WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.

What happens next

  • A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Amazon), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Amazon is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Amazon when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Amazon. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
  • It cannot find an order (404): the number is not in Amazon, or Amazon uses a longer number than the one on the receipt.
  • It says too many requests (429): wait a minute and press Save and test again.
  • Amazon says you need a plan or approval: Amazon uses short-lived access tokens (about 1 hour) obtained by sending the refresh token to https://api.amazon.com/auth/o2/token. A pasted static key does not work, so no test or order call is defined until the connector supports this token exchange. The documented self-authorization route covers only your own seller account through a private app, not a service for other sellers. Regional SP-API endpoints, the getOrder path and the request-signing requirements were not confirmed in the pages read.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

If your plan has no API

  • Export recent orders from Seller Central under Orders, Manage Orders, or download the All Orders report.
  • Ask Speakvora support to set up a public-app authorization with you.

Amazon's own instructions: https://developer-docs.amazon/sp-api/docs/self-authorization

All help guides · Every agent feature · AI receptionist by industry

Questions

What if this happens: It says the key was refused (401 or 403)?

copy the key again from Amazon. Make sure there is no space before or after it, and that it is a live key for the right shop or location.

What if this happens: It cannot find an order (404)?

the number is not in Amazon, or Amazon uses a longer number than the one on the receipt.

What if this happens: It says too many requests (429)?

wait a minute and press Save and test again.

What if this happens: Amazon says you need a plan or approval?

Amazon uses short-lived access tokens (about 1 hour) obtained by sending the refresh token to https://api.amazon.com/auth/o2/token. A pasted static key does not work, so no test or order call is defined until the connector supports this token exchange. The documented self-authorization route covers only your own seller account through a private app, not a service for other sellers. Regional SP-API endpoints, the getOrder path and the request-signing requirements were not confirmed in the pages read.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.