Create Managed Deposit Intent

This is the first step in the process of a managed deposit.

POST /transfer/managed/deposit-intents

Create Managed Deposit Intent

cURL

curl --request POST \
  --url https://api.paxos.com/v2/transfer/managed/deposit-intents \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "identity_id": "<string>",
  "profile_id": "<string>",
  "destination_crypto_networks": [],
  "asset": "<string>"
}
'

200

{
  "id": "<string>",
  "link_token": "<string>",
  "client_id": "<string>"
}

Authorizations

Authorization · string · header · required

Paxos APIs use OAuth 2 with the client credentials grant flow.

Token URLs:

• Production: https://oauth.paxos.com/oauth2/token
• Sandbox: https://oauth.sandbox.paxos.com/oauth2/token

Learn more in the API credentials guide →

Body

application/json

identity_id · string · required

The Paxos ID of the Identity associated with the transfer.

profile_id · string · required

The target Profile of the transfer.

destination_crypto_networks · enum<string>[]

Possible network to accept the deposit on.

A CryptoNetwork is a blockchain transmitting cryptocurrencies.

• STELLAR: @hidden
• XLAYER: @hidden

Available options: BITCOIN, ETHEREUM, BITCOIN_CASH, LITECOIN, SOLANA, POLYGON_POS, BASE, ARBITRUM_ONE, STELLAR, INK, XLAYER

asset · string

The token or asset to deposit. E.g. "ETH", "PYUSD".

Response

200 - application/json

A successful response.

id · string

The ID of the managed deposit intent.

link_token · string

The link token used in initializing the Mesh SDK. See https://docs.meshconnect.com/guides/web-sdk.

client_id · string

The client id used in initializing the Mesh SDK. See https://docs.meshconnect.com/guides/web-sdk.