REST API (api_1.0) using Basic Authentication

API & SDK
1

Originally posted by Mark Kevin Virena

Hi ServiceM8 Support,

We are integrating ServiceM8 with an external automation platform (n8n) and require access to the public REST API (api_1.0) using Basic Authentication.

Currently, our account only allows creation of Plugin API Keys (smk-), which do not authenticate against the REST API.

Could you please enable REST API access for our account or advise how to generate a REST API key?

Thanks.

2

Hi there,

ServiceM8 no longer supports Basic Authentication (username and password) for REST API access. You’ll need to use one of the current authentication methods instead.

For integrating ServiceM8 with n8n (or any automation platform), you have two options:

Option 1: API Keys (Recommended for your use case)

You can create API Keys directly in your ServiceM8 account without needing a Developer account. Here’s how:

  1. Go to Settings → API Keys in your ServiceM8 account
  2. Create a new API key and give it a descriptive name
  3. Configure the access level (Read Only or Full Access)
  4. Use the key in your n8n requests by including it in the X-API-Key header

Example:

curl -X GET "https://api.servicem8.com/api_1.0/company.json" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json"

API Keys work with all REST API endpoints at https://api.servicem8.com/api_1.0/.

Option 2: OAuth 2.0 (For more advanced integrations)

If you’re building a public integration or need more advanced features, you can use OAuth 2.0. However, for connecting n8n to your own ServiceM8 account, API Keys are simpler and more appropriate.

About Plugin API Keys (smk-)

The “Plugin API Keys (smk-)” you’re seeing are from an older system and are not used for REST API authentication. These legacy keys have been replaced by the current API Key system available in Settings → API Keys.

Thanks,
Cody