API Overview

The BKey API is in active development. Endpoints and schemas may change without notice.

Base URL

https://api.bkey.id

Most endpoints require a Bearer token obtained via OAuth 2.1 client credentials or CIBA:

Authorization: Bearer <access_token>

Merchant-facing endpoints use a separate merchant API key scheme:

Authorization: Bearer mk_live_...

Successful responses return JSON:

{
  "id": "chk_abc123",
  "status": "pending",
  "amount": 9.99
}

Errors return an appropriate HTTP status with structured details:

{
  "success": false,
  "error": {
    "code": "invalid_argument",
    "message": "Amount is required"
  }
}

Code	Meaning
`200`	Success
`201`	Created
`400`	Validation error — check request body
`401`	Unauthorized — missing or invalid token
`403`	Forbidden — insufficient scopes
`404`	Resource not found
`409`	Conflict — duplicate or concurrent request
`429`	Rate limited
`5XX`	Server error

GET /.well-known/openid-configuration

Returns the OIDC discovery document with all supported endpoints, grant types, and signing algorithms.

GET /oauth/jwks

Returns the JSON Web Key Set for verifying BKey-issued JWTs. Keys use EdDSA (Ed25519).