Connect Linnworks
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Linnworks 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 Linnworks. Only the status word and the order number.
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 Linnworks 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 Linnworks. 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 Linnworks 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 Linnworks's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Linnworks 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 Linnworks 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: Linnworks does not state a price for developer access in the pages read.
Part 1. Get your key from Linnworks
Do this on your computer, in a new browser tab, signed in to Linnworks.
- Ask the account holder to request a Linnworks developer account (see the Quick Start Guide at apidocs.linnworks.net).
- Sign in to the Linnworks developer portal (developer.linnworks.com).
- Create an application, enter an Application Name and choose System Integration as the type, then save.
- Copy the Application ID and Application Secret.
- Open the App Modules tab and press Create New Version, then keep the order read permission only.
- On the General page, open the Installation URL while signed in to your Linnworks account and install the app.
- Copy the Permanent Token shown after installation.
- Paste the three values into Speakvora.
WARNING: If Linnworks asks which permissions to give, tick only the read-only ones: orders: read (view order details). 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
- Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
- 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.
- Under Your apps type Linnworks in the box that says Find an app (1), or scroll down the list.
- Press Linnworks. 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.)



Part 3. Paste it in
3 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- Application ID. Shown in the Linnworks developer portal after the application is created.
- Application Secret (secret: it stays on this computer and is never shown again, only the last few characters). Shown next to the Application ID in the developer portal.
- Permanent Token (secret: it stays on this computer and is never shown again, only the last few characters). Shown after the application is installed on your Linnworks account using its Installation URL.

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
- Press the orange Save and test button.
- Linnworks 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.

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 Linnworks), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Linnworks is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Linnworks when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Linnworks. 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 Linnworks, or Linnworks 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.
- Linnworks says you need a plan or approval: Linnworks uses a two-step login: the Application ID, Application Secret and Permanent Token are POSTed to /api/Auth/AuthorizeByApplication to get a session token that expires after 20 minutes idle, and that session token goes in the Authorization header. Orders are read with GET /api/Orders/GetOrderById?pkOrderId=<UUID> (status in GeneralInfo.Status), which needs Linnworks' internal order UUID, not the order number the customer knows, and is served from a regional server. Speakvora's connector cannot do the session exchange or the number lookup yet, so no test or order call is declared.
- 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
- Forward order confirmation emails to the agent mailbox
- Export open orders from Linnworks to CSV and import into the pack
Linnworks's own instructions: https://apidocs.linnworks.net/docs/generating-an-api-key
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 Linnworks. 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 Linnworks, or Linnworks 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: Linnworks says you need a plan or approval?
Linnworks uses a two-step login: the Application ID, Application Secret and Permanent Token are POSTed to /api/Auth/AuthorizeByApplication to get a session token that expires after 20 minutes idle, and that session token goes in the Authorization header. Orders are read with GET /api/Orders/GetOrderById?pkOrderId=<UUID> (status in GeneralInfo.Status), which needs Linnworks' internal order UUID, not the order number the customer knows, and is served from a regional server. Speakvora's connector cannot do the session exchange or the number lookup yet, so no test or order call is declared.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.