How to Get ServiceM8 API Access (and What You Can Build)

Two routes into the ServiceM8 API

Before anything else, decide which of these you are actually doing, because the access path differs:

• A private connection for your own account. You want your ServiceM8 talking to your accounting system, your reporting, or an internal tool. This is the simpler route and the one most businesses need.
• A published add-on for other businesses. You are building something other ServiceM8 users will install. That goes through OAuth and a ServiceM8 review process before it can be listed.

People searching for a ServiceM8 API key are almost always in the first group, and are often told about the second, which is why the answers online feel more complicated than the situation warrants.

Getting access, step by step

1. Register for developer access through the ServiceM8 developer area, using an account the business controls.
2. Choose your integration type, private connection or distributed add-on, based on the section above.
3. Collect your credentials. For a distributed add-on this is an OAuth client id and secret. For a private connection the setup is lighter.
4. Select the scopes the integration needs. Grant read access where you only read, rather than granting everything by default.
5. Test against a non-production account if you can. Job and invoice data is not something you want to experiment on live.

What the ServiceM8 API lets you do

The API is organised around the job, which mirrors how the product works:

• Jobs, create, read and update, including status and scheduling
• Clients and contacts, keep customer records in step with another system
• Job materials and labour, the lines that make up what gets invoiced
• Staff and job allocations, who is assigned to what
• Job activity and timing, useful for payroll and productivity reporting
• Attachments, photos, signatures and documents captured on site
• Queues and categories, the workflow structure the office actually runs on

That combination is why ServiceM8 integrations tend to be about more than invoicing. Photo and signature capture flowing into a compliance record, or job timing feeding payroll, are common requests.

Add-ons, webhooks and the job card

Two capabilities are worth knowing about because they change what is possible.

Webhooks. ServiceM8 can notify your system when something changes rather than making you ask repeatedly. This matters more than it sounds. Polling a busy account for changed jobs is slow, wasteful and hits limits. Event driven updates are the difference between an integration that feels instant and one that lags.

Add-ons that extend the job card. A ServiceM8 add-on can put your own content and actions directly into the job screen the field team already uses. That is a genuinely useful pattern, because it means staff do not have to open a second app to do the extra step.

When to bring in a developer

ServiceM8 is a well built product with a sensible API. Most of the projects that come to us are not there because the API is difficult, but because the standard connector stops short of what the business needs and nobody wants to keep bridging the gap by hand.