Use the API & webhooks

Create a key from API keys in the dashboard. Save it when shown and send it as a bearer token. The key acts for your organization; keep it in your tool’s secret storage.

Use the API reference for the current base URL, endpoint shapes, limits, and errors. Revoke a key you no longer need or suspect has been exposed.

The API can read servers, usage, orders, invoices, and subscriptions. Supported actions include reboots, snapshot creation and restoration, and webhook endpoint management.

Ordering, rebuilding, server removal, and credential reveal are performed in the dashboard. Use the documented endpoints rather than relying on internal application requests.

Handle non-success responses, respect rate limits and Retry-After, and verify operation state before retrying a write. Snapshot creation and restores take time to complete.

Owners register public HTTPS endpoints under Webhooks. Save the signing secret when the endpoint is created.

Validate the x-datahall-signature header against the unmodified request body and check the timestamp before accepting an event. The API reference describes the signature format and event payloads.

Treat event IDs as deduplication keys. Return a successful response promptly after safely accepting the event, and perform longer work asynchronously. Delivery retries can cause duplicate events.

An endpoint with repeated delivery failures can be disabled. Review its state in the dashboard, investigate the destination, and contact Support if you need help restoring delivery.