Pre-quote lite

Overview

POST /partner/pre-quote-lite returns an indicative pricing summary for a corridor (best / worst / averages). It uses the same pricing engine as widget pre-quote but does not return a full options[] list and is never binding.


Auth	`X-API-Key` or Partner Portal Clerk session
Feature flag	Partner `allowedApis` must include `pre-quote-lite` (or leave unset for all-enabled)
Rate limit	30 requests / minute
Portal	Developer → Pre-quote lite

Example

curl -X POST https://raas-widgets-backend-sandbox.up.railway.app/partner/pre-quote-lite \
  -H "X-API-Key: raas_sandbox_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "originCountryCode": "US",
    "destinationCountryCode": "MX",
    "amount": 1000,
    "anchor": "send",
    "fundingMethod": "DEBIT_CARD",
    "payoutMethod": "CASH_PICKUP",
    "payerCode": "OXXO"
  }'

{
  "success": true,
  "data": {
    "count": 4,
    "best": {},
    "worst": {},
    "rankingMetric": "receiveAmount",
    "receiveAmount": { "min": 16980, "max": 17120, "avg": 17050 },
    "asOf": "2026-07-15T12:00:00.000Z",
    "indicative": true
  }
}

If nothing is offerable, you still get HTTP 200 with count: 0 and no best / worst — treat that as an empty market, not a transport error.

Catalog payers (helper)

curl "https://raas-widgets-backend-sandbox.up.railway.app/partner/pre-quote-lite/catalog/payers?destinationCountryCode=MX&payoutMethod=CASH_PICKUP&originCountryCode=US" \
  -H "X-API-Key: raas_sandbox_your_api_key_here"

Binding quotes

Widget flows obtain binding quotes later (signedQuote) before create operation. Pre-quote lite is for partner UX such as “from / to” ranges — not for commit.

Compatibility endpoints (brief)

Some partners still call older Request / Deferred surfaces. Prefer the flow-based POST /partner/links model documented in this site. For migration contexts only:

Compat path	Notes
`/v1/request-money`	Legacy Request Money API shape
`/v1/deferred-payout`	Legacy deferred payout origination

Contact your Leap integration specialist before relying on /v1/* in new work. New integrations should use request, fund-request, and deferred payout flows. How Request API becomes a fund-request link and then an operation: Request API · Lifecycle.

Getting Started

Request API

Concepts

Integration

Flows

Webhooks

Operations

Overview

Example

Catalog payers (helper)

Binding quotes

Compatibility endpoints (brief)

Next steps

Quick start

API overview

​Overview

​Example

​Catalog payers (helper)

​Binding quotes

​Compatibility endpoints (brief)

​Next steps

Quick start

API overview

Overview

Example

Catalog payers (helper)

Binding quotes

Compatibility endpoints (brief)

Next steps