---
title: "Create api_key"
method: POST
path: "/v1/api_key"
tags: ["ApiKeys"]
---

# Create api_key

`POST /v1/api_key`

Create a new api_key. It is possible to have multiple API keys with the same name. There is no de-duplication

## Request body

- object
  - `name` string, required — Name of the api key. Does not have to be unique
  - `org_name` string, nullable — For nearly all users, this parameter should be unnecessary. But in the rare case that your API key belongs to multiple organizations, you may specify the name of the organization the API key belongs in.

## Response `200`

Returns an object containing the raw API key. This is the only time the raw API key will be exposed

- CreateApiKeyOutput
  - `id` string, uuid, required — Unique identifier for the api key
  - `created` string, date-time, nullable — Date of api key creation
  - `name` string, required — Name of the api key
  - `preview_name` string, required
  - `user_id` string, uuid, nullable — Unique identifier for the user
  - `org_id` string, uuid, nullable — Unique identifier for the organization
  - `key` string, required — The raw API key. It will only be exposed this one time

## Other responses

- `400` — The request was unacceptable, often due to missing a required parameter
- `401` — No valid API key provided
- `403` — The API key doesn’t have permissions to perform the request
- `429` — Too many requests hit the API too quickly. We recommend an exponential backoff of your requests
- `500` — Something went wrong on Braintrust's end. (These are rare.)

---

[API](https://skmtc.net/braintrustdata/apis/braintrust-api.md) · [All operations](https://skmtc.net/braintrustdata/apis/braintrust-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/braintrustdata/braintrust-api/versions/9d216c8243fe/schema)