Documentation

Build on Century

Century is a Nigerian fintech platform for wallets, collections, virtual top-ups and bill payments. This portal documents every capability the platform actually exposes today — with real request shapes, real error codes and honest notes about what is not built yet.

How the API works

Century's API is a typed RPC surface. Each capability is a server function reachable at /_serverFn/<name> over HTTPS, plus a small set of raw HTTP routes under /api/public/* for webhooks and machine callers. Requests and responses are JSON; money amounts are in naira.

  • All traffic is HTTPS-only and same-origin from the Century apps.
  • Authentication is a Supabase-issued bearer token belonging to a real user account.
  • Authorization is enforced in the database with row-level security — the API never trusts the client.
  • 97 documented operations across 9 products.

A first call

Read the signed-in user's wallet:

cURL
curl -X GET https://centuryvtu.com/_serverFn/getWalletState \
  -H "Authorization: Bearer $CENTURY_ACCESS_TOKEN"

Products

What Century does not do (yet)

Read this before you design around it
There is no public partner API programme, no self-service API keys and no outbound webhooks to third-party systems. The operations documented here are the same ones the Century apps call, authorised as the signed-in user. Anything not listed in this portal does not exist — if a feature you need is missing, ask support rather than assuming an undocumented endpoint.