Skip to main content
GET
/
api
/
v1
/
transaction
/
{transactionId}
Get transaction by ID
curl --request GET \
  --url https://sandbox.api.afriex.com/api/v1/transaction/{transactionId} \
  --header 'x-api-key: <api-key>'
{
  "data": {
    "status": "SUCCESS",
    "type": "SWAP",
    "channel": "WALLET",
    "sourceAmount": "10",
    "sourceCurrency": "USD",
    "destinationAmount": "14101.041",
    "destinationCurrency": "NGN",
    "destinationId": "",
    "customerId": "68e6717848e1f632e9686460",
    "transactionId": "69d3c79531c0234586ad5ee0",
    "meta": {
      "reference": "ref-swap-minimal-002",
      "idempotencyKey": "idem-swap-minimal-002"
    },
    "createdAt": "2026-04-06T14:47:49.166Z",
    "updatedAt": "2026-04-06T14:47:49.166Z"
  }
}
Retrieve a specific transaction by its unique identifier.

Authorizations

​
x-api-key
string
header
required

Static business API key issued from the dashboard. A business can provision multiple API keys, each scoped to a configurable set of permissions (e.g. read transactions, create deposits, etc). Permissions are chosen per key at creation time in the dashboard and may be revoked by deleting the key. Requests made with a key that does not include the permission required by the target endpoint will be rejected with a 403 Forbidden response; an unrecognised, malformed or revoked key returns 401 Unauthorized. Manage your keys and their permissions under Developer → API keys in the dashboard.

Headers

​
x-api-signature
string

Signature of the request payload, used for request authentication where payload signing is enabled for your business.

​
x-api-version
string

API version in ISO 8601 format (e.g. 2025-12-28). Defaults to latest stable.

Path Parameters

​
transactionId
string
required

The unique identifier of the transaction

Response

Transaction retrieved successfully.

​
data
object