Connect Extensiv 3PL Warehouse Manager

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

Short answer: This connects your own Extensiv 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 Extensiv. 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 Extensiv 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 Extensiv. 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 Extensiv 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 Extensiv's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Extensiv 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: warehouse voice. How Extensiv gives access: The vendor only gives API access after an approval or a business agreement. Ask them first (steps below); until then use the no-API options at the end. What it costs you: Not stated in the public docs. Direct developer support needs a Developer Enablement package; ask your Customer Success Manager about cost.

Part 1. Get your key from Extensiv

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

  1. Sign in to 3PL Warehouse Manager as an administrator of your warehouse account.
  2. Click Support, then choose Manage Credentials (Beta), and generate REST API keys. If the option is missing, ask your warehouse representative or Customer Success Manager to provide them.
  3. Tell them you need read-only REST API access to orders only, for a status-lookup assistant, and ask for the Client ID, Client Secret and user_login.
  4. Also ask which Customer ID and Warehouse ID the keys apply to, and whether a Developer Enablement package is required.
  5. Paste the Client ID, Client Secret and user_login into Speakvora. Never share them by email or chat.

WARNING: If Extensiv asks which permissions to give, tick only the read-only ones: orders: read. 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 Extensiv 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 Extensiv 3PL Warehouse Manager. 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

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:

  1. REST API Client ID. The Client ID from the REST API keys your warehouse issued (Support > Manage Credentials in 3PL Warehouse Manager).
  2. REST API Client Secret (secret: it stays on this computer and is never shown again, only the last few characters). The Client Secret that came with the Client ID. Treat it like a password.
  3. User login. The user_login value your warehouse representative supplied with the keys.
  4. 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. Extensiv 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 Extensiv), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Extensiv is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Extensiv when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Extensiv. 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 Extensiv, or Extensiv 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.
  • Extensiv says you need a plan or approval: Extensiv documents a token flow: POST https://secure-wms.com/AuthServer/api/Token with Basic ClientID:ClientSecret, grant_type client_credentials and user_login, returning a bearer token valid about 30 to 60 minutes. The official pages read did not state the API base URL or the single-order read call, so no test or order call is set until it is confirmed. The static-credential connector cannot yet exchange tokens either.
  • 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

  • Ask the warehouse to email or export order status reports instead.

Extensiv's own instructions: https://developer.3plcentral.com/

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 Extensiv. 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 Extensiv, or Extensiv 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: Extensiv says you need a plan or approval?

Extensiv documents a token flow: POST https://secure-wms.com/AuthServer/api/Token with Basic ClientID:ClientSecret, grant_type client_credentials and user_login, returning a bearer token valid about 30 to 60 minutes. The official pages read did not state the API base URL or the single-order read call, so no test or order call is set until it is confirmed. The static-credential connector cannot yet exchange tokens either.

What if this happens: Still stuck??

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