DOKU Malaysia API Reference
Home
Products
Products
  • Checkout
  • Payment
  • Cards Payment
DOKU Docs
Home
Products
Products
  • Checkout
  • Payment
  • Cards Payment
DOKU Docs
  1. Technical Reference
  • Introduction
  • Getting Started
    • Create Account
    • Authentication & API Keys
    • Make your first API call
  • Checkout
    • Overview
    • Create Checkout
      POST
    • Retrieve Checkout Status
      GET
  • Payment
    • Overview
    • Create Payment
    • Get Bank List - FPX
    • Retrieve Payment Status
  • Cards Payment
    • Overview
    • Payment Form
      • Request Payment
    • Host-to-Host Payment
      • Check Three D Secure
      • Charge Payment
      • Capture Authorized Payment
    • Request Refund
    • Unbind Token
    • Check Status
  • Notification
    • Overview
    • Setup Notification URL
    • Retry Notification
    • Sample Notification - Global
    • Sample Notification - Cards
  • Technical Reference
    • Authentication & Integrity
    • Idempotency
    • Data Type
    • Order & Transaction Status
    • Postman Collection
    • Response Code
      • Error Code
    • API Version
      • Create Checkout
      • Create Payment
      • Get Bank List - FPX
      • Retrieve Checkout
      • Retrieve Payment
    • Signature
      • Signature - Global
        • Signature
      • Signature - Cards Payment API
        • Signature Component from Request Header
        • Signature Component from Response Header
        • Signature from API Get Method
        • Sample Code
  1. Technical Reference

API Version

API-Version is used to control which version of the API behavior and contract is applied to a request.
By specifying an API-Version in the request header, merchants can continue using a stable API contract without being affected by new features, new parameters, or changes to existing parameters. Any enhancements or breaking changes will only apply to newer API versions.
This ensures:
Backward compatibility for existing integrations
Safe rollout of new features and parameter changes
Full control for merchants to upgrade when ready
Merchants who do not update their API-Version will continue to receive the same behavior as their current implementation.
API-Version defines the version of a specific API being used in the request.
Each API (e.g. Checkout API, Payment API) maintains its own versioning lifecycle. Changes such as new parameters, modified parameters, or behavior updates apply only to the specified API and version.
Modified at 2026-02-02 03:38:06
Previous
Error Code
Next
Create Checkout
Built with