Welcome to the Gozem Developer Platform.
Gozem is a super app built for Africa, offering a growing ecosystem of services across transportation, logistics, and payments. Our APIs let approved partners access and extend Gozem’s platform capabilities programmatically and securely, bringing Gozem services into their own systems.
A multi-service platform
The platform exposes Gozem’s capabilities as a set of independent REST APIs, each its own service with its own endpoints and resources. You integrate only the services you need, and more services are being added over time. Every service shares the same platform foundation, so once you understand how authentication, environments, and the common conventions work, that knowledge carries across all of them.
How the platform is organized
The platform is a standards-based REST API ecosystem. Behavior is predictable, resources follow consistent models, and integration contracts stay stable across versions. A few structural ideas run through everything you will read here.
REST endpoints. Every action is an HTTP request against a versioned endpoint. Resources follow standard conventions for listing, retrieving, creating, and updating.
OAuth2 and scoped access. You authenticate with OAuth2 client credentials and receive a bearer token. Each API client is granted access to specific services, specific endpoints, and optionally a fixed set of source IP addresses. An API key is also available for server-to-server integrations; the Authentication page explains when to use each.
Consistent data models. Request and response shapes are stable and documented, so you can rely on the same field names and structures everywhere.
Two environments. Sandbox and production are fully separated, each with its own base URL, credentials, and data. You build and test in sandbox, then move the same integration to production by changing configuration. See the Environments & Access page for the details.
Where to start
- Read Environments & Access to understand sandbox versus production and to set up your API client and credentials in the Partner Portal.
- Read Authentication to exchange those credentials for a token.
- Review API Basics for the conventions every service shares: versioning, pagination, and rate limiting.
- Then open the section for the service you are integrating and follow its quickstart.