Skip to main content

Developer tools

A REST API for the workshop data you own

A documented REST API over the same records the workshop uses, so what you build on top of GarageSphere sees exactly what the front desk sees.

Start 14-day free trial Talk to us
  • RESTful and language-agnostic
  • API keys managed from your admin panel
  • IP whitelisting for locked-down access
An illustration of the REST API: a GET request to the jobs endpoint returning a 200 response with a job reference, status and total.

Where this fits in the job

  1. Booking
  2. Job card
  3. VHC
  4. Parts
  5. Invoice
  6. Payment

Underneath every step

Connected to the tools the trade already uses

  • DVLA
  • HaynesPro
  • Xero
  • QuickBooks
  • GSF Car Parts
Explore all integrations →

Build on your own workshop data

The API is the same data layer the product runs on, not an export of it.

Lightning Fast

Responses come from the live system, so an integration is never working from a copy that is an hour behind.

Secure by Design

Key-based authentication with optional IP whitelisting, and rate limits that keep one integration from affecting anyone else.

Developer Friendly

Predictable REST, JSON in and out, and worked examples in cURL, PHP and JavaScript to start from.

Comprehensive API Endpoints

The records an integration actually needs, addressable directly.

Work Orders

Read and create jobs, their status, labour and parts.

Customers

Customer records, contact details and their vehicles.

Vehicles

Vehicle records, specification and service history.

Complete API Control

Keys are generated with your account and managed from the admin panel. Regenerate one, restrict it, or switch it off entirely without raising a ticket and waiting for somebody to get back to you.

  • Generate and regenerate keys from the admin panel
  • Disable a key immediately if it is exposed
  • IP whitelisting to lock access to your own servers
  • Rate limits documented and tied to your plan
An illustration of the REST API: a GET request to the jobs endpoint returning a 200 response with a job reference, status and total.

Interactive Documentation

The reference shows request and response side by side, so the first call works. An API is only as good as the hour somebody spends trying to make it do something, and that hour is usually spent guessing at response shapes.

  • Every endpoint with its parameters and response shape
  • Worked examples in cURL, PHP and JavaScript
  • Error responses documented, not just the happy path
  • Language-agnostic, so anything that speaks HTTP will do
An illustration of technical data on a job: four repair operations with their book labour times, sourced from Haynes Pro and Autodata, totalling 4.1 hours.

Enterprise-Grade Security

The same controls that protect the workshop data protect the API over it, because it is the same data.

  • Key-based authentication over TLS
  • IP whitelisting for server-to-server access
  • Rate limiting for fair use and stability
  • Access auditable from your admin panel
An illustration of the GarageSphere app: the navigation sidebar beside today's job count and a list of jobs due, with times.

Get Started in Minutes

Four steps between having an account and having a working call.

1

Generate API Key

Your key is created with your account; find it under API Access.

2

Set IP Whitelist

Optionally restrict the key to your own server addresses.

3

Test Endpoints

Try a call against the documented examples.

4

Start Building

Work against live records in any language that speaks HTTP.

Frequently Asked Questions

API keys are automatically generated when you sign up for GarageSphere. You can manage your API key, regenerate it, or disable it entirely from the API Access section in your admin panel.

Yes, we implement rate limiting to ensure fair usage and system stability. The exact limits depend on your subscription plan and are clearly documented in the API documentation.

Absolutely! You can whitelist specific IP addresses to restrict API access. This is a great security feature for enterprise users who want to ensure API access only comes from their office or server locations.

Our API is RESTful and language-agnostic, but we provide code examples in cURL, PHP, and JavaScript. You can use any programming language that supports HTTP requests to integrate with our API.

It is part of the platform, with rate limits tied to your plan rather than a separate licence. If your integration needs more headroom than your plan allows, that is a conversation about limits rather than about buying access.

Breaking changes are the thing that makes an integration expensive to own, so they are avoided rather than shipped and announced. If something has to change in a way that would break existing calls, you hear about it before it happens, not from your own error logs.

Jobs, customers and vehicles, which is the spine most integrations need. It reads the same records the workshop is working in, so what your integration sees is what the front desk sees, with no export step in between.

Tell us what you are building

Read the endpoint reference, or talk to us about what you are building on top of GarageSphere.

Book a demo Start free trial
  • No credit card
  • Free onboarding
  • Unlimited users