Connect Buildium

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

Short answer: This connects your own Buildium 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 Buildium. 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 Buildium 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 Buildium. 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 Buildium 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 Buildium's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Buildium 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: real estate property. How Buildium gives access: You create the key yourself in your own account; no approval is needed. What it costs you: Buildium states the Open API requires a Premium subscription.

Part 1. Get your key from Buildium

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

  1. Sign in to Buildium as an administrator who has access to Application settings.
  2. Open Settings, then Application settings, and under System preferences click Api settings.
  3. Turn the Open API toggle on and click Save (this needs a Premium subscription).
  4. Open [[Settings > Developer Tools, and click Create API Key]].
  5. Enter the name Speakvora and a short description, then click Next.
  6. Tick only the read-only View access for Maintenance > Work Orders and Tasks, then click Next.
  7. Copy the client ID and the secret now; the secret is shown only once.

WARNING: If Buildium asks which permissions to give, tick only the read-only ones: Maintenance > Work Orders: View, Tasks > Tasks: View. 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 Buildium 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 Buildium. 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

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:

  1. API key client ID. Shown when you create the key under Settings > Developer Tools. The client ID is safe to share.
  2. API key secret (secret: it stays on this computer and is never shown again, only the last few characters). Shown only once when the key is created. If you lost it, delete the key and create a new one.
  3. 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. Buildium is asked for one harmless record, just to prove the key works. Nothing is changed in Buildium.
  3. Part 4: the green message under the buttons means it worked (1)

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 Buildium), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Buildium is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Buildium when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Buildium. 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 Buildium, or Buildium 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.
  • Buildium says you need a plan or approval: Buildium authenticates every request with two headers, x-buildium-client-id and x-buildium-client-secret. This spec format can send only one credential header, so it is marked unverified until the connector can send the secret header too. Endpoints, status values and key setup were read in Buildium's official developer docs.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

Buildium's own instructions: https://developer.buildium.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 Buildium. 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 Buildium, or Buildium 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: Buildium says you need a plan or approval?

Buildium authenticates every request with two headers, x-buildium-client-id and x-buildium-client-secret. This spec format can send only one credential header, so it is marked unverified until the connector can send the secret header too. Endpoints, status values and key setup were read in Buildium's official developer docs.

What if this happens: Still stuck??

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