docs(query-requests): simplify and refactor query requests documentation for practical implementation#65
Open
docs(query-requests): simplify and refactor query requests documentation for practical implementation#65
Conversation
…onciliation mapping Update `api-features/query-requests.mdx` to use the correct OpenAPI deep links for request status and wallet-level reconciliation. - replaced non-working request status endpoint links with: - https://api.request.network/open-api/#tag/v2request/GET/v2/request/{requestId} - added wallet-level reconciliation endpoint reference: - https://api.request.network/open-api/#tag/v2payments/GET/v2/payments - updated both “Core Endpoints” and “How It Works” sections to keep endpoint guidance consistent - clarified that request-level and wallet-level querying are complementary in reconciliation workflows
This was referenced Mar 2, 2026
Open
Open
Member
Author
This was referenced Mar 2, 2026
Open
aimensahnoun
changed the title
api-features/query-requests.mdx to use the correct OpenAPI deep links for request status and wallet-level reconciliation. - replaced non-working request stat
Greptile SummarySuccessfully refactors Query Requests documentation from AI-generated placeholder content to practical, endpoint-driven guidance. Removes theoretical status lifecycle diagrams and replaces them with concrete API endpoint references and step-by-step reconciliation patterns. Reduces page length by 20% while adding more actionable information. OpenAPI links and internal page references are all valid. Key improvements:
Check needed:
Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 5b84b6a |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+25
to
+29
| - `hasBeenPaid` | ||
| - `paymentReference` | ||
| - `txHash` | ||
| - `isListening` | ||
| - optional metadata such as `customerInfo` and `reference` |
There was a problem hiding this comment.
Verify field names match actual API schema. hasBeenPaid and isListening not found in webhook docs or other pages - webhooks use totalAmountPaid/expectedAmount instead.
This was referenced Mar 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
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.
TL;DR
Rewrote the Query Requests documentation page to focus on practical usage patterns and core endpoints rather than theoretical concepts.
What changed?
How to test?
Review the updated documentation page to ensure:
Why make this change?
The original documentation was too theoretical and included AI-generated disclaimers that reduced confidence. The new version provides developers with immediate, actionable guidance on how to actually use query endpoints for request status monitoring and reconciliation workflows.