Skip to main content
POST
Create Address
Auth method: Signed (HMAC) — this endpoint requires the full set of signed headers: x-access-id, x-request-id, x-timestamp, and an HMAC-SHA256 authorization signature. See Authentication.
Creates a new address slot in an existing wallet, with one address per requested network. All addresses created by one call share the same address_reference.
address_reference values are globally unique across Tender. Reusing one, even in a different wallet, fails with 409.

Example

Headers

string
required
Base64-encoded HMAC-SHA256 signature of {"timeStamp":"<x-timestamp>","requestId":"<x-request-id>","accessId":"<x-access-id>"}, signed with your access secret. The request body is not part of the signature.Example: "pV3n0o8kq0lK2mJ8bZ1yq3Yt6hR0cXK9u4mVJ2l9sE0="
string
required
ISO 8601 timestamp; must be within 5 minutes of server timeExample: "2026-10-15T09:45:53.000Z"
string
required
A unique UUID v4 per requestExample: "550e8400-e29b-41d4-a716-446655440000"
string
required
Your API access IDExample: "your-access-id-here"
string
required
Example: "application/json"

Body

string
required
The reference of a wallet you created with Create Wallet.Example: "acme-user-8821"
string
required
Your label for the new address slot. Must be unique across Tender. Maximum 500 characters.Example: "acme-user-8821-slot-2"
string[]
required
Networks to create addresses on (at least one). Use EVM, TRON or BTC. The aliases ethereum, eth, trx and bitcoin are also accepted, but each returned network echoes the value you sent, so use the canonical values to keep your records consistent with the rest of the API.Example: ["EVM", "TRON"]

Response

string
required
Example: "success"
string
required
Example: "success"
object
required
Additional fields may be present; ignore fields you don’t recognise.

Error responses

Authorizations

authorization
string
header
required

Signed (HMAC) authentication. Required headers: x-access-id, x-request-id (UUID v4), x-timestamp (ISO 8601, must be within 5 minutes of server time), and authorization: the Base64 HMAC-SHA256 of the JSON string {"timeStamp":"","requestId":"","accessId":""} (keys in that order, no whitespace) using your access secret. The request body, method and path are not signed. The API key must be linked to an outlet.

Headers

authorization
string
required

Base64-encoded HMAC-SHA256 signature of {"timeStamp":"","requestId":"","accessId":""}, signed with your access secret. The request body is not part of the signature.

x-timestamp
string<date-time>
required

ISO 8601 timestamp; must be within 5 minutes of server time

x-request-id
string<uuid>
required

A unique UUID v4 per request

x-access-id
string
required
Content-Type
string
required

Body

application/json
wallet_reference
string
required
Maximum string length: 500
Example:

"acme-user-8821"

address_reference
string
required

Globally unique across Tender.

Maximum string length: 500
Example:

"acme-user-8821-slot-2"

networks
string[]
required

EVM, TRON or BTC (aliases ethereum, eth, trx, bitcoin accepted).

Minimum array length: 1
Example:

Response

Addresses created

status
string
required
Example:

"success"

message
string
required
Example:

"success"

data
object
required