Cellulant
Cellulant is a pan-African payments platform headquartered in Nairobi, Kenya, operating across 35 African countries. Its flagship product Tingg is a single API that lets businesses collect online and offline payments, disburse to mobile money wallets and bank accounts, vend airtime and data, pay bills, and engage customers by SMS — interoperably across 350+ banks, mobile network operators, and card networks. Cellulant processes more than 4.5 million transactions per day for over 2,000 enterprise merchants and powers payments for ~220 million consumers. The Tingg platform exposes three primary developer-facing surfaces: Tingg Checkout 3.0 (Express, Custom and Direct Card), Tingg Payouts (the Beep global JSON endpoint), and Tingg Engage (transactional SMS). Cellulant ships official SDKs for PHP, Python, Node.js, .NET, JavaScript, plus a WooCommerce plugin.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Cellulant the way a machine reads it — 42 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cellulant scores 54.2/100 (developing), with a separate agent-readiness read of 29/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Cellulant's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cellulant/"
title="Cellulant on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cellulant.svg"
alt="Cellulant Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/cellulant/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cellulant/"
title="Cellulant on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cellulant/card.svg"
alt="Cellulant Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Cellulant
Each block below is one kind of artifact we hold for Cellulant. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cellulant Acknowledgement API
Acknowledge successful or partial payments back to the platform.
Cellulant Authentication API
OAuth 2.0 access token issuance for Tingg API calls.
Cellulant Custom Checkout API
Host-to-host checkout flow for merchant-controlled UX.
Cellulant Engagement API
Outbound SMS notifications and OTPs.
Cellulant Express Checkout API
Create hosted checkout sessions returning short and long URLs.
Cellulant Payments API
Post payouts, queries, validations, balances, and refunds.
Postman Collections 3
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Cellulant Tingg Checkout API
POSTMANCellulant Tingg Engage API
POSTMANCellulant Tingg Payouts API
POSTMANOpen Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCellulant Tingg Checkout Acknowledgement API
OPEN COLLECTIONCellulant Tingg Checkout Acknowledgement Authentication API
OPEN COLLECTIONCellulant Tingg Checkout API
OPEN COLLECTIONCellulant Tingg Checkout Acknowledgement Custom Checkout API
OPEN COLLECTIONCellulant Tingg Engage API
OPEN COLLECTIONCellulant Tingg Checkout Acknowledgement Engagement API
OPEN COLLECTIONCellulant Tingg Checkout Acknowledgement Payments API
OPEN COLLECTIONCellulant Tingg Payouts API
OPEN COLLECTIONScroll within the panel for all 10 ·
Arazzo Workflows 10
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Cellulant Charge with OTP Notification
Initiate a custom checkout, send the customer an OTP by SMS, then push the charge request.
ARAZZOCellulant Check Balance and Payout
Read the float balance, then disburse a payout only when the platform authenticated the balance query.
ARAZZOCellulant Checkout, Poll, and Acknowledge
Raise an Express Checkout, poll status until paid, then acknowledge delivery back to the platform.
ARAZZOCellulant Checkout with SMS Notification
Create an Express Checkout, then text the customer the short payment URL over Tingg Engage.
ARAZZOCellulant Custom Checkout, Charge, and Poll
Host-to-host flow — authenticate, initiate a custom checkout, push the charge prompt, then poll until the payment resolves.
ARAZZOCellulant Express Checkout and Poll Status
Authenticate, raise a Tingg Express Checkout, then poll the request status until the payment settles.
ARAZZOCellulant Get Bill and Pay
Fetch the outstanding bill for an account, then settle it with a Beep payout.
ARAZZOCellulant Payout, Query, and Refund
Disburse a payout, query its outcome, and reverse it with a refund when the payout did not succeed.
ARAZZOCellulant Post Payout and Query Status
Disburse a payout, then poll the Beep platform with queryPayment until the payout reaches a terminal state.
ARAZZOCellulant Validate and Post Payout
Validate the destination account, then post a mobile money or bank payout through the Beep platform.
ARAZZOScroll within the panel for all 10 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Cellulant Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Cellulant Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cellulant Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Cellulant API Rules
SPECTRALCellulant API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Tingg Express Checkout Request
JSON SCHEMATingg Payout Packet
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Cellulant — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 12
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 12 ·
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cellulant · machine-readable index on apis.io
This is an independent, third-party profile of Cellulant, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.