Features Pricing API Docs
Log in Get started
Cloudexa API v1

Control Cloudexa from your own tools.

Read repositories, hosted projects, deployments and databases through a versioned JSON API using revocable bearer tokens.

API index Create account
GET /api/v1/health Live 
{
    "status": "operational",
    "database": "operational",
    "version": "v1",
    "latency_ms": 3
}
API basics

Small, versioned and JSON-first.

API v1 exposes read-only Cloudexa resources and API-token management without exposing shell execution, Docker commands or arbitrary deployment commands.

Base URL cloudexa.dev/api/v1
Authentication Bearer token
Format JSON
Endpoints

Available API routes

GET /api/v1 Public
GET /api/v1/health Public
GET /api/v1/me Token
GET /api/v1/repositories Token
GET /api/v1/hosting/projects Token
GET /api/v1/hosting/projects/:id Token
GET /api/v1/deployments Token
GET /api/v1/databases Token
GET /api/v1/tokens Session
POST /api/v1/tokens Session
DELETE /api/v1/tokens/:id Session
Authentication

Authenticate with a bearer token.

API tokens begin with clx_api_. Cloudexa stores only a SHA-256 hash of the full token.

Request 
curl https://cloudexa.dev/api/v1/me \
  -H "Authorization: Bearer clx_api_YOUR_TOKEN"
Response 
{
    "id": 1,
    "username": "example",
    "plan": "normal",
    "authentication": "token"
}
Tokens are shown once The raw token is returned only when it is created. Store it somewhere safe before leaving the creation response.
Example

Read your hosted projects.

cURL 
curl https://cloudexa.dev/api/v1/hosting/projects \
  -H "Authorization: Bearer clx_api_YOUR_TOKEN"
JavaScript 
const response =
    await fetch(
        "https://cloudexa.dev/api/v1/hosting/projects",
        {
            headers: {
                Authorization:
                    "Bearer " +
                    process.env.CLOUDEXA_TOKEN
            }
        }
    );

const data =
    await response.json();

console.log(
    data.projects
);
Security

Intentionally limited.

API v1 starts with the operations needed for integrations without directly exposing dangerous infrastructure controls.

No command execution The API does not expose shell or arbitrary command execution.
No Docker exec Containers cannot be accessed through an API exec endpoint.
Secrets excluded Database passwords and encrypted credentials are not returned.
Rate limited API clients are limited to a bounded number of requests per minute.

Start using API v1.

Create a token and connect your tools directly to Cloudexa.

API index Create account