Connect BLAZE Retail (Greenline in Canada)
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own BLAZE 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 BLAZE. Only the status word and the order number are ever.
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 BLAZE 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 BLAZE. 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 BLAZE 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 BLAZE's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live BLAZE 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 BLAZE 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 BLAZE API documentation; ask BLAZE.
Part 1. Get your key from BLAZE
Do this on your computer, in a new browser tab, signed in to BLAZE.
- Contact your BLAZE account manager or BLAZE support (blaze.me) as the shop owner.
- Say you want API access for a third-party assistant that only reads orders (transactions) for your shop.
- Ask for a partner key and a developer key tied to your company and shop, limited to read-only access to transactions and the store.
- Ask which call looks up an order by its customer-facing order number (transNo), and whether webhooks for order updates are available.
- Ask what it costs and how long approval takes.
- When BLAZE sends the keys, paste the partner key and the developer key here and press Test; keep them private.
WARNING: If BLAZE asks which permissions to give, tick only the read-only ones: Read-only access to transactions (orders) for your shop. 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 BLAZE in the box that says Find an app (1), or scroll down the list.
- Press BLAZE Retail (Greenline in Canada). 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:
- BLAZE partner key (secret: it stays on this computer and is never shown again, only the last few characters). The partner key BLAZE gives you after your API access request is approved. It is sent as the x-api-key header.
- BLAZE developer key for your shop (secret: it stays on this computer and is never shown again, only the last few characters). The developer key tied to your company and shop, sent as the Authorization header.

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

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 BLAZE), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If BLAZE is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks BLAZE when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from BLAZE. 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 BLAZE, or BLAZE 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.
- BLAZE says you need a plan or approval: BLAZE API access is issued by BLAZE: the docs send every request with a partner key (x-api-key) and a shop-bound developer key (Authorization), but do not say how either is issued. Transactions are read by transaction id (GET /api/v1/partner/transactions/{transactionId}, status field 'status'); no lookup by the customer-facing order number (transNo) is documented, so no order lookup is configured until BLAZE confirms one. The store test call and header handling are not confirmed against a live account.
- 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 shop's BLAZE account manager whether a read-only transactions export or webhook can be enabled.
BLAZE's own instructions: https://apidocs.blaze.me/intro
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 BLAZE. 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 BLAZE, or BLAZE 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: BLAZE says you need a plan or approval?
BLAZE API access is issued by BLAZE: the docs send every request with a partner key (x-api-key) and a shop-bound developer key (Authorization), but do not say how either is issued. Transactions are read by transaction id (GET /api/v1/partner/transactions/{transactionId}, status field 'status'); no lookup by the customer-facing order number (transNo) is documented, so no order lookup is configured until BLAZE confirms one. The store test call and header handling are not confirmed against a live account.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.