docs(supported-chains): add Tron network support and enhance currency documentation#73
Open
docs(supported-chains): add Tron network support and enhance currency documentation#73
Conversation
…fe updates Improve resource pages for supported chains/currencies and token discovery while preserving required Tron coverage and improving navigation clarity. - update `supported-chains-and-currencies` with clearer coverage wording: EVM-compatible chains + select non-EVM support (Tron) - keep and structure Tron-specific support details where relevant (network, token standard, address-format warning, examples) - convert key references from generic links to cards for better UX - update card targets to section-level anchors where possible to reduce navigation friction - keep currencies endpoint references visible and actionable - update `token-list` by removing outdated AI warning and simplifying usage flow - replace raw usage URL text with a dedicated “Request Token List JSON” card - keep legacy token-list structure/content intact - add concise “Token List vs Currencies API” guidance with endpoint cards - remove unnecessary SDK-source reference line to keep page focused
This was referenced Mar 3, 2026
Open
Open
Open
Member
Author
This was referenced Mar 3, 2026
aimensahnoun
changed the title
Greptile SummaryThis PR enhances the Request Network documentation by adding comprehensive Tron network support details to Key changes:
Issues found:
Confidence Score: 4/5
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Developer needs currency info] --> B{Payment type?}
B --> C[ERC20 / Native]
B --> D[Conversion Payment]
B --> E[Tron / USDT TRC-20]
B --> F[Crosschain]
B --> G[Crypto-to-fiat]
C --> H[Token List\nrequest-token-list JSON\n500+ tokens]
C --> I[GET /v2/currencies\nfilter by network & symbol]
D --> J[Invoice currency: USD/EUR/CNY/GBP/JPY]
D --> K[Payment currency: USDC/USDT/DAI/FAU]
D --> L[GET /v2/currencies/currencyId/conversion-routes]
E --> M[Network ID: tron\nCurrency: USDT-tron\nAddress format: T...]
H --> N[Use for static metadata\n& broad catalog browsing]
I --> O[Use for runtime filtering\n& conversion-route discovery]
Last reviewed commit: b5a3a67 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+143
to
+144
| curl -X GET 'https://api.request.network/v2/currencies?network=base&symbol=USDC&firstOnly=true' \ | ||
| -H 'x-api-key: YOUR_API_KEY' |
There was a problem hiding this comment.
The firstOnly=true query parameter in this example should be verified against the Request Network API specification before publishing. If this parameter is not officially documented in the OpenAPI spec, the example could mislead developers. Please confirm this parameter is supported by checking the API documentation at https://api.request.network/open-api/, or remove it from the example if it is not part of the official API.
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
Added comprehensive Tron network support documentation and enhanced the supported chains and currencies guide with practical examples and API usage patterns.
What changed?
T...address format differencesETH-mainnet,USDC-base) and Tron format (USDT-tron)How to test?
Why make this change?
This change provides developers with clearer guidance on Request Network's expanded chain support, particularly the addition of Tron for USDT payments. The enhanced documentation includes practical examples and API usage patterns that make it easier for developers to integrate with the platform and understand the differences between EVM and non-EVM implementations.