API version v1 · Production-ready docs
SkyStack API provides a consistent interface for provisioning compute resources, managing infrastructure lifecycles, and automating deployment workflows across distributed environments.
SkyStack API
SkyStack API provides a single programmable interface for managing scalable cloud infrastructure and compute workloads. It is designed for engineering teams that need predictable automation, operational visibility, and reproducible infrastructure changes across environments.
The API exposes infrastructure objects as versioned resources so teams can create, update, and retire compute assets using standard HTTP operations.
Instead of manual console operations, integrations can control provisioning, scaling, and lifecycle behavior directly from CI/CD pipelines, platform tooling, or internal services.
Provision compute resources
Create instances, define sizing profiles, and attach network/storage settings from API requests.
Manage infrastructure programmatically
Apply configuration changes through idempotent calls and integrate with existing deployment workflows.
Monitor workloads
Retrieve status, utilization, and health signals to support alerting and runtime diagnostics.
Automate operations
Trigger repeatable infrastructure actions with scripts, schedulers, and event-driven orchestration.
POST /v1/compute/instances
Authorization: Bearer <token>
Content-Type: application/json
{
"name": "worker-eu-01",
"profile": "c4-standard",
"region": "eu-central",
"autoscale": true
}SkyStack API
SkyStack API uses API key authentication via Bearer tokens. Every request to protected endpoints must include a valid token in the Authorization header and must be sent over HTTPS.
Generate tokens from the SkyStack developer console. Tokens are scoped to your workspace and should be treated as secrets. Store them in environment variables or a secure secrets manager rather than source code.
Include your token using the Bearer scheme on every authenticated request.
GET /v1/projects HTTP/1.1
Host: api.skystack.dev
Authorization: Bearer YOUR_API_TOKEN
Accept: application/json
If you use cURL or an SDK, ensure that the header name remains exactly Authorization and that Bearer is followed by a single space and the raw token.
Only call the API via HTTPS. Plain HTTP can expose credentials in transit and is not supported for authenticated requests.
Security note: enforce TLS validation in your HTTP client and avoid disabling certificate checks in development scripts.
Rotate tokens on a defined schedule and immediately after any suspected exposure. During rotation, deploy the new token first, validate traffic, then revoke the old token.
A 401 Unauthorized response indicates missing, invalid, expired, or revoked credentials. Your client should treat this as an authentication failure and recover safely.
SkyStack API
Core REST operations for managing compute instances. All requests use JSON and require a bearer token in the
Authorization
header.
/v1/instances
Returns a paginated list of compute instances available to the authenticated workspace.
GET /v1/instances?page=1&limit=20
Authorization: Bearer <token>{
"data": [{ "id": "ins_123", "name": "worker-a" }],
"pagination": { "page": 1, "limit": 20, "total": 74 }
}/v1/instances
Creates a new compute instance with the selected region, machine type, and image.
POST /v1/instances
Authorization: Bearer <token>
Content-Type: application/json
{
"name": "worker-b",
"region": "us-east-1",
"size": "standard-2"
}{
"id": "ins_987",
"name": "worker-b",
"status": "provisioning",
"created_at": "2026-03-19T10:22:44Z"
}/v1/instances/{id}
Fetches full details for a single instance by ID, including metadata and networking state.
GET /v1/instances/ins_123
Authorization: Bearer <token>{
"id": "ins_123",
"name": "worker-a",
"status": "running",
"ip": "10.24.8.12"
}/v1/instances/{id}
Permanently removes an instance. The operation is idempotent and returns no body on success.
DELETE /v1/instances/ins_123
Authorization: Bearer <token>HTTP/1.1 204 No ContentSkyStack API
Practical implementation details for production integrations. Answers are intentionally concise and optimized for quick lookup.