docs(getting-started): remove AI warning and refactor to focus on practical payment integration#53
Open
docs(getting-started): remove AI warning and refactor to focus on practical payment integration#53
Conversation
…ontent Migrate Getting Started page from AI-generated placeholder to verified content based on legacy Integration Tutorial. Remove AI warning banner, correct account setup information (no testnet separation, single account type), and add accurate Node.js integration examples with webhook handling. Also update Integration Tutorial links to /api-setup/ path for consistency.
Member
Author
This was referenced Mar 2, 2026
Open
Open
aimensahnoun
changed the title
Greptile SummaryThis PR successfully removes the AI-generated warning and refactors the getting started guide to provide a practical, hands-on Node.js integration example. The new approach is more actionable and focused on helping developers create their first payment request quickly. Key improvements:
Issues found:
These issues should be fixed to ensure developers can follow the guide without errors. Confidence Score: 3/5
Important Files Changed
Last reviewed commit: a6b536c |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| method: 'POST', | ||
| headers: { | ||
| 'Authorization': `Bearer ${process.env.REQUEST_NETWORK_API_KEY}`, | ||
| 'X-Api-Key': process.env.RN_API_KEY, |
There was a problem hiding this comment.
inconsistent header name - use lowercase x-api-key to match the rest of the documentation
Suggested change
| 'X-Api-Key': process.env.RN_API_KEY, | |
| 'x-api-key': process.env.RN_API_KEY, |
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!
| const crypto = require('crypto'); | ||
|
|
||
| // Webhook handler | ||
| app.post('/webhooks', async (req, res) => { |
There was a problem hiding this comment.
app is undefined - the example is missing Express setup
Add setup context before this code:
const express = require('express');
const app = express();
app.use(express.json());| - Check environment (testnet vs mainnet) | ||
| - Ensure API key has required permissions | ||
| - Verify Authorization header format | ||
| - Check that you're using the right header: `X-Api-Key` |
There was a problem hiding this comment.
inconsistent header reference - use lowercase x-api-key to match the rest of the documentation
Suggested change
| - Check that you're using the right header: `X-Api-Key` | |
| - Check that you're using the right header: `x-api-key` |
This was referenced Mar 2, 2026
bassgeta
approved these changes
Mar 2, 2026
Contributor
bassgeta
left a comment
bassgeta
left a comment
There was a problem hiding this comment.
Looking good, leaner and cleaner 💯
Maybe we could still implement Greptile's recommendations, they aren't that much work
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
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
Removed AI-generated content warning and rewrote the getting started guide to focus on practical payment creation with Node.js examples instead of general API testing.
What changed?
RN_prefixed variablesHow to test?
.envfile with the specified API key formatWhy make this change?
The guide was too generic and focused on broad concepts rather than helping developers get started quickly. The new version provides a concrete, working example that developers can run immediately to understand how Request Network payments work, making it more actionable and practical for first-time users.