Aiven API

Name: Aiven API
Brand: Aiven API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureComputebearer, oauth2445 EndpointsREST

For Agents

Provision and operate managed PostgreSQL, Kafka, ClickHouse, OpenSearch, and other open-source data services across major clouds via Aiven.

Use for: Provision a new managed PostgreSQL service in Aiven, Create a Kafka topic with specific partition and retention settings, List all services running in an Aiven project, Set up a service integration to send Kafka logs to OpenSearch

Not supported: Does not handle bare-metal compute, generic VM provisioning, or non-Aiven workloads - use for Aiven-managed open-source data services, projects, and organizations only.

The Aiven API gives programmatic control over Aiven's managed open-source data platform, covering provisioning and operation of services such as PostgreSQL, Kafka, ClickHouse, OpenSearch, MySQL, Redis, Cassandra, Flink, and Grafana on AWS, GCP, Azure, DigitalOcean, and UpCloud. Endpoints span organizations, projects, services, integrations, billing, governance, and per-engine operations such as Kafka topics, ClickHouse queries, and PostgreSQL connection pools. Authentication is via a personal token (Authorization: aivenv1 token) or OAuth 2.0. Suited for platform teams that automate database provisioning, GitOps-driven infrastructure, and SRE-grade fleet management.

Jentic One on Github

Install Jentic One Beta

Connect the Aiven API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aiven API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.aiven.io%2Faiven" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.aiven.io%2Faiven" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Aiven API.

Provision a managed service (PostgreSQL, Kafka, ClickHouse, OpenSearch, MySQL, Redis) inside a project

Configure service integrations between databases, monitoring, and external sinks via the Service Integrations endpoints

Manage Kafka topics, ACL entries, quotas, and schema registry through the Kafka-specific operations

Run ClickHouse queries and manage databases through the Service: ClickHouse endpoints

GET STARTED

Start building with Aiven API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Aiven API for, with concrete tasks.

★ Database provisioning automation

Automate per-environment database provisioning by calling /project/{project}/service to create a PostgreSQL or Kafka service from a Terraform-style intent. The API returns the connection URI once the service reaches RUNNING state, which a CI pipeline can write into application secrets. Replaces clickops in the Aiven console for staging and ephemeral environments and gives platform teams a typed contract.

POST to /project/myproj/service with service_type=pg, plan=startup-4, cloud=aws-eu-west-1, then poll until state=RUNNING and return service_uri.

Kafka topic and ACL management

Manage the full lifecycle of Kafka topics, ACL entries, and schema registry subjects without granting humans cluster admin. The Service: Kafka endpoints let an automation actor create topics with the right partition count, restrict producer/consumer ACLs to specific principals, and publish schemas to the registry. Underpins data-platform self-service portals.

POST to /project/{project}/service/{service_name}/topic with topic_name, partitions=12, replication=3, then POST an ACL granting a service account write access.

Cross-service observability wiring

Stand up a logging and metrics pipeline by creating an Aiven OpenSearch and Grafana service, then using the Service Integrations endpoints to fan logs and metrics from every other service into them. A platform team can offer 'logs to OpenSearch' as a one-click feature for application teams without each team configuring their own sinks. Reduces observability drift across a fleet of services.

POST to /project/{project}/integration with integration_type=logs, source_service=my-kafka, dest_service=my-opensearch.

Agent integration via Jentic

Give an SRE agent a typed surface over Aiven's 445 operations through Jentic. The agent can answer 'spin up a Postgres for staging' or 'add this consumer ACL on the prod Kafka cluster' in a single tool call, with the personal token kept inside your Jentic One instance. Avoids hand-rolling a thin client per workflow.

Search Jentic for 'create Aiven PostgreSQL service', load the relevant /project/{project}/service POST operation, and execute it with the requested service_type and plan.

Key Endpoints

445 endpoints — the aiven api gives programmatic control over aiven's managed open-source data platform, covering provisioning and operation of services such as postgresql, kafka, clickhouse, opensearch, mysql, redis, cassandra, flink, and grafana on aws, gcp, azure, digitalocean, and upcloud.

METHOD

PATH

DESCRIPTION

GET

/account

List Aiven accounts

GET

/account/{account_id}

Retrieve a specific account

GET

/account/{account_id}/payment_methods

List payment methods on an account

GET

/account/{account_id}/billing-group

List billing groups on an account

GET

/account/{account_id}/authentication

List authentication methods on an account

GET

/account/{account_id}/events

List recent events on an account

GET

/account

List Aiven accounts

GET

/account/{account_id}

Retrieve a specific account

GET

/account/{account_id}/payment_methods

List payment methods on an account

GET

/account/{account_id}/billing-group

List billing groups on an account

GET

/account/{account_id}/authentication

List authentication methods on an account

GET

/account/{account_id}/events

List recent events on an account

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Aiven API by hand means choosing between its personal-token and OAuth auth, targeting the v1 host, and finding the right routes among 445 project and organization endpoints yourself. Through Jentic you install once, import Aiven from the API Directory, store the token once, and your agent calls it.

Permission scoping

Aiven puts the account id in the URL path (/account/{account_id}/events, /account/{account_id}/billing-group), so a rule can pin your agent to one account: it can read that account's events and settings and nothing else. You choose the operations it may call, so writes such as payment-method changes are only included if you add them.

Credential isolation

Your Aiven personal token or OAuth token 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.

Intent-based discovery

Agents search Jentic by intent such as 'create an Aiven PostgreSQL service', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Aiven API through Jentic.

What authentication does the Aiven API use?

The Aiven API supports a personal token (Authorization: aivenv1 {token}) and OAuth 2.0. Tokens are created from the Aiven console and scoped to a user; service tokens can be created for automation. When called through Jentic, the token is held in your Jentic One instance and injected on each request.

Can I provision a managed PostgreSQL or Kafka cluster through the Aiven API?

Yes. POST /project/{project}/service with service_type set to pg, kafka, clickhouse, opensearch, mysql, redis, or another supported engine, plus plan and cloud. The service moves through REBUILDING > RUNNING; the response includes the service_uri once it is ready to accept connections.

How do I manage Kafka topics and ACLs?

The Service: Kafka endpoints expose topic creation, partition and retention configuration, ACL entries, quotas, and schema registry operations under /project/{project}/service/{service_name}/topic and /acl paths. They are the programmatic equivalent of the Kafka tab in the Aiven console.

What are the rate limits for the Aiven API?

Aiven applies per-token rate limits in the low hundreds of requests per minute, with separate ceilings for read and write paths. 429 responses include a Retry-After header; agents should back off and retry. Heavy bulk operations should use service-specific batch endpoints where available.

How do I provision an Aiven service through Jentic?

Search Jentic for 'create Aiven PostgreSQL service', load the POST /project/{project}/service operation, and execute it with project, service_type, plan, and cloud. Then poll GET /project/{project}/service/{service_name} until state=RUNNING to retrieve the service_uri.

Does the Aiven API support service maintenance and upgrades?

Yes. Service-level endpoints expose maintenance windows, allow triggering immediate upgrades, and surface upgrade pipeline state for blue/green-style migrations between major versions. Use these endpoints to script controlled major-version upgrades across a fleet of services.

Can I limit what my agent is allowed to do with the Aiven API?

Yes. Because you run Jentic One yourself, your own rules decide which Aiven operations and which stored token the agent may use. Aiven puts the account id in the URL path, so you can pin the agent to a single account and let it read that account's events, billing groups, and authentication methods under /account/{account_id} while it can touch nothing else. Sensitive writes such as changing payment methods are only reachable if you explicitly add those operations to the agent's allowed set.