Skip to main content
POST
Send multiple own-wallet P2P transfers atomically

Authorizations

Authorization
string
header
required

Access token issued by POST /v1/auth/token.

x-zeam-auth
string
header
required

Application secret (the apiKey issued at registration), validated at the Kong edge.

Body

application/json

Multiple same-asset transfers between the caller's own wallets, executed as one atomic Stellar transaction.

idempotencyKey
string
required
transactionId
string
required
externalReference
string
required
transfers
object[]
required

Transfer legs. All legs settle or fail together.

memo
string

Optional Stellar memo (applies to the whole transaction).

Response

Multi-transfer accepted for asynchronous processing.

A 202 means the submission was accepted for asynchronous execution, not that it settled. Track completion with the Transactions routes or webhooks.

transactionRecordId
string<uuid>
required

The transaction record id, used with GET /v1/transactions/{transactionId}.

status
string
required

Submission status; not a terminal transaction status.

Example:

"accepted"

intentId
string

Downstream intent id, when present.

isIdempotent
boolean

True when this response replays a prior submission with the same idempotencyKey.

message
string