API Reference
The ZevCloud API lets you programmatically manage projects, services, deployments, and more.
Base URL
https://api.zevcloud.net/v1Authentication
All API requests require authentication via an API key:
bash
curl https://api.zevcloud.net/v1/projects \
-H "Authorization: Bearer sk_live_your_api_key"Generate API keys from Dashboard → Settings → Security → API Keys.
API keys are scoped to a team — all operations use the team context associated with the key.
Request Format
- Content-Type:
application/json - Team ID: Automatically set from the API key (or pass
x-team-idheader for ZevID token auth)
Response Format
All responses are JSON. Successful responses return the data directly:
json
{
"id": "uuid",
"name": "My Project",
"slug": "my-project"
}List endpoints return paginated data:
json
{
"data": [...],
"pagination": {
"page": 1,
"limit": 25,
"total": 42,
"pages": 2
}
}Error responses:
json
{
"statusCode": 400,
"message": "Validation failed",
"timestamp": "2026-03-28T12:00:00.000Z",
"path": "/v1/projects"
}Rate Limiting
| Endpoint | Limit |
|---|---|
| Most endpoints | 100 requests / minute |
| Deploy triggers | 10 / minute |
| Auth endpoints | 10 / minute |
Rate limit headers are included in every response:
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset
Endpoints
| Resource | Endpoints |
|---|---|
| Projects | CRUD for projects |
| Services | Create, manage, deploy services |
| Deployments | Trigger and monitor deployments |
| Domains | Custom domain management |
| Environment Variables | Service-scoped env vars |