We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Other
Relevant Discord thread: https://discord.com/channels/621778831602221064/1301836198355931220/1301836198355931220
API URLs described at the top of API pages including (but not limited to):
URLs, e.g. GET /api/0/issues/{issue_id}/ are used as an example of a URL to call.
GET /api/0/issues/{issue_id}/
Further down on the page, the docs state that each URL requires an organization_id_or_slug.
organization_id_or_slug
This is not represented in the URL.
I understand that the API docs are auto-generated from the annotations on API endpoint definitions inside the Sentry repo i.e. here.
No response
The text was updated successfully, but these errors were encountered:
Assigning to @getsentry/support for routing ⏲️
Sorry, something went wrong.
I think this has to do with auto generated API docs more than authors
No branches or pull requests
SDK
Other
Description
Relevant Discord thread: https://discord.com/channels/621778831602221064/1301836198355931220/1301836198355931220
Affected pages:
API URLs described at the top of API pages including (but not limited to):
The issue
URLs, e.g.
GET /api/0/issues/{issue_id}/
are used as an example of a URL to call.Further down on the page, the docs state that each URL requires an
organization_id_or_slug
.This is not represented in the URL.
I understand that the API docs are auto-generated from the annotations on API endpoint definitions inside the Sentry repo i.e. here.
Suggested Solution
No response
The text was updated successfully, but these errors were encountered: