Braintrust API
POST /v1/api_key endpoint removal
Stopped workingSubscribe to Braintrust APIShare
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.
Calls it hits
POST /v1/api_key
What to use instead of these calls
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.
In 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.
Facts
- API
- Braintrust API
api.braintrust.dev - Kind
- Endpoint removal
- Announced
- May 1, 2026
- Takes effect
- May 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Braintrust API's own pages
Questions
When does this change take effect?
Calls to POST /v1/api_key on Braintrust API stopped working on May 1, 2026.
What happens to calls after May 1, 2026?
They have failed since May 1, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Braintrust API 1
-
No date
PUT /v1/service_tokenEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.