Connect Bokun (Tripadvisor)
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Bokun 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 Bokun. 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 Bokun 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 Bokun. 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 Bokun 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 Bokun's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Bokun 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: guidance wayfinding. How Bokun gives access: The vendor charges extra for API access or a higher plan. Check your plan before you start. What it costs you: API access may need a paid Bokun plan; the vendor docs do not state which plan.
Part 1. Get your key from Bokun
Do this on your computer, in a new browser tab, signed in to Bokun.
- Sign in to Bokun as the account owner.
- Create a booking channel for Speakvora (the API works inside a booking channel) and set its allowed checkout currency.
- Open Settings and find the API keys area for that channel.
- Create a new API key named Speakvora and tick only read permissions for bookings.
- Copy the access key and secret key when shown; the secret may not be shown again.
- If you cannot see API keys, ask Bokun support whether your plan includes API access.
WARNING: If Bokun asks which permissions to give, tick only the read-only ones: bookings: read only. 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 Bokun in the box that says Find an app (1), or scroll down the list.
- Press Bokun (Tripadvisor). 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:
- API access key. Shown when you create the API key in your Bokun settings.
- API secret key (secret: it stays on this computer and is never shown again, only the last few characters). Shown once when the API key is created; copy it then.

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.
- Bokun 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 Bokun), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Bokun is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Bokun when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Bokun. 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 Bokun, or Bokun 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.
- Bokun says you need a plan or approval: Bokun signs every request (X-Bokun-Date, X-Bokun-AccessKey and an HMAC-SHA1 X-Bokun-Signature over date + access key + method + path) which this connector cannot yet do. The production base URL and the read-one-booking call were not found in the public pages read, so no test or order call is listed.
- 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 Bokun support which plan includes API access and for read-only booking access.
Bokun's own instructions: https://bokun.dev/booking-api-rest/vU6sCfxwYdJWd1QAcLt12i/configuring-the-platform-for-api-usage-and-authentication/sFiGRpo4detkmrZPcWtQPj
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 Bokun. 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 Bokun, or Bokun 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: Bokun says you need a plan or approval?
Bokun signs every request (X-Bokun-Date, X-Bokun-AccessKey and an HMAC-SHA1 X-Bokun-Signature over date + access key + method + path) which this connector cannot yet do. The production base URL and the read-one-booking call were not found in the public pages read, so no test or order call is listed.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.