docs(conversion-payments): rewrite with step-by-step implementation guide and remove AI-generated warning#61
Open
docs(conversion-payments): rewrite with step-by-step implementation guide and remove AI-generated warning#61
Conversation
…avior
Refactor `api-features/conversion-payments.mdx` from AI-generated placeholder
content into endpoint-driven documentation aligned with current API behavior.
- removed AI warning banner and unsupported assumptions
- rewrote page to explain conversion as “different invoice and payment currencies”
instead of fiat-only behavior
- updated conversion flow to a step-based implementation using:
- POST /v2/request
- GET /v2/request/{requestId}/pay
- GET /v2/request/{requestId}
- documented status-level conversion fields used in practice:
- amountInUsd
- conversionRate
- rateSource
- conversionBreakdown (for partial/multi-payment cases)
- replaced invalid currency example `USDC-base-base` with valid `USDC-base`
- removed hidden/unsupported use-case references and kept only active links
- standardized API docs reference to canonical OpenAPI URL:
https://api.request.network/open-api
This was referenced Mar 2, 2026
Open
Open
Member
Author
This was referenced Mar 2, 2026
Open
aimensahnoun
changed the title
api-features/conversion-payments.mdx from AI-generated placeholder content into endpoint-driven documentation aligned with current API behavior. - removed AI warning ban
Greptile SummaryThis PR successfully removes AI-generated placeholder content and replaces it with accurate, implementation-focused documentation for conversion payments. The updated page correctly clarifies that conversion payments work between any two currencies (not just fiat-to-crypto) and provides a clear step-by-step implementation guide using actual API endpoints. Key improvements:
The documentation is well-structured, uses appropriate Mintlify components, and all internal links have been verified to exist. Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 64bce28 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
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
Updated conversion payments documentation to clarify that it supports any currency-to-currency conversion, not just fiat-to-crypto, and replaced AI-generated content with accurate implementation details.
What changed?
How to test?
Review the updated documentation to ensure:
Why make this change?
The previous documentation was AI-generated and contained inaccuracies about conversion payments being limited to fiat-to-crypto scenarios. This update provides accurate, implementation-focused guidance that reflects the actual API capabilities and helps developers understand how to use conversion payments for any currency pair.