API — Cloudexa

Base URL: https://cloudexa.dev/api/v1
Authentication: Bearer token
Response format: JSON

Endpoints

Routes currently exposed by API v1.

GET /api/v1 Public

GET /api/v1/health Public

GET /api/v1/me 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

Send your API token in the Authorization header.

cURL

curl https://cloudexa.dev/api/v1/me \
  -H "Authorization: Bearer clx_api_YOUR_TOKEN"

Example request

Fetch the hosting projects available to the token owner.

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();

Health check

The health endpoint is public and suitable for basic monitoring.

GET /api/v1/health

{
    "status": "operational",
    "database": "operational",
    "version": "v1",
    "latency_ms": 3
}

Security model

API v1 is limited to application-level resources and token management.

No shell execution

There is no endpoint for arbitrary host or application shell commands.

No Docker exec

The API does not provide direct container exec access.

Secrets excluded

Database passwords and encrypted credential values are not returned in normal API responses.

Rate limiting

API requests are subject to Cloudexa request limits.

Revocable tokens

Tokens can be removed from account settings when they are no longer needed.

Start using API v1

Create a token, then send it as a bearer token with your requests.

API index Create account