Braintrust API
PUT /v1/service_token endpoint removal
Deprecated, no dateSubscribe to Braintrust APIShare
The PUT /v1/service_token endpoint has been removed from the public API without a scheduled shutdown date. Requests sent to this endpoint now fail. Braintrust API no longer supports creating service tokens through this call.
Calls it hits
PUT /v1/service_token
What to use instead of these calls
Use Manage API keys and Create service tokens for the supported flows.
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
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Braintrust API's own pages
Questions
When does this change take effect?
Braintrust API deprecated PUT /v1/service_token without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Braintrust API has not given a shutdown date yet.
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
-
POST /v1/api_keyEndpoint removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.