What is the difference between the Internal API and the Customer API?

Gazoop provides two types of APIs depending on the level of access and control needed: the Internal API and the Customer API. Understanding the differences will help you choose the right integration method.

The Internal API is a more powerful, fleet-controlled API. It offers deeper system integration for developers building custom applications or tools for dispatching, reporting, or pricing manipulation.

The Customer API is a lightweight API available to all customers without approval. It is intended for basic tasks like creating a booking or checking its status.

Access Requirements

Internal API: Requires an API key, which can be managed under AdministrationAPI. These keys are controlled by the fleet operator.
Customer API: Requires only a login (usually a mobile number and PIN). No fleet approval or API key is needed unless the account is suspended.

Capabilities

Internal API: Supports advanced operations such as manipulating job pricing, creating custom booking logic, or syncing bookings with third-party systems.
Customer API: Allows basic booking features only. You can feed jobs into the system or retrieve limited live data, but you cannot manipulate core business rules.

Security

API keys used with the Internal API can be restricted to specific IP addresses or ranges for added protection. Always keep API keys and login credentials secure.

Example Use Cases

A company builds its own website to accept bookings and feeds them into Gazoop using the Internal API.
A third-party reporting dashboard pulls booking summaries from Gazoop using the Internal API.
A customer-facing app uses the Customer API to let passengers place bookings and view live updates.

For more technical details, see the official Gazoop documentation at docs.gazoop.com.