canonical: https://jentic.com/apis/temporal.io/temporal

# Temporal Cloud Ops API

HTTP API for programmatic management of Temporal Cloud control plane resources including namespaces, users, service accounts, API keys, audit logs, and billing. The API exposes 45 endpoints secured with bearer authentication.

## For AI agents

Programmatically update account configuration, get account details. Covers 45 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Update account configuration
- Get account details
- Create an API key
- List API keys
- Monitor Temporal Cloud Ops API operational status and events

## Use cases

### Payments Operations

Use the Temporal Cloud Ops API to perform payments operations programmatically. The API provides 45 endpoints covering core functionality including update account configuration, get account details, get current identity.

Example prompt: Call POST /cloud/account to update account configuration

### Automated Cloud Management

Automate cloud operations by combining multiple Temporal Cloud Ops API endpoints. Agents can get account details and then get current identity in a single workflow.

Example prompt: Call GET /cloud/account to get account details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Temporal Cloud Ops API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'update account configuration', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /cloud/account | Update account configuration |
| GET | /cloud/account | Get account details |
| GET | /cloud/current-identity | Get current identity |
| POST | /cloud/api-keys | Create an API key |
| GET | /cloud/api-keys | List API keys |
| POST | /cloud/api-keys/{keyId} | Update an API key |
| GET | /cloud/api-keys/{keyId} | Get an API key |
| DELETE | /cloud/api-keys/{keyId} | Delete an API key |

## Key resources

- **Cloud** — Operations for cloud

## Why Jentic

- **Setup:** Wiring the Temporal Cloud Ops API by hand means learning its bearer token auth against the saas-api.tmprl.cloud host and handling account, API-key, and namespace calls yourself. Through Jentic you install once, import the Temporal Cloud Ops API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** This API puts the key id in the URL path (/cloud/api-keys/{keyId}), so a rule can pin your agent to the specific management operations it needs, such as reading account details or listing API keys. You choose the operations it may call, so destructive ones like deleting an API key are not included unless you add them.
- **Credential handling:** Your Temporal Cloud bearer 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.
- **Discovery method:** Agents search Jentic by intent such as 'read account configuration' or 'list API keys', and Jentic returns the matching Temporal Cloud Ops API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Temporal Cloud Ops API use?

The Temporal Cloud Ops API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I update account configuration with the Temporal Cloud Ops API?

Yes. Use the POST /cloud/account endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Temporal Cloud Ops API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I update account configuration through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update account configuration'. Jentic returns the matching Temporal Cloud Ops API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Temporal Cloud Ops API have?

The Temporal Cloud Ops API exposes 45 endpoints covering cloud operations.

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

Yes. Because you run Jentic One yourself and self-host it, your own rules decide which Temporal Cloud Ops API operations and credentials the agent may use. Since the key id sits in the URL path (/cloud/api-keys/{keyId}), you can pin the agent to just the operations it needs, such as GET /cloud/account to read account details or GET /cloud/api-keys to list keys. Destructive calls like DELETE /cloud/api-keys/{keyId} are excluded unless you explicitly grant them.