Generate a transaction quote so you can price the transfer, confirm inputs, and execute with a valid quote ID.

⏱️
Time to integrate: Most teams can connect quote generation in under 10 minutes once account funding, beneficiary setup, and payout destination validation are complete.

What this endpoint does

Use this endpoint to generate a quote for a transaction before execution.

A quote is a priced transaction request. It typically represents the amounts, fees, exchange context, and other inputs required before funds can move.

In most flows, you generate the quote after the source account and recipient details are ready, then use the returned quote ID to execute the transaction.

When to call this endpoint

Call this endpoint when you need to:

price a transaction before execution
confirm the transaction details before moving funds
validate that the source account, destination, and corridor inputs are ready
obtain the quote ID required for execution

This endpoint comes after account retrieval, verification checks, beneficiary setup, and destination validation.

Why quote generation matters

Generating a quote before execution helps your team:

confirm the transaction inputs before committing funds movement
present pricing or transfer details to internal operators or end users
separate transaction preparation from final execution
catch issues earlier in the flow instead of during the final execute call

For enterprise teams, quote generation is also an operational checkpoint for approval workflows and reconciliation.

Authentication

Send your API key in the x-api-key header on every request.

Item	Value
Authentication method	API key
Required header	`x-api-key`
Rate limit scope	Per API key

Recommended workflow

Use this endpoint in the core transaction sequence:

Fetch organization accounts.
Check verification status.
Create a beneficiary.
Add a beneficiary account.
Resolve bank account details if required.
Generate a quote.
Execute the transaction with the quote ID.

What data to prepare before generating a quote

Before sending the request, confirm the transaction inputs your payout corridor requires.

At minimum, your team should confirm:

the source account to use
the transaction amount and currency context
the beneficiary or destination the funds are going to
any country, provider, or network information required for routing
any compliance or operational metadata required by your internal process

⚠️
Needs confirmation: Exact request fields, required amount and currency properties, destination references, quote validity window, and routing constraints should be confirmed in the API definition.

Validation guidance

Before calling this endpoint, validate the transaction inputs in your own system.

Recommended checks:

confirm the source account exists in the intended environment
confirm the source account has or can receive sufficient balance
confirm the beneficiary and payout destination are ready for use
verify the transaction amount is within expected business rules before sending the request
confirm the corridor, provider, country, and currency inputs match the intended payout method

If your workflow includes internal approval, generate the quote only after the transaction details are final enough to be reviewed.

How to use the response

After the quote is created, store the returned quote ID in your backend.

You will typically use the response to:

review the transaction pricing and details
confirm that the transaction is ready for execution
pass the quote ID into the execute transaction step
record pre-execution details for audit and reconciliation workflows

Recommended decision flow

If quote generation succeeds:

store the quote ID
verify the returned details match the intended transaction
execute the transaction before the quote is no longer usable

If quote generation fails:

review source account, destination, and amount inputs
check limits, funding, or corridor requirements
correct the request before retrying

Common use cases

Prepare a payout for execution

Generate the quote after the beneficiary and destination are ready, then use the quote ID to execute the transaction.

Internal approval workflow

Use the quote as the pre-execution record for operations or treasury review before funds move.

Frontend-assisted or operator-assisted flows

Generate a quote first so an internal user or end user can confirm pricing details before execution begins.

Production notes

Before using this endpoint in production:

Define how long your application treats a generated quote as usable.
Confirm who is allowed to generate quotes versus execute transactions.
Store quote IDs and related transaction references for traceability.
Recheck funding and destination readiness if there is a delay before execution.

Quotes are a preparation step, not a guarantee that execution will succeed later under all conditions.

Common failure cases

Authentication fails

Check these items first:

the x-api-key header is present
the API key belongs to the intended environment
the base URL is correct

Validation errors

If the API rejects the request:

verify all required fields are present
confirm the source account and destination references are correct
check amount, currency, provider, and corridor inputs

Quote generation succeeds but execution fails later

If execution fails after a quote is generated:

confirm the quote is still valid for execution
confirm the source account still has sufficient balance
confirm the payout destination remains usable
confirm transaction-specific validation still passes at execution time

Pricing or returned details do not match expectations

If the returned quote details are unexpected:

do not execute automatically
compare the returned result against the intended transaction
correct the transaction inputs or route for review before continuing

⚠️
Needs confirmation: Exact response fields, quote expiry behavior, failure codes, and whether quotes reserve pricing or balance should be confirmed from the API schema and backend behavior.

Enterprise implementation notes

Access control

Separate quote generation from transaction execution if your operating model requires maker-checker or approval controls.

Auditability

Record:

quote ID
source account ID
beneficiary or destination reference
requested amount and currency context
creating service or user
creation timestamp

Operational controls

If quotes are used in high-volume workflows, define how your team handles regenerated quotes, stale quotes, and approval delays.

Troubleshooting checklist

Use this checklist if quote generation is blocking your flow:

Confirm authentication with x-api-key.
Confirm the source account is correct and funded.
Confirm the beneficiary and payout destination are ready.
Confirm amount, currency, provider, and route inputs are correct.
Store the returned quote ID for execution.
Execute promptly after quote creation if your flow depends on fresh pricing.

Recommended next endpoints

After you generate a quote, continue with:

Related pages

Execute Transaction

Use the returned quote ID to initiate funds movement.

Resolve Bank Account

Validate destination details before pricing the transaction.

Get transaction limits for a currency and country

Check whether the requested amount is likely to fit the corridor limits before quoting.