GET
/
api
/
v1
/
end-users
/
{end_user_id}
/
auto-swap-addresses
/
curl --request GET \
  --url https://sandbox-b2b.ripio.com/api/v1/end-users/{end_user_id}/auto-swap-addresses/ \
  --header 'Authorization: Bearer <token>'
[
  {
    "network": "BITCOIN",
    "end_user_id": "user_1",
    "address": "1Lbcfr7sAHTD9CgdQo3HTMTkV8LK4ZnX71",
    "target_address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "xpub": "ks3tMd",
    "derivation_path": "m/24"
  },
  {
    "network": "ETHEREUM_SEPOLIA",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "ETHEREUM",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "POLYGON",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "POLYGON_MUMBAI",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  }
]

Authorizations

​
Authorization
string
header
required

B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:

  • clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.

Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.

Every request must be accompianed by an Authorization header with a value that follows the following schema: Bearer ACCESS_TOKEN

Path Parameters

​
end_user_id
string
required

End user's external ref, usually a uuid.

Query Parameters

​
token
enum<string>

Network's token to filter addresses

Available options:
BTC,
ETH

Response

200 - application/json

OK

The response is of type AutoSwapAddress · object[].

GET
/
api
/
v1
/
end-users
/
{end_user_id}
/
auto-swap-addresses
/
curl --request GET \
  --url https://sandbox-b2b.ripio.com/api/v1/end-users/{end_user_id}/auto-swap-addresses/ \
  --header 'Authorization: Bearer <token>'
[
  {
    "network": "BITCOIN",
    "end_user_id": "user_1",
    "address": "1Lbcfr7sAHTD9CgdQo3HTMTkV8LK4ZnX71",
    "target_address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "xpub": "ks3tMd",
    "derivation_path": "m/24"
  },
  {
    "network": "ETHEREUM_SEPOLIA",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "ETHEREUM",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "POLYGON",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  },
  {
    "network": "POLYGON_MUMBAI",
    "end_user_id": "user_1",
    "address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE543a3",
    "target_address": "0x3c03a69dEce0A387764d2c1cEC315AC6cBE542b2",
    "xpub": "wSeET7",
    "derivation_path": "m/24"
  }
]

Authorizations

​
Authorization
string
header
required

B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:

  • clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.

Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.

Every request must be accompianed by an Authorization header with a value that follows the following schema: Bearer ACCESS_TOKEN

Path Parameters

​
end_user_id
string
required

End user's external ref, usually a uuid.

Query Parameters

​
token
enum<string>

Network's token to filter addresses

Available options:
BTC,
ETH

Response

200 - application/json

OK

The response is of type AutoSwapAddress · object[].