API Reference
Reference documentation for the Dash USD API.
Spec in progress
The Dash USD REST API is under development. The testnet faucet is already live (POST/GET /v1/faucet) — everything else below is a planned specification, not a live service — endpoints will go live with published keys and changelogs. Today, all verifiable DUSD data is already public on Dash Platform.
API Overview
Base URL
https://dashusd.org/v1 Authentication
All API requests will require authentication using an API key in the header:
Authorization: Bearer YOUR_API_KEY
Response Format
All responses will be returned in JSON format with the following structure:
{
"status": "success",
"data": { },
"meta": { }
} Endpoints
Faucet (Testnet — tDUSD)
/v1/faucet LIVE Dispense 3 tDUSD per request to a Dash Platform identity on testnet. No authentication — built for AI agents. 24h cooldown per identity, fair-use per-IP limit.
Request body: {"identityId": "YOUR_IDENTITY_ID"}
Success: {"success": true, "amount": 3, "symbol": "tDUSD", "identityId": "…", "transitionId": null} — transitionId is null today (the platform transfer op exposes no id yet); confirm drips by balance on the explorer.
Interactive UI: the tDUSD Faucet page. Implemented in the dashusd-api worker (see HANDOFF-FAUCET.md + HANDOFF-FAUCET-ACK.md).
/v1/faucet LIVE
Live faucet status — payout size, cooldown window, and whether the faucet is ok or drained. Poll this before requesting.
Response: {"success": true, "amount": 3, "symbol": "tDUSD", "cooldownHours": 24, "status": "ok"}
Supply
/supply Current DUSD total supply, straight from Dash Platform.
Today's equivalent: query the token directly on the Dash Platform Explorer.
/reserve Current reserve composition and collateralization ratio (Liquity BOLD, Federation custody).
Until live, reserve figures are published on the Proof of Reserves page.
Payments
/payment/request Create a payment request that settles in DUSD.
Merchant acceptance today works wallet-to-wallet — see the merchant guide.
Swaps
Rate Limits
The Free and Public API will implement rate limiting to ensure stability and fair usage:
(enterprise services available upon request)
- 10 requests per minute per API key
- 100 requests per hour per API key
- 1000 requests per day per API key
Rate limit information will be included in the response headers:
X-RateLimit-Limit: 100 X-RateLimit-Remaining: 95 X-RateLimit-Reset: 1625097600
Error Handling
The API will use conventional HTTP response codes to indicate the success or failure of an API request:
-
2xx
Success response indicating the request was processed successfully
-
4xx
Client error response indicating an issue with the request
-
5xx
Server error response indicating an issue on our end
Error Response Format:
{
"status": "error",
"error": {
"code": "invalid_request",
"message": "The request was invalid",
"details": { }
}
} Questions about the API? Reach the team through our public channels.
@SansbankDAO on X →