Connect Open311 GeoReport v2 (city 311)
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Open311 (open standard, each city hosts its own endpoint) 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.
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 Open311 (open standard, each city hosts its own endpoint) 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 Open311 (open standard, each city hosts its own endpoint). 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 Open311 (open standard, each city hosts its own endpoint) 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 Open311 (open standard, each city hosts its own endpoint)'s public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Open311 (open standard, each city hosts its own endpoint) 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: government utilities. How Open311 (open standard, each city hosts its own endpoint) gives access: You create the key yourself in your own account; no approval is needed. What it costs you: The Open311 spec does not state any fee; each city decides. Public read access is normally free.
Part 1. Get your key from Open311 (open standard, each city hosts its own endpoint)
Do this on your computer, in a new browser tab, signed in to Open311 (open standard, each city hosts its own endpoint).
- Ask your city's 311 or IT team (or the vendor that runs your 311 system) whether the city publishes an Open311 GeoReport v2 API.
- Ask for the endpoint address, the part before /services.json, and whether it supports JSON responses.
- Ask whether the endpoint needs a jurisdiction_id value (only needed when one endpoint serves several jurisdictions).
- Paste the endpoint address without https:// into Speakvora.
- Press Test connection; Speakvora reads the public service list at /services.json.
- To check one request, give Speakvora the service request number the resident was given when they reported the issue.
WARNING: If Open311 (open standard, each city hosts its own endpoint) asks which permissions to give, tick only the read-only ones: Read only: Speakvora only calls GET Service List and GET Service Request, which need no API key in the spec. 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 Open311 (open standard, each city hosts its own endpoint) in the box that says Find an app (1), or scroll down the list.
- Press Open311 GeoReport v2 (city 311). 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
1 box to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- Open311 endpoint address. The web address of your 311 system's Open311 API, without https:// and without a trailing slash or file name. Your 311 vendor or IT team publishes it (the spec shows api.city.gov/dev/v2).

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.
- Open311 (open standard, each city hosts its own endpoint) is asked for one harmless record, just to prove the key works. Nothing is changed in Open311 (open standard, each city hosts its own endpoint).

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 Open311 (open standard, each city hosts its own endpoint)), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Open311 (open standard, each city hosts its own endpoint) is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Open311 (open standard, each city hosts its own endpoint) when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Open311 (open standard, each city hosts its own endpoint). 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 Open311 (open standard, each city hosts its own endpoint), or Open311 (open standard, each city hosts its own endpoint) 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.
- Open311 (open standard, each city hosts its own endpoint) says you need a plan or approval: Every city hosts its own endpoint and not all offer JSON (XML is the only required format) or serve a single jurisdiction; if your endpoint needs a jurisdiction_id value or only returns XML, this connector will not work until your 311 vendor enables JSON. The spec defines only open and closed statuses. The API key in the spec is needed only for creating requests, which Speakvora never does.
- 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 311 confirmation emails to Speakvora
- Share your public 311 request lookup page link
Open311 (open standard, each city hosts its own endpoint)'s own instructions: https://wiki.open311.org/GeoReport_v2/
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 Open311 (open standard, each city hosts its own endpoint). 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 Open311 (open standard, each city hosts its own endpoint), or Open311 (open standard, each city hosts its own endpoint) 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: Open311 (open standard, each city hosts its own endpoint) says you need a plan or approval?
Every city hosts its own endpoint and not all offer JSON (XML is the only required format) or serve a single jurisdiction; if your endpoint needs a jurisdiction_id value or only returns XML, this connector will not work until your 311 vendor enables JSON. The spec defines only open and closed statuses. The API key in the spec is needed only for creating requests, which Speakvora never does.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.