Every console action is an API action
ScodyX Cloud is built API-first. If you can click it in the console, you can script it — provisioning, scaling, DNS, backups and billing all run through the same endpoints.
Built as an API with a console on top
That ordering matters: it means the API is never a second-class citizen bolted onto a UI after the fact.
Console parity
Every action available in the ScodyX Cloud console — creating an instance, attaching storage, rotating a credential — is backed by the same API endpoint. The console is a client of the API, not a separate system.
Scoped API keys
Generate API keys per project with read or write scope. Keys are shown once, stored hashed, and can be revoked instantly from the console without affecting other keys on the account.
SSH key management
Upload public keys to your account and select them at provisioning time so new instances come up with key-based access already configured — no manual copying after boot.
Webhooks
Subscribe to lifecycle events — instance state changes, backup completion, billing events — and receive signed HTTP callbacks so your own systems can react without polling.
Infrastructure-as-code posture
The API is stable and typed enough to script against directly with curl or any HTTP client, and maps cleanly onto Terraform-style declarative workflows where resources are defined, diffed and applied.
Rate limits and idempotency
Requests are rate-limited per key to protect the platform for everyone. Mutating endpoints accept idempotency keys so retried requests do not create duplicate resources.
What a request looks like
These snippets show the shape of the interaction, not a guaranteed live schema — check the reference documentation for exact fields and endpoints.
curl — illustrative shape
curl -X POST https://api.scodyx.cloud/v1/instances \
-H "Authorization: Bearer $SCODYX_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 8f0c2c-provision-01" \
-d '{
"product": "cloud-compute",
"plan": "cc-4c-8g",
"region": "eu-central",
"ssh_key_id": "sk_9x2q...",
"hostname": "app-01"
}'shell — illustrative automation
#!/usr/bin/env bash set -euo pipefail id=$(curl -sf https://api.scodyx.cloud/v1/instances \ -H "Authorization: Bearer $SCODYX_API_KEY" | jq -r '.instances[0].id') curl -sf -X POST \ "https://api.scodyx.cloud/v1/instances/$id/snapshots" \ -H "Authorization: Bearer $SCODYX_API_KEY" echo "Snapshot requested for $id"
Keys, scopes and revocation
- API keys are created and managed per project from the console, never issued by support over email or chat.
- Each key carries an explicit scope (read or read/write) so integrations only get the access they need.
- Revoking a key takes effect immediately and does not require rotating other keys on the account.
- SSH public keys are stored against your account and attached to instances at creation time.
- Webhook payloads are signed so your receiving endpoint can verify they originated from ScodyX Cloud.
Start building against the API
The reference documentation covers authentication, every resource endpoint, and webhook payload shapes.