Search by

servicem8 / servicem8-php

benford-servicem8

PHP SDK for the ServiceM8 API

Package info

github.com/servicem8/servicem8-php

Homepage

pkg:composer/servicem8/servicem8-php

Statistics

Installs: 103

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

v1.54.0 2026-10-25 03:05 UTC

README

fern shield php shield

The Servicem8 PHP library provides convenient access to the Servicem8 APIs from PHP.

Table of Contents

Requirements

This SDK requires PHP ^8.1.

Installation

composer require servicem8/servicem8-php

Usage

Instantiate and use the client with the following:

<?php

namespace Example;

use ServiceM8\ServiceM8Client;
use ServiceM8\ServiceTemplates\Requests\ServiceTemplateUpsertRequest;

$client = new ServiceM8Client(
    apiKey: '<value>',
);
$client->serviceTemplates->upsertServiceTemplate(
    'uuid',
    new ServiceTemplateUpsertRequest([]),
);

Environments

This SDK allows you to configure different environments for API requests.

The SDK defaults to the `Default_` environment. To use a different environment, pass it to the client constructor:

```php
use ServiceM8\ServiceM8Client;
use ServiceM8\Environments;

$client = new ServiceM8Client(
    token: '<YOUR_TOKEN>',
    options: [
        'baseUrl' => Environments::Staging->value
    ]
);

Available environments:

  • Environments::Default_

## Exception Handling

When the API returns a non-success status code (4xx or 5xx response), an exception will be thrown.

```php
use ServiceM8\Exceptions\Servicem8ApiException;
use ServiceM8\Exceptions\Servicem8Exception;

try {
    $response = $client->serviceTemplates->upsertServiceTemplate(...);
} catch (Servicem8ApiException $e) {
    echo 'API Exception occurred: ' . $e->getMessage() . "\n";
    echo 'Status Code: ' . $e->getCode() . "\n";
    echo 'Response Body: ' . $e->getBody() . "\n";
    // Optionally, rethrow the exception or handle accordingly.
}

Advanced

Custom Client

This SDK is built to work with any HTTP client that implements the PSR-18 ClientInterface. By default, if no client is provided, the SDK will use php-http/discovery to find an installed HTTP client. However, you can pass your own client that adheres to ClientInterface:

use ServiceM8\ServiceM8Client;

// Pass any PSR-18 compatible HTTP client implementation.
// For example, using Guzzle:
$customClient = new \GuzzleHttp\Client([
    'timeout' => 5.0,
]);

$client = new ServiceM8Client(options: [
    'client' => $customClient
]);

// Or using Symfony HttpClient:
// $customClient = (new \Symfony\Component\HttpClient\Psr18Client())
//     ->withOptions(['timeout' => 5.0]);
//
// $client = new ServiceM8Client(options: [
//     'client' => $customClient
// ]);

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

A request is deemed retryable when any of the following HTTP status codes is returned:

  • 408 (Timeout)
  • 429 (Too Many Requests)
  • 5XX (Internal Server Error)

The retryStatusCodes configuration controls which 5XX status codes are retried:

  • legacy (default): Retries 408, 429, and all >= 500
  • recommended: Retries 408, 429, 502, 503, 504 only (excludes 500 Internal Server Error to avoid retrying non-idempotent failures)

Use the maxRetries request option to configure this behavior.

$response = $client->serviceTemplates->upsertServiceTemplate(
    ...,
    options: [
        'maxRetries' => 0 // Override maxRetries at the request level
    ]
);

Timeouts

The SDK defaults to a 30 second timeout. Use the timeout option to configure this behavior.

$response = $client->serviceTemplates->upsertServiceTemplate(
    ...,
    options: [
        'timeout' => 3.0 // Override timeout at the request level
    ]
);

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!