# POST /v1/api_key stops working

Calls to POST /v1/api_key on Braintrust API stopped working on May 1, 2026.

On May 1, 2026, the POST /v1/api_key endpoint was removed from the public API. Calls to POST /v1/api_key fail because the REST API no longer supports creating them. This change also coincides with the removal of service token management endpoints.

- API: Braintrust API (api.braintrust.dev)
- Kind: Endpoint removal
- Announced: May 1, 2026
- Takes effect: May 1, 2026
- Calls after that day: fail
- Calls it hits: `POST /v1/api_key`
- Source: [Announcement](https://www.braintrust.dev/docs/changelog)
- Page: https://www.okapi.bot/providers/braintrust-api/breaking-changes/post-v1-api-key-stops-working/

## What to use instead

Create API keys manually in the Braintrust UI, or have an organization owner create a service token with POST /v1/service_token for automation. Moving to service tokens requires deciding whether to issue tokens through an owner or generate keys interactively.

API keys can now only be created by a person in the Braintrust UI, or replaced by service tokens an organization owner issues.

## Braintrust API's words

> The REST API no longer supports creating either, and the POST /v1/api_key , POST /v1/service_token , and PUT /v1/service_token endpoints have been removed from the public API.