Skip to content

docs(drift): draft from internal source #484

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Open
pedromcunha wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(drift): draft from internal source #484

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion references/api/api_guides/migrating-to-requests-v3.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -317,7 +317,7 @@ Every individual change, grouped by request side and response side.

The `x-api-key` request header is now required. Every request authenticates against an active API key. See [API Keys](/references/api/api-keys) for details.

**Access scope.** v3 returns only requests that your integrator owns. Any of your API keys can access all v3 data for your other keys. If you use more than one key, you do not have to change your integration.
**Access scope.** v3 returns requests owned by your integrator, plus requests that were created without an API key. Any of your API keys can access all v3 data for your other keys — if you use more than one key, you do not have to change your integration.

@greptile-apps greptile-apps Bot Sep 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Conflicting access scope. This sentence says v3 returns requests created without an API key, but the migration checklist still says results include only requests owned by the integrator. Readers following the checklist cannot tell whether unkeyed requests should appear. Please reconcile the two statements and explain how an unkeyed request is associated with an integrator. Greptile automatically discovered a related ticket stating that the guide should explain how access scope applies to all associated Requests v3 data, which informed this comment.

Source Used: Linear — Update Requests v3 migration guidance

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

</Accordion>

<Accordion title="Filtering, search & sorting" icon="magnifying-glass">
Expand Down
Loading