Create Counterparty by Link
POST/v1/crossborder/clients/:client_id/counterparties/by-link
Create a new crossborder counterparty by link. The counterparty will be associated with the specified client.
Request
Path Parameters
Unique identifier (UUID) of the client that will own this counterparty.
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
- application/json
Body
required
Full name of the client. Must be a valid string with maximum 80 characters. For legal entities, the name field corresponds to the legal name.
Possible values: [NATURAL_PERSON, LEGAL_PERSON]
Type of client entity. NATURAL_PERSON for individuals, LEGAL_PERSON for companies or organizations.
Valid email address of the client. Used for communication and notifications. Maximum 255 characters.
Responses
- 201
- 400
- 401
- 422
Counterparty created by link successfully.
- application/json
- Schema
- Example (from schema)
Schema
Unique identifier (UUID) of the created counterparty.
Full name of the counterparty. For legal entities, the name field corresponds to the legal name.
Possible values: [NATURAL_PERSON, LEGAL_PERSON]
Type of counterparty entity. NATURAL_PERSON for individuals, LEGAL_PERSON for companies or organizations.
Email address of the counterparty.
Possible values: [ACTIVE, INACTIVE, PENDING]
Current status of the counterparty.
External URL of the counterparty.
Counterparty created date.
Counterparty updated date.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"name": "John Doe",
"type": "NATURAL_PERSON",
"email": "john.doe@example.com",
"status": "PENDING",
"external_url": "https://www.example.com",
"created_at": "2026-03-26T14:02:59.422Z",
"updated_at": "2026-03-26T14:02:59.422Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.