curl --request POST \
  --url https://api.ripio.com/wallet/contacts/ \
  --header 'Content-Type: application/json' \
  --header 'authorization: <authorization>' \
  --header 'signature: <signature>' \
  --header 'timestamp: <timestamp>' \
  --data '
{
  "type": "crypto",
  "entity_name": "My BTC wallet",
  "network": "bitcoin",
  "currency": "BTC",
  "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
}
'

{
  "error_code": null,
  "message": null,
  "data": {}
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

Contacts

Create External Contact (crypto, Bank Or Rp_tag)

Creates a new contact. The body field type discriminates the flow: crypto saves a blockchain address (network + currency codes), bank saves an AR/ARS banking account (entity_number — CBU/alias; replaces the old type=fiat, which now responds 400), or rp_tag adds another Ripio account as a P2P contact by its rp_tag handle (auto-whitelisted on creation, same semantics as the now-deprecated legacy rp_tag endpoint).

Idempotent + auto-whitelist (crypto/bank): If an equivalent crypto/bank contact already exists for this account it is returned without creating a duplicate — and if it was not yet whitelisted, it is whitelisted as part of this call.

Rate limit: Subject to the contacts_gateway_hour hourly rate limit. Only write operations (POST and DELETE) count toward this limit; GET is not throttled.

Requires the contacts_write permission. The account must be fully operative.

NOTE: Contacts created via this endpoint are automatically whitelisted, meaning they will not require OTP for operations. For this reason it is strongly recommended to have a separate api key with the contacts_write permission.

Authorization

Requires a valid API key.

POST

wallet

contacts

curl --request POST \
  --url https://api.ripio.com/wallet/contacts/ \
  --header 'Content-Type: application/json' \
  --header 'authorization: <authorization>' \
  --header 'signature: <signature>' \
  --header 'timestamp: <timestamp>' \
  --data '
{
  "type": "crypto",
  "entity_name": "My BTC wallet",
  "network": "bitcoin",
  "currency": "BTC",
  "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
}
'

{
  "error_code": null,
  "message": null,
  "data": {}
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

{
  "error_code": "ERR_0008",
  "message": "Invalid Gateway JWT",
  "data": null
}

Headers

authorization

string

required

The API key as a string.

signature

string

required

See the Generating Signature section for more details.

timestamp

number

required

A timestamp in milliseconds. See the Timestamp Security section for more details.

timstamp-tolerance

number

An additional, non-required parameter, that you can send to specify the number of milliseconds after the timestamp for the request to be valid. See the Timestamp Security section for more details.

Body

application/json

The body is of type object.

Response

Contact created (or returned if already existed, for crypto/bank).

error_code

string

required

Example:

null

message

string

required

Example:

null

data

object

required

⌘I

Introduction

Ripio Wallet

Ripio Trade

Create External Contact (crypto, Bank Or Rp_tag)

Headers

Body

Response