AtlasOps REST API.

Use scoped API keys to integrate project, deployment, billing, and monitoring data with CI/CD systems, internal portals, and support tools.

Authentication

Create an API key from Settings. AtlasOps stores only a hash and shows a short prefix for recognition.

Authorization: Bearer atlas_xxxxxxxxxxxxxxxxx
Accept: application/json

List projects

Returns projects visible to the API key owner and their active organization membership.

GET /api/v1/projects

{
  "data": [
    {
      "id": "uuid",
      "name": "Web console",
      "slug": "web-console",
      "status": "ACTIVE",
      "framework": "Next.js",
      "productionUrl": "https://app.example.com"
    }
  ]
}

Errors and status codes

API responses are intentionally small and predictable for automation.

401 Unauthorized means the bearer token is missing, malformed, revoked, or expired.
403 Forbidden means the key is valid but lacks the required scope or organization membership.
404 Not Found means the resource does not exist in the active organization boundary.
422 Unprocessable Entity means request validation failed against a Zod schema.
429 Too Many Requests means the rate limiter rejected the request and the client should back off.

Webhook verification

Billing webhooks use the Razorpay signature header and the configured webhook secret.

POST /api/razorpay/webhook
X-Razorpay-Signature: <hmac-sha256>

{
  "event": "payment.captured",
  "payload": {
    "payment": { "entity": { "id": "pay_...", "amount": 9900 } }
  }
}