Isometric workshop hub with colorful cables linking an app tile, assistant orb, API key, and tablet into one system

Expand your capabilities

Hook up other software, assistants, and API keys to the same jobs, customers, and invoices your team already uses in Servicebay — without leaving the records behind.

API

When another system needs to read or update the same workshop records your team already uses, the HTTP API is the direct path.

Isometric stack of three cream workshop record crates with charcoal lids

Workshop records

Read and update the jobs, customers, quotes, invoices, calendar, stock, and services your workshop already keeps in Servicebay.

/api/v1 · cursor pagination · 100 requests per minute

Access and keys

Available to Pro or trial organisations. Create a key in the portal, then send it with each request. New keys are read-only for 90 days by default.

X-API-Key or Bearer · scope v2 read / write / delete (write does not include delete)

API documentation

Reference pages for people, a live API explorer, and text files that language models can load.

/docs · OpenAPI playground · /llms.txt · /llms-full.txt

Agents

Let an assistant or another app ask for access, then work with individual workshop records on your behalf.

Isometric figure beside a cream document card marked with a chain-link symbol

Sign-in for apps

Another program or an assistant can ask for permission, then use the same workshop data you already have.

OAuth 2.1 · PKCE required · MCP https://oauth.servicebay.io/mcp

Record links

A link an assistant can open so you can see one workshop record after you sign in.

/r/{org}/{entity}/{id} · example sb:tickets:12

Developer Portal

Sign in to manage keys, try calls, review connected apps, and check recent activity for your organisation.

Portal management needs an active admin account signed in with TOTP.

Isometric cream access key standing next to a charcoal-bordered access card