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
    • Make your first API call
    • Authentication & API Keys
  • Checkout
    • Overview
    • Create Checkout
      POST
    • Retrieve Checkout Status
      GET
  • Payment
    • Overview
    • Create Payment
      POST
    • Get Bank List - FPX
      POST
    • Retrieve Payment Status
      GET
  • Cards Payment
    • Overview
    • Payment Form
      • Request Payment
    • Host-to-Host Payment
      • Check Three D Secure
      • Charge Payment
      • Capture Authorized Payment
    • Request Refund
      POST
    • Unbind Token
      POST
    • Check Status
      GET
  • Payout
    • Overview
    • Inquire Beneficiary Account
    • Send Payout
    • Read Payout Status
    • Read Available Balance
  • Notification
    • Overview
    • Retry Notification
    • Setup Notification URL
    • Sample Notification - Global
    • Sample Notification - Cards
  • Technical Reference
    • Authentication & Integrity
    • Idempotency
    • Data Type
    • Order & Transaction Status
    • Postman Collection
    • Response Code
      • Error Code
      • Payout Response Code
      • Credit Card Acquirer Response Code
    • API Version
      • Create Checkout
      • Create Payment
      • Get Bank List - FPX
      • Retrieve Checkout
      • Retrieve Payment
      • Inquire Beneficiary Account
      • Send Payout
      • Read Payout Status
      • Read Available Balance
    • Signature
      • Signature - Global
        • Prepare Signature Component
        • Generating Signature
        • Validating Signature
        • Sample Code
      • Signature - Cards Payment API
        • Signature Component from Response Header
        • Signature from API Get Method
        • Sample Code
        • Signature Component from Request Header
  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-10-05 10:27:25
Previous
Credit Card Acquirer Response Code
Next
Create Checkout
Built with