Connect Meadow
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Meadow 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 Meadow. 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 Meadow 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 Meadow. 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 Meadow 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 Meadow's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Meadow 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: dispensary. How Meadow 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 API docs; ask Meadow.
Part 1. Get your key from Meadow
Do this on your computer, in a new browser tab, signed in to Meadow.
- Sign in to Meadow Admin as a user with Full Privilege Admin access.
- Open [[Settings > API Settings]].
- Create a new client API key named Speakvora and tick only the Analytics permission.
- Copy the client key into the Client API key field above.
- Contact your Meadow representative and say you want read-only access so a voice assistant can tell callers their order status.
- Ask for the consumer key (X-Consumer-Key) for the Speakvora integration and paste it into the consumer key field.
- Ask Meadow to confirm that the order id used by GET /api/v1/orders/{orderId}/detail matches the order number your customers are given.
WARNING: If Meadow asks which permissions to give, tick only the read-only ones: Analytics: read-only historical data including orders. 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 Meadow in the box that says Find an app (1), or scroll down the list.
- Press Meadow. 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
2 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- Meadow partner (consumer) key (secret: it stays on this computer and is never shown again, only the last few characters). The X-Consumer-Key that a Meadow representative issues to the company building the integration.
- Your Meadow client API key (secret: it stays on this computer and is never shown again, only the last few characters). Created in Meadow Admin under Settings > API Settings by a Full Privilege Admin; tick only Analytics.

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.
- Meadow is asked for one harmless record, just to prove the key works. Nothing is changed in Meadow.

YOU SHOULD SEE: green words starting with Connected.
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 Meadow), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Meadow is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Meadow when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Meadow. 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 Meadow, or Meadow 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.
- Meadow says you need a plan or approval: Meadow requests need two headers: X-Client-Key, which the dispensary generates in Meadow, and X-Consumer-Key, which a Meadow representative issues to the integrating company. Without the consumer key the calls are refused. The docs show responses wrapped in a data envelope; the order id in the path is Meadow's own order id, which may differ from the number printed on a receipt.
- 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 Meadow support for a report of open orders by email.
- Use the Speakvora agent without a live order lookup.
Meadow's own instructions: https://api-docs.getmeadow.com/llms.txt
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 Meadow. 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 Meadow, or Meadow 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: Meadow says you need a plan or approval?
Meadow requests need two headers: X-Client-Key, which the dispensary generates in Meadow, and X-Consumer-Key, which a Meadow representative issues to the integrating company. Without the consumer key the calls are refused. The docs show responses wrapped in a data envelope; the order id in the path is Meadow's own order id, which may differ from the number printed on a receipt.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.