BodyShop Booster Integrations

March 2025 Inbound Matching API v1 POST /repair /This initial release included the ability to send information to BodyShop Booster and have it either create a new record or update an existing record automatically. April 2025 Inbound Matching API v1.5 POST

API keys can be created by admins inside the BodyShop Booster app. See Guide to Creating an API key as a BodyShop Booster Customer for more detail. This key needs to be sent in the header X-Booster-API-Key with each message.

BodyShop Booster is a CRM for repairers, with multiple tools allowing users to communicate better, attract more business, and cut down on admin costs. A customer record is unique by mobile phone number, unless they do not have a mobile number in which cas

Description Start here to learn how to use the Open APIs published by BodyShop Booster. Search this Space First Steps Right now, only our Inbound Matching API is available in general release. Check out our Getting Started page or jump straight into the de

Each Repair Status in BodyShop Booster is associated with a pair of dates - one Actual date and one Scheduled Date. These statuses and Actual dates are strongly coupled - it is not possible to change a status without also updating its associated Actual da

curl --location 'us-east-1.api.bodyshopbooster.com/open-api/v1/custom-fields' --header 'X-Booster-API-Key: {{access_key}}'

Example using system fields only : curl --location 'us-east-1.api.bodyshopbooster.com/open-api/v0.1/repair' \ --header 'X-Booster-API-Key: {{access_key}}' \ --header 'Content-Type: application/json' \ --data ' { "customerInfo": { "firstName": "Donald", "l

GET / calendars This endpoint is used to retrieve booking calendars defined per site within the BodyShop Booster system. It returns a list of available calendars that can be used when creating or updating bookings. Environment Region URL Documentation Sta

If you want to include custom fields in your message to the POST /repair endpoint first of all you will need to collect information about which custom fields have been created and are in use on a site by site basis. Calling the GET /custom-fields endpoint

The endpoint is the API endpoint used to check if the inbound matching API is up and running. It responds with the success message, "PONG" and status code 200 OK. GET "https://us-east-1.api.bodyshopbooster.com/open-api/v1/ping" Endpoint URLs: Environment

As an existing BodyShop Booster Customer You can simply create an API key in Admin → Integrations → Open API. Share this securely with your development partner, along with a link to this page. Instructions for creating an API key are under Guide to Creati

This is only possible if you have Admin access in BodyShop Booster. For Booster help call 800-867-6839 Screenshot 2025-03-07 at 17.53.39.png In this sidebar, you need to enter the following information: Name This is the name you want to identify this API

How the Inbound Matching process works The inbound matching API takes an inbound message and attempts to match it to an existing record inside BodyShop Booster, usually via the customer cellphone number. If we are able to do that, we will store the value

This is the first API we are making available. It is designed to be flexible, simple to use, and fault tolerant. Because of the way we match repairs to your GUID, after the initial data send, subsequent updates can be either be a complete resend of the or

It is possible to include a callbackURL and an externalLink value in the payload - both are optional. This allows you to establish links between matched records on both sides. For example, you can allow your own users to directly open the matching record

The message should be formatted as RFC 8259 compliant JSON and sent as a POST to the correct environment endpoint as specified in the documentation. An example POST is shown in the Example cURL commands page. The format broadly follows conventions and cod

You can use our Zapier integration to send data from Booster into external systems whenever certain events happen inside Booster. Currently, there is only one outbound message format available, the Booster Open API JSON schema as described for the Inbound

POST / bookings/ {bookingId} This endpoint is used to cancel an existing booking in the BodyShop Booster system. The booking to be cancelled is identified using the bookingId provided in the request path. An optional cancellation note can be included to c

This endpoint is used to create or update a repair record along with an associated booking in the BodyShop Booster system. The request accepts a JSON payload containing customer information, repair details, and booking data. Records are processed using Bo

This endpoint is used to create a conversation entry in the BodyShop Booster system. A conversation entry is an element within the Repair Record history - for example, a text message from a customer, a text message to a customer, the detail of an assignme

This can be used to send a JSON payload of customer and estimate / repair related information into BodyShop Booster. See How the inbound matching process works for more information on how this is handled on our end. Endpoint URLs: Environment Region URL D

PUT / bookings/{bookingId} This endpoint is used to update an existing booking in the BodyShop Booster system. It allows modification of booking-specific details such as start time, end time, and description. The booking to be updated is identified using

For each customer (ie bodyshop / MSO / entity): Have them generate an API key and share it with you For each repair record for each of those customers: Using the bodyshop’s API key, send a JSON message formatted according to the specification https://us-e