API reference
API reference
Interactive request, response, schema, and code examples generated from OmniPay's OpenAPI contract.
The production API uses:
https://omnipay.page/apiEvery endpoint below is generated from OmniPay's versioned OpenAPI 3.1 contract.
Download the OpenAPI document →
Deposits
Withdrawals
Authentication
All endpoints use Authorization: Bearer <api-key>. H2H creation, H2H status,
and H2H verification additionally require X-Omni-Timestamp and
X-Omni-Signature.
The interactive schema lists those headers, but the signature depends on the exact outgoing body. Generate it in your backend immediately before sending the request.
Response conventions
Amounts are BDT decimal strings. Timestamps are UTC. Error responses use the
stable error.code envelope, and every response includes X-Request-Id for
support and debugging.