Conversation
The platform API accepts Authorization: Bearer <token>. The legacy accessToken format keeps working and is noted as such.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The platform API now accepts access tokens as
Authorization: Bearer <token>, the standard format, in addition to the legacyAuthorization: accessToken <token>(steadybit/platform#2064). The MCP page already documentsBearer, so this aligns the API page with it.Beareras the header format, with a hint thataccessTokenis still supported and that older on-prem versions accept only the legacy format.curlexamples on the page (create token, rate limiting, create experiment, run experiment) useBearer.Bearerreturns 401 on/api/**in SaaS.BusinessMap: https://steadybitgmbh.kanbanize.com/ctrl_board/2/cards/25243