API Reference

Authentication

Authentication

To access any of the endpoints of the Orquesta API, you must authenticate your requests. This guide explains how you use bearer authentication (token authentication).

OAuth with bearer token

We recommend authenticating with the API using OAuth2 and a bearer token. You can find this access token in your Orquesta dashboard under workspace settings.

You can get your workspace API key from the settings section in your Orquesta workspace.
https://my.orquesta.dev/<workspace>/settings/developers

Here's how to add the token to the request header using cURL:

Example request with bearer token

curl https://api.orquesta.dev/v2/prompts \
  -H "Authorization: Bearer {token}"

⚠️ Important: Always keep your token safe and reset it if you suspect it has been compromised.

Using an SDK

If you use one of our official SDKs, you won't have to worry about any of the above — just add your API token, and the client library will take care of the rest. All the client libraries use OAuth2 behind the scenes.

Check out our list of first-party SDKs 🡢

Using the API

After setting up your authentication, consume Orquesta API for your LLM Ops and Remote Configurations

Prompts API 🡢

Remote Configs API 🡢

Authentication

To access any of the endpoints of the Orquesta API, you must authenticate your requests. This guide explains how you use bearer authentication (token authentication).

OAuth with bearer token

We recommend authenticating with the API using OAuth2 and a bearer token. You can find this access token in your Orquesta dashboard under workspace settings.

You can get your workspace API key from the settings section in your Orquesta workspace.
https://my.orquesta.dev/<workspace>/settings/developers

Here's how to add the token to the request header using cURL:

Example request with bearer token

curl https://api.orquesta.dev/v2/prompts \
  -H "Authorization: Bearer {token}"

⚠️ Important: Always keep your token safe and reset it if you suspect it has been compromised.

Using an SDK

If you use one of our official SDKs, you won't have to worry about any of the above — just add your API token, and the client library will take care of the rest. All the client libraries use OAuth2 behind the scenes.

Check out our list of first-party SDKs 🡢

Using the API

After setting up your authentication, consume Orquesta API for your LLM Ops and Remote Configurations

Prompts API 🡢

Remote Configs API 🡢

Authentication

To access any of the endpoints of the Orquesta API, you must authenticate your requests. This guide explains how you use bearer authentication (token authentication).

OAuth with bearer token

We recommend authenticating with the API using OAuth2 and a bearer token. You can find this access token in your Orquesta dashboard under workspace settings.

You can get your workspace API key from the settings section in your Orquesta workspace.
https://my.orquesta.dev/<workspace>/settings/developers

Here's how to add the token to the request header using cURL:

Example request with bearer token

curl https://api.orquesta.dev/v2/prompts \
  -H "Authorization: Bearer {token}"

⚠️ Important: Always keep your token safe and reset it if you suspect it has been compromised.

Using an SDK

If you use one of our official SDKs, you won't have to worry about any of the above — just add your API token, and the client library will take care of the rest. All the client libraries use OAuth2 behind the scenes.

Check out our list of first-party SDKs 🡢

Using the API

After setting up your authentication, consume Orquesta API for your LLM Ops and Remote Configurations

Prompts API 🡢

Remote Configs API 🡢

Start powering your SaaS with LLMs

Start

powering

your SaaS

with LLMs

Start powering your SaaS with LLMs