Skip to main content
The ENSC API is the merchant interface to the ENSC stablecoin platform: conversions through the ENSC converter (a pair token or Naira in, ENSC out, and back), ENSC transfers, balances, the bank directory and account resolution. It is built for server-side integration. Every call between your server and ENSC is protected by three independent layers on top of TLS: encrypted request bodies, Ed25519-signed writes, and responses sealed to your signing key. The official SDK, @ensc/sdk, applies all of them automatically, so the code you write looks like this:

What you can do

Conversions

Issue ENSC against USDC, USDT, CELO or a Naira bank transfer, and redeem it back. ENSC quotes, screens and authorises; your own wallet signs and broadcasts.

Transfers and balances

Build an unsigned ENSC transfer for your wallet to sign, and read balances of ENSC and the pair tokens.

Webhooks

Every conversion and payout outcome reaches your backend as a signed event, without polling.

Security

What the three layers protect, what each credential does, and why your wallet key never leaves your infrastructure.

How ENSC treats your keys

ENSC never holds or asks for a wallet private key. Every on-chain action (a conversion, a transfer) comes back as unsigned calldata, { from, to, data, value: "0", chainId }, that your own wallet signs and broadcasts. Conversions are additionally gated by a voucher that ENSC signs for the exact wallet, amounts and deadline you asked for.

Where to go next

2

Environments

Sandbox and Live: what the key prefix selects and which chain each environment runs on.
3

Going live

The checklist for moving to Live keys, the IP allowlist and the celo chain.

The API reference

The API reference tab of this site is generated from the OpenAPI document for API version 2026-09-15, the same schemas the API validates requests with. It has one page per operation: conversions, accounts and banks, transfer, balance, webhook endpoints, events, test data, the read-only credential listings, public keys and health. Each operation shows the @ensc/sdk call that makes it. The API also serves the same material itself:
There is no interactive playground. Every write must be encrypted and signed, and every successful response is sealed to your signing key, so a request typed into a browser cannot succeed. Use the SDK.