Skip to main content
POST
Execute an internal account-to-account transfer

Authorizations

Authorization
string
header
required

eToro OAuth2. Each operation lists the scopes that grant access as separate security requirements (OpenAPI OR semantics): the caller's token only needs ONE of them — you do NOT need all of them. The same scopes back the x-api-key/x-user-key credential pair.

Headers

x-request-id
string<uuid>
required

A unique request identifier.

Example:

"e424f4ba-e647-4854-8f15-6bb043a947cd"

x-api-key
string<password>
required

API key for authentication.

Example:

"lhgfaslk21490FAScVPkdsb53F9dNkfHG4faZSG5vfjndfcfgdssdgsdHF4663"

x-user-key
string<password>
required

User-specific authentication key.

Example:

"eyJlYW4iOiJVbnJlZ2lzdGVyZWRBcHBsaWNhdGlvbiIsImVrIjoiOE5sZ2cwcW5EUVdROUFNWGpXT2lmOWktZnpidG5KcUlqWGJ3WHJZZkpZcldrbG90ZEhvLVBjSWhQaU8xU1ZtMW84aU1WZGZqN2xWNzFjLXFxLmcybXE1dnh4Q1hUT25xaWRUaTFlcEhmVk1fIn0_"

Body

application/json

Request model for executing an internal transfer

requestReferenceId
string
required

Client reference / idempotency key.

Example:

"client-ref-8f3a-001"

sourceAccount
object
required

Account identifier for a transfer participant

destinationAccount
object
required

Account identifier for a transfer participant

amount
number<double>
required

Amount to transfer.

Example:

250

currency
string | null
required

ISO 4217 alphabetic currency code; must match the source account currency.

Example:

"USD"

extraData
object | null

Optional client metadata (opaque JSON object).

Response

Transfer accepted; returns transfer id and optional echoed request reference id.

Response after executing a transfer

transferId
integer<int64>
required

Server transfer identifier.

Example:

9876543210

requestReferenceId
string | null

Echo of client requestReferenceId when provided.

Example:

"client-ref-8f3a-001"