Use the OpenAPI document
Download the public developer API contract and generate a client.
Download the public contract
Download OpenAPI JSON or OpenAPI YAML. Both are generated from the App's public contract.
The API reference covers the public operations for Spaces, domains, DNS records, Compliance, and Marketing. Use the public contract for code generation and client examples.
Connect and authenticate
Use https://app.dashio.net as the API origin. Create a Space-scoped API token and send its opaque dashio_ secret using Authorization: Bearer <token>. Every public operation requires a token and its documented scope.
The contract declares each operation's required permission in x-required-scopes and its credit cost and applicable gateway budgets in x-rate-limit. The token's Space and product access still apply.
Generate or write a client
Import either download into your OpenAPI-compatible tool and configure its bearer credential from a server-side secret. Use stable operationId values when generating methods. Keep the domain name, record UUID, and list cursor as distinct identifiers; do not substitute one for another.
The generated reference includes cURL, JavaScript, TypeScript, Python, PHP, and Go HTTP-client examples. Configure credentials through the environment and replace URL or schema placeholders before running them. No Dashio SDK is required.
Examples run on the server and read DASHIO_API_TOKEN from the environment. They use bounded timeouts, avoid redirecting credentials, and report HTTP failures with request identifiers. Run examples in a private terminal and keep credentials and response data out of shared logs.
The reference labels examples supplied by the contract and illustrations generated from a schema. Inspect the HTTP status and content type before decoding a response.
Design reliable automation
Use paginated reads, bounded request timeouts, and the documented quota headers. On 429, honor Retry-After.
For write operations, follow the request preconditions documented for that endpoint. After a conflict or uncertain result, read the current resource and compare its state with the intended change before trying again.
The API returns X-Request-Id for troubleshooting. Record this identifier with the HTTP status and the response's data.code when available.
Scope and future integrations
Registration, renewal, transfer, paid add-ons, automated reseller purchases, and outgoing webhooks are outside this release. Future reseller orders need payment verification before registrar fulfillment; a saved payment method alone is not proof of payment.
The public HTTP contract is the intended foundation for a future MCP server and Terraform provider. Neither integration is available in this release. Stable resource identifiers, explicit scopes, pagination, and resource reads help those clients converge on the same API later.
The existing /api/v1/ prefix prepares for versioning. Initial contracts can change without a backwards-compatibility promise. Review the current definition when updating an integration.
Was this helpful?