fix(specs): usage api #2954
Merged
fix(specs): usage api #2954
Conversation
This file contains 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
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
shortcuts
reviewed
Apr 5, 2024
Comment on lines
+42
to
+45
| appId: | ||
| $ref: '../common/securitySchemes.yml#/appId' | ||
| apiKey: | ||
| $ref: '../common/securitySchemes.yml#/apiKey' |
There was a problem hiding this comment.
it's really this and not basic? if so we will be able to generate clients then!
There was a problem hiding this comment.
@shortcuts I thought the Usage API isn't part of the SDKs?
The current/old API reference in the docs say that it uses the x-algolia-* headers and not basic auth.
There was a problem hiding this comment.
Yes it's not because generating clients only works with the appID and apiKey combo for now, but since it doesn't use the basic auth anymore, we can make a client for it!
|
nice my fix worked :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🧭 What and Why
Update of the Usage API spec.
Unfortunately, I can't test the Usage API (can't make any requests) so I can't independently verify the information like I did for the other APIs, so I only did a few style updates.
Changes included:
{statistics}parameter