Create Ramp On Synthetic

Executes a ramp-on operation: receives fiat via bank deposit, converts to crypto, and credits the user's crypto balance. Combines a fiat deposit + buy order in a single atomic operation.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Optional idempotency identifier.

string

Optional session identifier.

string
required

User id, numberId, or externalId.

string
required

Crypto asset in the operation.

string
required

Fiat quote asset.

string

Amount in asset units.

string

Amount in fiat units.

string

Optional price lock code.

string

Optional exact, case-sensitive label of a deposit address or deposit-request account already configured on the user or company. Filters eligible candidates without changing network selection, account capabilities, or deposit-request generation rules. When a deposit stage is required and no compatible deposit instructions can be obtained, creation fails with INVALID_DEPOSIT_INFO. The deposit stage matches deposits with this same label. Omit to retain normal account selection; send the matching label when funding through a labeled address. See /docs/ramps-overview#select-a-deposit-account-by-label.

originDeclaration
object

Optional incoming funds declaration. Required only for an applicable CRYPTO_BRL crypto funding leg; the fiat funding leg of a ramp-on does not require it.

boolean

If true, reject when balance is insufficient instead of using company debt.

boolean

If true, skip the deposit stage when supported.

string
enum

Source of the fiat funds. USER_BALANCE (default): the user's balance on the platform, funded through the operation's deposit. VIRTUAL_ACCOUNT: the amount is debited from the user's virtual account balance; no deposit stage is created and company debt is never used.

Allowed:
boolean

Whether to use overflow funds when supported. Defaults to true.

boolean

Only available in countries that support pooled deposit accounts (e.g. ARS in Argentina). Deposits via principal accounts default to a payment QR; set to true to receive a dedicated bank account (a CVU in Argentina) for bank transfer funding instead.

destination
object
required
sender
object
recipient
object
Headers
string
required

Your Manteca API key.

Responses

400

Invalid request.

404

Referenced user, lock, or destination not found.

409

Conflict, such as invalid user status or blocked operation.

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json