Uh oh!
There was an error while loading. Please reload this page.
docs(query-requests): simplify and refactor query requests documentation for practical implementation - #65
Conversation
This was referenced Mar 2, 2026
Merged
Merged
ContributorAuthor
This was referenced Mar 2, 2026
Merged
api-features/query-requests.mdx to use the correct OpenAPI deep links for request status and wallet-level reconciliation. - replaced non-working request stataimen74
marked this pull request as ready for review
March 2, 2026 12:11
Greptile SummaryThis PR rewrites
Confidence Score: 5/5Safe to merge — this is a documentation-only rewrite with no functional code changes. The change is confined to a single MDX documentation file. All internal hrefs resolve to existing pages, the frontmatter structure is valid, and the Mintlify components used are standard. The only gaps are a stale description field and absent runnable code examples — neither affects correctness or site rendering. No files require special attention beyond the minor frontmatter description mismatch in api-features/query-requests.mdx. Important Files Changed
Reviews (2): Last reviewed commit: "docs(api-features): fix query-requests O..." | Re-trigger Greptile |
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Mar 2, 2026
Merged
Merged
This was referenced Mar 3, 2026
This was referenced Mar 30, 2026
This was referenced May 8, 2026
Contributor
Merge activity
|
rodrigopavezi
changed the base branch from
03-02-docs_api-features_refine_payment-detection_with_legacy-aligned_accurate_guidance_update_api-features_payment-detection.mdx_to_remove_ai-generated_placeholder_framing_and_align_the_page_with_legacy-supported_detection_concepts_wh
to
graphite-base/65May 12, 2026 16:28
…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
rodrigopaveziforce-pushed
the
03-02-docs_api-features_fix_query-requests_openapi_endpoint_links_and_reconciliation_mapping_update_api-features_query-requests.mdx_to_use_the_correct_openapi_deep_links_for_request_status_and_wallet-level_reconciliation._-_replaced_n
branch
from
May 12, 2026 16:30
5b84b6a to
5f2feceCompareUh oh!
There was an error while loading. Please reload this page.
rodrigopavezi
deleted the
03-02-docs_api-features_fix_query-requests_openapi_endpoint_links_and_reconciliation_mapping_update_api-features_query-requests.mdx_to_use_the_correct_openapi_deep_links_for_request_status_and_wallet-level_reconciliation._-_replaced_n
branch
May 12, 2026 16:31
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 freeto 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.
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.