Clever-Cloud API

Name: Clever-Cloud API API
Brand: Clever-Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth2324 EndpointsREST

For Agents

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

Quickstart

Get started with Clever-Cloud API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy an application to clever cloud"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Clever-Cloud API API.

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

GET STARTED

Start building with Clever-Cloud API API

Explore with Jentic

View OpenAPI Document

Use for: I need to deploy a new application to Clever Cloud, Set up a log drain for an application running on Clever Cloud, Retrieve the latest deployment events for an application, List all add-ons attached to a Clever Cloud organization

Not supported: 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.

Jentic publishes the only available OpenAPI document for Clever-Cloud API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Clever-Cloud API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

324 endpoints — jentic publishes the only available openapi specification for clever-cloud api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Clever Cloud OAuth consumer keys and tokens are stored encrypted in the Jentic vault. Agents receive scoped execution handles — the four-part signed credential never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'deploy a clever cloud application') and Jentic returns the matching Clever Cloud operation with its input schema, so the agent can call the right endpoint without browsing 324 endpoints of documentation.

Time to first call

Direct Clever Cloud integration: 2-4 days to wire up OAuth signing, deployment polling, and log drain setup. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Vercel API

Frontend-focused PaaS with Git-driven deploys and edge functions

Choose Vercel when the workload is a Next.js or static frontend that benefits from edge rendering rather than a long-running backend service

Alternative

Netlify API

Build, deploy, and host static and Jamstack sites

Choose Netlify for static site hosting and form/identity workflows; Clever Cloud is better for full backend services with managed add-ons

Alternative

DigitalOcean API

General-purpose IaaS and managed services across droplets, kubernetes, and databases

Choose DigitalOcean when the agent needs raw VMs or Kubernetes control rather than the opinionated PaaS model Clever Cloud provides

FAQs

Specific to using Clever-Cloud API API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.