Skip to main content

Environments

Use the environment that matches your integration stage.
EnvironmentBase URLRecommended use
Staginghttps://staging.qash.aiTesting and pre-production validation
Productionhttps://app.qash.aiLive client traffic
The interactive reference lets you switch between staging and production before running a request.

Authentication

QASH currently documents two authentication models in this reference.
API areaAuthentication
Exchange rates / TRMNone
CardsAuthorization: Bearer <token>
Cards endpoints require a valid JWT. The primary card is identified from the authenticated token, so you do not need to send the card ID in most requests.

Request conventions

  • Send Content-Type: application/json for POST requests
  • Use numeric values for amounts
  • Read timestamps as ISO 8601 values
  • Request a fresh quote immediately before executing a transaction

Try the API from the docs

Every endpoint page includes the interactive Mintlify playground.
  1. Open an endpoint under API reference.
  2. Choose the server you want to call.
  3. Review or edit the example request.
  4. Click Run.
  5. Inspect the live response in the same page.

Current documented endpoints

MethodEndpointAuthenticationDescription
GET/api/v1/exchanges/assetsNoneReturn the assets currently supported for conversion
POST/api/v1/exchanges/quote/publicNoneReturn a real-time exchange quote with TRM applied
GET/api/v1/cards/statusBearer JWTReturn the current card status
GET/api/v1/cards/detailsBearer JWTReturn masked details for the primary card
POST/api/v1/cards/lockBearer JWTTemporarily block the primary card
POST/api/v1/cards/unlockBearer JWTReactivate a previously locked card
PATCH/api/v1/cards/limitBearer JWTUpdate the primary card spending limit
GET/api/v1/cards/balanceBearer JWTReturn the current card balance by currency
GET/api/v1/cards/transactionsBearer JWTReturn card transaction history

Quote validity

Quotes expire 30 seconds after they are created. If you are about to execute a transaction, request a new quote immediately before processing it.

Idempotency

x-idempotency-key is required for the following Cards operations:
  • POST /api/v1/cards/lock
  • POST /api/v1/cards/unlock
  • PATCH /api/v1/cards/limit
Use a unique UUID for each operation to prevent duplicate processing.