Skip to main content

Airbag Documentation

The first software focused on drivers

Airbag helps you reduce accidents and the costs caused by poor driving habits.

Airbag Sync · Documentation

At Airbag we help reduce traffic accidents caused by human factors: phone use while driving, fatigue, and poor driving habits.

This documentation is intended for development teams that need to keep data in sync between their company systems and the Airbag platform. Below you will find the available ways to achieve it.

Author
Airbag Team
Version
1.0.8
Link
sync.airbagtech.io
Last updated
2023-06-05
Don't have an account yet?

Request your Airbag account through our contact form or by reaching out to [email protected].

Getting started

There are three ways to load and keep your information up to date in Airbag. Choose the one that best fits your team:

1. Manual

Upload and manage each resource directly from the Airbag Logistics platform. Ideal for small teams or early testing: locate the resource type (drivers, vehicles, admins, etc.) and create, edit or remove it from the UI.

2. Bulk upload (Bucle)

The Airbag team will provide a Microsoft Excel template with the exact format to upload your information in bulk. The template includes instructions; if you need additional help, email us at [email protected].

Resources available via bulk upload:

  • Drivers
  • Vehicles
  • Admins

3. REST API

A JSON REST API that is agnostic to your language of choice, designed for scalable and automated integrations. It requires basic programming knowledge and an API_KEY, which will be issued by one of our agents.

Unique identifiers

All endpoints assume the resources to be created, edited, read or removed have a unique ID, which you can define yourself when creating them.

Authentication

To consume the API you need an API_KEY. Once you have it, include it in the Authorization header of every request:

Authorization: apikey {{API_KEY}}

Required and optional fields

Every endpoint documents a table with its required and optional fields.

  • Required: must always be included; without them the operation cannot be completed.
  • Optional: you may omit them if they are not relevant. If you do send them, the server will validate their format according to the endpoint description table.

Report bugs or suggest improvements

Did you find a bug or have an idea to improve the system? Write to [email protected]. To speed up the process, include as much detail as possible (steps to reproduce, screenshots, logs, etc.); in some cases we may reply to request additional information.

Terms of use

Review our privacy notice and terms and conditions for the details of the service.