Zuper developer hub

Build on the platform your crews already run on.

REST APIs, webhooks and an MCP server for every job, quote, invoice and crew in Zuper. If your team can do it in the app, your code can do it too.

Get your API key Browse the API

# Every account lives in one data center. Ask which.
curl https://accounts.zuperpro.com/api/config \
  -X POST \
  -H 'content-type: application/json' \
  -d '{"company_name":"your-company"}'

200 OK

{ "type": "success", "config": {
    "dc_country": "US WEST",
    "dc_api_url": "https://us-west-1c.zuperpro.com" } }

Three ways in

Pick how your code talks to Zuper.

REST API

JSON in, JSON out, standard status codes. Create jobs, move statuses, raise invoices, sync inventory.

Quick start

Webhooks

Get a call the moment a job closes or a quote is signed. History and retry built in, so nothing gets dropped.

Set up a webhook New

MCP server

Give Claude, Cursor or your own agent 290 tools to read the schedule, book jobs and chase invoices.

Connect an agent

Model Context Protocol

Your AI agent can run the dispatch board.

Point any MCP client at one URL. Sign in with your Zuper account, or pass your API key, and the agent can list jobs, check a tech's conflicts and reschedule, the same way your dispatcher would.

Claude
Cursor
Windsurf
OpenAI Agent Builder

https://mcp.zuperpro.com/sse

list_jobsFilter by status, tech, date
check_schedule_conflictIs Dave free at 2pm?
reschedule_jobMove it to Thursday
create_job_invoiceBill it when it closes
send_job_cardEmail the PDF to the customer

Stuck on something?

Post it in Discussions or reach our technical support team. Answers stay up for the next developer who hits the same wall.

Open Discussions