Supermove API Guide for Moving Companies

One-line verdict: A real but narrow API built around one object — the project — with keys Supermove emails you by hand, plus a genuinely easy lead door for your website. Openness: 3 / 5 — rated 3 because Supermove documents project read and create/update endpoints with vendor-issued credentials, while everything beyond projects, and any rate limit or plan rule, is undocumented.

The connection that works

Rung 1 — Direct connection, projects only. Supermove’s data model, in its own words: “a project consists of many job objects where each job represents a single segment of work for a crew.” Its public API documentation covers exactly that shape. Two endpoints are documented to the ground: Get Project — retrieve all attributes of one project by its ID — and Sync Project — send a project keyed on its identifier and Supermove creates it if there’s no match, updates it if there is; the payload carries the jobs array (type, status like BOOKED, date, crew size, locations, notes) and the customer (name, phone, email) nested inside. Create and Update Project endpoints are also listed on the API overview; their individual pages weren’t read in our pass, so they sit at overview level. Jobs and customers have no standalone endpoints — they exist only inside a project.

Sign-in is an API key plus your organization ID — and here is the gate, in the vendor’s own documentation: the ID “is provided alongside your API key (via email).” There is no key button in the app. Supermove issues credentials by hand.

The second surface is the easy one: Supermove’s help centre documents inbound lead endpoints — a Developer API (New Lead) endpoint and a simpler Standard Website endpoint. Your website POSTs a JSON payload to a unique per-account URL (copied from Company Settings → Lead Providers); “no further API keys or organization identifiers are needed.” The developer payload creates a project carrying the client, jobs with locations, project type, tags, and survey data (payloads with unconfigured values are rejected). For most moving companies, this door — website lead becomes a ready-made project — is the whole ballgame.

Outbound signals exist too, as automations, not API subscriptions: Supermove Automations offer an Invoke Webhook action that can fire on documented events — Project Created, Job Created, Job Completed, Quote Sent/Accepted, Confirmation events, tag changes, SMS Received, even Storage Autopay Failed/Succeeded. That’s an in-product automation webhook; this page publishes it as exactly that, not as an API webhook system. No rate limits and no plan gate for API access are stated in any vendor source we found.

Bridge apps: no native Supermove app exists on Zapier or Make. The working bridge pattern (documented in a third-party integration guide, labeled as such) is Supermove’s own Invoke Webhook firing into Zapier’s generic Catch Hook — the trigger is Supermove’s webhook, the Zapier side is plumbing.

Can automate

• Speed-to-Lead — the strongest fit: a website lead lands as a complete project — client, jobs, locations, survey data — through the documented lead endpoints, no key negotiation required.
• Project sync — a project created or updated in your CRM can be synced into Supermove (and read back) through the public API, once the emailed key arrives.
• Completion signals out — Job Completed and Project Created automation webhooks can start the next step in your other tools — including, per the documented third-party pattern, a review request through a reviews tool.
• Quote and confirmation events — Quote Sent/Accepted and confirmation events are documented automation triggers for follow-up sequences.

Can’t automate

• Standalone jobs or customers — no endpoints. They travel inside projects only; per-job or per-customer API work is not documented.
• Invoices or payments — no endpoints. The only payments trace in vendor docs is the Storage Autopay Failed/Succeeded automation events — notifications, not a payments API.
• Inventory through the API — UNVERIFIED. The overview mentions inventory as an API use; no endpoint was read in our pass.
• Create/Update Project detail beyond the overview listing — UNVERIFIED (Sync and Get are the endpoints actually documented page by page).
• Rate limits and any plan gate — UNVERIFIED. None are stated in vendor sources.
• A native Zapier or Make app — none exists; the bridge is Supermove’s outbound webhook into generic catch-hooks.

Hidden gate: There’s no key button in the app — Supermove has to email you your API key and set you up before the real API works. The lead endpoints skip that gate entirely; the project API does not.

Build fit — what this platform supports well

• Speed-to-Lead — excellent, and the reason this page scores a 3 instead of lower: the lead-to-project door is documented, keyless, and complete.
• Project handoff — CRM-to-Supermove project sync is the API’s documented purpose.
• Invoice Chase / AR — not here: no invoice or payment endpoints; the chase runs against your accounting records, with Supermove events as signals.
• Review Engine — like every platform here, Supermove has no verified reviews API — its review flow is a webhook into a third-party reviews tool — so the review ask runs on our system triggered by a job-completion signal, which its Job Completed webhook supplies.

What this means for your shop

If you run a moving company on Supermove, your highest-value connection is also your easiest: website leads becoming projects, automatically, through a URL you copy out of settings today. The deeper project sync is real but hand-provisioned — request the key early — and anything about invoices, payments, or standalone jobs is outside the documented surface, whatever a salesperson implies.