Integrations
MoveBoard API (API keys)
Connect your own tools, automations and assistants to MoveBoard with an API key — what a key can do, who it acts as, limits, and where your developer finds every address.
- 5 min read
- Checked against MoveBoard
- For owners & admins
On this page
The MoveBoard API lets another system read and work your MoveBoard with a key you make — an automation service, your own software, your phone system, or an assistant. It can:
- Leads and orders — find them (by phone, email, name, number, status, dates), read one, create a lead, and change its status, salesperson, move date, arrival window, size, estimate type and your own id for it.
- Customers — find, read, add and change name, email and phone.
- Quotes — read the quote as the order window prices it (lines, totals, crew, trucks, hours, rates, valuation) and change the crew, trucks, rates and hours.
- Jobs — read the move days: date, arrival window, crew, trucks and status.
- Follow-ups — add one (title, due time, who it is for), list an order's, complete one.
- Notes — read and add office notes and crew-only notes (the foreman sees those in the Movers App).
- Calls and texts from another phone system — log them on the customer's order.
- Payments (read only) and users (to know who to assign).
Nothing is open until an admin makes a key.
Connecting Zapier? Use Settings › Integrations › Zapier instead: it makes the key for you and shows your Zaps — see Connect MoveBoard to Zapier.
Make a key
Go to Settings › Integrations › API keys (admins only).
- Name — what will use it, e.g. Zapier or our phone system.
- What it may do — Read only, or Read and change.
- Areas it may use — untick what the tool doesn't need.
- Acts as — the MoveBoard user the key works as.
- Press Make the key and copy it. It is shown only once; MoveBoard keeps only a fingerprint of it.
The key works in the branch you are in when you make it: new leads go there. A second branch gets its own key.
A key never expires. Revoke it on the same page and it stops at once. Each key shows its calls this month, its total, and when it was last used.
Who the key acts as
Everything a key does is done as the user you chose, with that user's permissions — exactly what that person could do on the screens. If they can't see other people's orders, neither can the key; if they can't archive, the key can't either.
- Every change goes through the same save the screens use, so the order log shows it, followed by via API key "Zapier" (the key's name).
- Your emails, texts, Workflows and notifications follow as they do when the office makes the change — a status change works like Change status on the Orders list, so your automatic messages and Workflows for that status go out, and a new lead gets your New lead notification and the new-lead webhook.
- Tip: make a user just for the key in Settings › Users & permissions, with only the permissions it needs, and choose that user. If that user is switched off, the key stops working.
New leads
A lead made by the API lands as a New order, the same as a lead sent by API: the customer is matched by email in the branch, the lead source by name (unknown → Other), and your assignment rules pick the salesperson — unless the request names one. The same lead sent twice is refused, so a tool that retries is safe. It can carry your own id for the order (kept as the Secondary ID), inventory items (matched to your item list by name), the pickup, the drop-off and the stops between them, in order. A move size named by its name must be one of yours, or the lead is refused with the reason.
Calls and texts from another phone system
If your company uses another phone system, it can send each call and text to MoveBoard:
- A call shows on the customer's order like MoveBoard's own phone calls — Inbound call from … — ended (2m 36s) — with the phone system's name after it, and on the Calls page. Its summary and the recording link go in an office note beside it. The recording stays a link: MoveBoard doesn't download it.
- A text is kept on the order the way the office logs things that happened elsewhere, with its words and the phone system's name. MoveBoard never sends it.
- They go on the newest order with the customer's number that the key's user can see. A call with no such order waits on the Calls page, where the office can attach it. Sent twice with the same id, they are filed once.
Limits
- 60 calls a minute and 150,000 a month per key (the month is the calendar month, UTC). That is plenty for an automation polling every minute all month.
- Every answer says how many are left. Over a limit, the tool is told how long to wait.
- There is no charge for API calls.
For your developer
Send them the key and this page: MoveBoard API documentation — every address with examples, errors and limits, and the OpenAPI file for tools that read it. Calls go from a server (not a web browser) with the key in the Authorization: Bearer header.
Related: the read-only partner data feed for an ad agency, and AI connections (MCP) for AI assistants that sign in as a person.
Related guides
- IntegrationsSend leads by APIFor your web developer or a lead seller — sending leads into MoveBoard from another system, what a lead needs, and how duplicates and limits work.
- IntegrationsWebhook — send leads to your own serverSend every new lead to your own server the moment it comes in, as signed JSON, with retries and a send log, and how your developer checks the signature.
- IntegrationsPartner data feedGive a partner you choose — your ad agency, an analytics service — a read-only key to your booked orders, with an example request for their developer.
- IntegrationsAI connections (MCP)Connect Claude, ChatGPT or another AI app to MoveBoard so it can answer questions about your company's data — and, if your company allows it, make changes you confirm — as you, with your permissions.
Still stuck? A person will help.
Open a ticket from Support inside MoveBoard, or email us — we usually reply within one business day.