How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

DOKU Checkout API

DOKU-hosted checkout page (non-SNAP).

DOKU Checkout API is one of 6 APIs that DOKU publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 2 base URLs: https://api.doku.com, https://api-sandbox.doku.com.

1 operations 1 paths 2 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.doku.com
Authentication
API Key, API Key, API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 4

DOKU Checkout API declares 4 security schemes for authenticating requests. An API key is passed in the header as Signature (CheckoutSignature). An API key is passed in the header as X-SIGNATURE (SnapAsymmetric). An API key is passed in the header as X-SIGNATURE (SnapSymmetric). It accepts HTTP bearer tokens (JWT) (SnapBearer).

  • CheckoutSignature — Non-SNAP scheme. Send Client-Id, Request-Id, Request-Timestamp and Signature headers. Signature = "HMACSHA256=" + base64(HMAC-SHA256( clientSecret, componentSt…
  • SnapAsymmetric — SNAP access-token signature. Asymmetric SHA256withRSA over "clientId|X-TIMESTAMP" using the merchant private key. Sent with X-CLIENT-KEY and X-TIMESTAMP.
  • SnapSymmetric — SNAP transaction signature. Symmetric HMAC-SHA512 over "HTTPMethod:EndpointUrl:AccessToken:Lowercase(HexEncode(SHA-256(minified body))):X-TIMESTAMP" using the…
  • SnapBearer — SNAP B2B access token from /authorization/v1/access-token/b2b.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Checkout 1

DOKU-hosted checkout page (non-SNAP).

POST
/checkout/v1/payment
Generate a DOKU-hosted checkout page
createCheckoutPayment body → 200400401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are CheckoutPaymentRequest (3 properties), CheckoutPaymentResponse (2 properties). Each schema is shown below with its type and property counts.

CheckoutPaymentResponse
object
2 properties
CheckoutPaymentRequest
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

doku-checkout-api-openapi.yml Raw ↑

Other APIs DOKU publishes across the network.

DOKU Access Token API
DOKU Direct Debit & e-Wallet API
DOKU Payout API
DOKU QRIS API
DOKU Virtual Account API
Where this information came from

This is an independent, third-party profile of DOKU Checkout API, 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.