Skip to main content
POST
/
crypto
/
offramp
Retrieve a list of crypto offramp options
curl --request POST \
  --url https://api.slash.com/crypto/offramp \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "virtualAccountId": "<string>"
}
'
{
  "wallet": {
    "id": "<string>",
    "subaccountId": "<string>",
    "slashAccountGroupId": "<string>",
    "timestamp": "2023-11-07T05:31:56Z"
  },
  "addresses": [
    {
      "id": "<string>",
      "walletId": "<string>",
      "address": "<string>",
      "timestamp": "2023-11-07T05:31:56Z",
      "blockchainMemo": "<string>"
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.slash.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-API-Key
string
header
required

API key authentication for public API requests.

Keys come in two flavors:

  • Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
  • User-scoped keys are pinned to a user and span every legal entity that user has access to. Every request made with a user-scoped key (except GET /legal-entity, which lists the legal entities the user can access) must include an x-legal-entity header naming the legal entity the request is operating on. Requests without the header are rejected with 400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with 403.

Body

application/json
​
virtualAccountId
string
required

The id of the virtual account to offramp funds to.

​
paymentRail
enum<string>
required
Available options:
ach,
wire
​
currency
enum<string>
required
Available options:
usdt,
usdc

Response

OK

​
wallet
Wallet · object
required
​
addresses
Address · object[]
required