You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the CreateQuote method, we are returning a few ILP-specific fields: maxPacketAmountminExchangeRatelowEstimatedExchangeRatehighEstimatedExchangeRate. These are used internally only, and unlikely to be useful to any callers of the Admin APIs, so they can be removed from the resulting schema. They become especially unnecessary with the introduction of local payments.
However, it would be useful to start exposing estimatedExchangeRate in the response object, as it can give integrators an easy way to display quote details to their end users.
The text was updated successfully, but these errors were encountered:
mkurapov
changed the title
Removing the ILP-specific GraphQL fields from the CreateQuote method: maxPacketAmountminExchangeRatelowEstimatedExchangeRatehighEstimatedExchangeRate, but add estimatedExchangeRate
Update the createQuote mutation response type
Aug 9, 2024
Context
In the
CreateQuote
method, we are returning a few ILP-specific fields:maxPacketAmount
minExchangeRate
lowEstimatedExchangeRate
highEstimatedExchangeRate
. These are used internally only, and unlikely to be useful to any callers of the Admin APIs, so they can be removed from the resulting schema. They become especially unnecessary with the introduction of local payments.However, it would be useful to start exposing
estimatedExchangeRate
in the response object, as it can give integrators an easy way to display quote details to their end users.The text was updated successfully, but these errors were encountered: