Skip to main content
GET
You can only request data for transactions that were authorized using your API and secret key.

Authorizations

X-Processing-Key
string
header
required

Your API key.

Headers

X-Processing-Signature
string
required

Hex-encoded HMAC-SHA512 signature of the request body, generated using your secret key.

Body

application/json
id
integer
required

Internal transaction ID.

Example:

717535

Response

OK

id
integer<int32>
required
Required range: x >= 1
Example:

717535

type
string
required

Transaction type.

transactions
object[]
required

Transaction entries. Each entry has a transaction_type that determines which fields are present:

  • blockchain: On-chain transactions (has address, tag, txid, riskscore, confirmations)
  • internal: Internal transfers (has address, tag, txid, confirmations)
  • exchange: Currency exchanges (has currency_to, amount_to)
fees
object[]
required
status
enum<string>
required

Transaction status. Note: internal statuses are mapped before returning:

  • processing and verifying are returned as not_confirmed
  • error is returned as cancelled
  • rejected is returned as cancelled
Available options:
cancelled,
confirmed,
declined,
not_confirmed,
pending
foreign_id
string

This transaction's unique identifier in your system.

end_user_reference
string

End user reference. Present only when KYC data was provided.

crypto_address
object

Address details. Present only when entry has an associated address.

currency_sent
object

Sent currency details. Present for confirmed, verifying, or processing transactions.

currency_received
object

Received currency details. Present for confirmed, verifying, or processing transactions.

error
string | null

Error message. Null or empty string for successful transactions.

additional_details
object | null

Additional transaction details. Present only when available.

Last modified on July 14, 2026