Merged
Conversation
Change query parameter name from authorization-token to authorization_token in the OpenAPI spec and generated API docs.
felipefdl
approved these changes
Apr 2, 2026
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
2 participants
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.
Problem
The
authorization-tokenquery parameter in the Network API endpoint used hyphens instead of underscores, which was inconsistent with the actual API behavior.Investigation
The OpenAPI spec (
tagoio-api.yaml) defined the parameter name asauthorization-tokenwith hyphens, and this propagated to the generated API docs (send-data-using-network.api.mdx).Solution
Renamed the parameter from
authorization-tokentoauthorization_tokenin both the OpenAPI spec and the generated API documentation to match the correct parameter name.