Skip to content
Cloud infrastructure/devops

hetzner.cloud

Hetzner Cloud sandbox and mock API

This is the official API documentation for the Public Hetzner Cloud. ## Introduction The Hetzner Cloud API operates over HTTPS and uses JSON as its data format. The API is a RESTful API and utilizes HTTP methods and HTTP status codes to specify requests and responses. As an alternative to working directly with our API you may also consider to use: * Our CLI program [hcloud](https://github.com/hetz Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
144
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-hetzner-cloud.slurry.io/v1/actions \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 144.

  • GET/actions
  • GET/actions/{id}
  • GET/certificates
  • POST/certificates
  • GET/certificates/{id}
  • PUT/certificates/{id}
  • DELETE/certificates/{id}
  • GET/certificates/{id}/actions
  • POST/certificates/{id}/actions/retry
  • GET/certificates/{id}/actions/{action_id}
  • GET/datacenters
  • GET/datacenters/{id}