Cellulant Custom Checkout API
Host-to-host checkout flow for merchant-controlled UX.
Cellulant Custom Checkout API is one of 6 APIs that Cellulant publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Custom Checkout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.
This API exposes 3 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 3.0.0.
Requests are made against 2 base URLs: https://api.tingg.africa, https://api-approval.tingg.africa.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Cellulant Custom Checkout API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
An API key is passed in the header as apikey (ApiKeyAuth).
By default, every request must be authenticated.
ApiKeyAuth— Merchant apiKey issued in the Tingg integration dashboard.
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Host-to-host checkout flow for merchant-controlled UX.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ExpressCheckoutRequest (17 properties), Payment (9 properties), StatusResponse (7 properties), ChargeRequest (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Cellulant 5
Other APIs Cellulant publishes across the network.