canonical: https://jentic.com/apis/clever-cloud.com/clever-cloud

# Clever-Cloud API

Jentic publishes the only available OpenAPI specification for Clever-Cloud API, keeping it validated and agent-ready. The Clever-Cloud API is the public management interface for the Clever Cloud platform-as-a-service, exposing operations for application deployment, environment configuration, log streaming, billing, organization membership, and add-on provisioning. It covers more than 320 endpoints spanning compute applications, scalability rules, networking, GitHub integrations, OAuth tokens, and consumer accounts. Agents can use it to deploy and operate hosted services, retrieve logs, manage drains, and orchestrate tenant-level billing without touching the Clever Cloud console.

## For AI agents

Deploy and operate applications on Clever Cloud - manage application lifecycles, environment variables, log drains, add-ons, and billing across organizations.

## Scope

Does not handle frontend hosting CDN edge configuration, container image building, or end-user authentication for hosted apps - use for Clever Cloud platform management only.

## Capabilities

- Deploy and redeploy applications and read live deployment status across environments
- Stream and chunk-fetch application logs and configure long-lived log drains
- Manage environment variables and runtime configuration on a per-application basis
- Provision and bind add-ons such as databases, caches, and message brokers to applications
- Administer organization members, roles, and consumer OAuth credentials
- Retrieve invoices, payment methods, and billing balances for an owner
- Wire GitHub repositories to Clever Cloud for source-driven deploys

## Use cases

### Application Deployment Automation

Automate application deployments on Clever Cloud, including triggering builds, redeploying GitHub-linked apps, and updating environment variables before each release. The API exposes deployment endpoints, environment variable management, and event streams so an external system can run a full deploy pipeline without using the Clever Cloud console. Typical setup takes a few hours of integration work for a single environment.

Example prompt: Redeploy the application with appId 'app_abc123' using the GitHub-linked source and verify the latest deployment event reports a successful state

### Centralised Log Aggregation

Forward application logs from Clever Cloud into an external observability stack by configuring log drains and consuming the log socket. The API supports per-application drains, chunked log fetches, and SSE streams so that logs can be persisted in tools like Datadog, Loki, or Elasticsearch. Setup typically takes under a day for a basic drain configuration.

Example prompt: Create a syslog log drain for application 'app_abc123' pointing at the customer's external Loki endpoint and confirm the drain id is returned

### Multi-Tenant Billing Operations

Pull billing data, invoices, and payment methods for organizations managed on Clever Cloud to power internal finance dashboards or rebill customers in a multi-tenant setup. The API exposes invoice listings, balances, and payment information per owner. A simple billing sync job can be wired up in a few hours.

Example prompt: Retrieve all invoices for owner 'orga_xyz' in the last 90 days and aggregate the total amount due

### Agent-Driven Platform Management via Jentic

Expose Clever Cloud as a tool to AI agents through Jentic so that agents can deploy services, rotate environment variables, and triage failed deployments using natural language. Jentic isolates the OAuth credentials and surfaces only the operations relevant to a given intent. A working agent integration takes well under an hour with the Jentic SDK.

Example prompt: Search Jentic for 'deploy a clever cloud application', load the schema, and execute a redeploy on appId 'app_abc123'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/logs/{appId}` | Fetch logs for an application |
| POST | `/logs/drains` | Create a log drain |
| GET | `/application/{appId}/environment` | List environment variables for an application |
| POST | `/github/redeploy` | Redeploy an application linked to GitHub |
| GET | `/notifications/emailhooks/{ownerId}` | List configured email notification hooks for an owner |
| GET | `/products/instances` | List available compute instance flavours |

## Key resources

- **Applications** — Create, configure, scale, and redeploy applications and read deployment events
- **Environment** — Read and update environment variables attached to an application
- **Logs and Drains** — Fetch, stream, and forward application logs to external sinks via configurable drains
- **Add-ons** — Provision and bind managed services such as databases and caches to applications
- **Organisations and Members** — Manage organisation membership, roles, and consumer OAuth tokens
- **Billing** — List invoices, payment methods, balances, and price catalogues for an owner
- **GitHub Integration** — Link, redeploy, and authenticate applications against GitHub repositories

## Why Jentic

- **Setup:** Wiring the Clever-Cloud API by hand means completing its OAuth flow and threading owner and application ids through calls to api.clever-cloud.com/v2 across its large platform operation set. Through Jentic you install once, import Clever-Cloud from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Clever-Cloud puts the application id in the URL path (`/application/{appId}/environment`), so a rule can pin your agent to one application: it can read that app's logs and environment and nothing else. You choose the operations it may call, so triggering a GitHub redeploy is not included unless you add it.
- **Credential handling:** Your Clever-Cloud credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read an application's logs' or 'get environment variables in Clever-Cloud', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Vercel API** — Frontend-focused PaaS with Git-driven deploys and edge functions
- **Netlify API** — Build, deploy, and host static and Jamstack sites
- **DigitalOcean API** — General-purpose IaaS and managed services across droplets, kubernetes, and databases

## FAQ

### Why is there no official OpenAPI spec for Clever-Cloud API?

Clever Cloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clever-Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Clever-Cloud API use?

Clever Cloud uses OAuth 1.0a-style signed requests against api.clever-cloud.com/v2, requiring consumer key, consumer secret, OAuth token, and OAuth token secret. When called through Jentic, these credentials are stored in your Jentic One instance and never exposed to the agent context - the agent only receives a scoped execution handle.

### Can I redeploy a GitHub-linked application with the Clever-Cloud API?

Yes. The `/github/redeploy` endpoint triggers a redeploy of an application that has been linked to a GitHub repository, and `/events/event-socket` plus deployment endpoints let you observe the resulting deployment state.

### What are the rate limits for the Clever-Cloud API?

Clever Cloud does not document fixed numeric rate limits in the public spec. In practice, throttling applies to high-frequency log socket connections and deployment triggers - keep deployment polling to a few requests per second per application and prefer the SSE log stream over repeated GETs.

### How do I stream application logs through Jentic?

Search Jentic for 'stream clever cloud application logs', load the operation against `/logs/{appId}/sse`, and execute it with the target appId. Jentic returns the streamed log payload and handles the OAuth signing for you.

### Can I manage billing and invoices through this API?

Yes. Owner-scoped endpoints expose invoices, payment methods, and balances, which is enough to drive an internal billing dashboard or reconcile customer charges across multiple organisations.

### Can I limit what my agent is allowed to do with the Clever Cloud API?

Yes. Because you self-host Jentic One, your own rules decide which Clever Cloud operations and credentials the agent may use. Since the application id sits in the URL path, such as `/application/{appId}/environment`, you can pin the agent to a single app so it only reads that app's logs and environment variables. You also choose the operations it may call, so a GitHub redeploy through `/github/redeploy` is off limits unless you explicitly add it.