docs(create-requests): rewrite with workflows, examples, and remove AI warning#55
Open
docs(create-requests): rewrite with workflows, examples, and remove AI warning#55
Conversation
…vior Refactor the Create Requests docs to keep the Mintlify layout while replacing AI-generated/uncertain content with verified guidance from legacy docs. - Removed inaccurate sections and fields (`Due Date`, `Customer Info`, `Reference`, and generic “Content Data” block) - Reworked “Request Types” into clearer workflow-based guidance (invoice-first vs payment-first) - Updated the flow diagram and examples to reflect actual request/payment flow - Cleaned up links and removed references to hidden/unsupported pages - Pointed API reference to the canonical OpenAPI URL: https://api.request.network/open-api Result: the page now preserves the current Mintlify structure, but the content is tighter and aligned with real API usage.
This was referenced Mar 2, 2026
Member
Author
This was referenced Mar 2, 2026
Open
Open
aimensahnoun
changed the title
Greptile SummaryChangesThis PR completely rewrites the Create Requests documentation, removing the AI-generated warning and providing comprehensive guidance on request creation workflows. Improvements:
Critical Issue:
Verification:
Confidence Score: 2/5
Important Files Changed
Last reviewed commit: 7a351c3 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| Request Network API-->>App: 201 Created {requestId, paymentReference} | ||
|
|
||
| User->>App: Pay Request | ||
| App->>Request Network API: GET /request/{paymentReference}/pay {apiKey} |
There was a problem hiding this comment.
Incorrect parameter in v2 API endpoint. According to the v2 migration docs, the v2 pay endpoint uses {requestId}, not {paymentReference}.
Suggested change
| App->>Request Network API: GET /request/{paymentReference}/pay {apiKey} | |
| App->>Request Network API: GET /request/{requestId}/pay {apiKey} |
Comment on lines
+129
to
+135
| ```javascript | ||
| const payResponse = await fetch( | ||
| `https://api.request.network/v2/request/${paymentReference}/pay`, | ||
| { | ||
| headers: { 'X-Api-Key': process.env.RN_API_KEY } | ||
| } | ||
| ); |
There was a problem hiding this comment.
Incorrect parameter in v2 API endpoint. The v2 pay endpoint requires requestId (not paymentReference). Update both the URL and the destructured variable.
Suggested change
| ```javascript | |
| const payResponse = await fetch( | |
| `https://api.request.network/v2/request/${paymentReference}/pay`, | |
| { | |
| headers: { 'X-Api-Key': process.env.RN_API_KEY } | |
| } | |
| ); | |
| const payResponse = await fetch( | |
| `https://api.request.network/v2/request/${requestId}/pay`, | |
| { | |
| headers: { 'X-Api-Key': process.env.RN_API_KEY } | |
| } | |
| ); |
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
Completely rewrote the Create Requests documentation page to provide clearer explanations, practical examples, and better organization of request creation workflows.
What changed?
How to test?
Why make this change?
The previous documentation was marked as AI-generated and potentially inaccurate. This rewrite provides developers with clear, actionable guidance on request creation workflows, includes practical code examples, and better explains the different approaches available through the API. The new structure makes it easier for developers to understand both the conceptual flow and implementation details.