> ## Documentation Index > Fetch the complete documentation index at: https://guides.saber.money/llms.txt > Use this file to discover all available pages before exploring further. # Get External Buy Detail > Retrieve the details of an external buy transaction. This route currently supports only `transaction_type=BUY`. **Response field values** | Field | Possible Values | | --- | --- | | `transaction_type` (path) | `BUY` | | `transaction_type` (response) | `CRYPTO_BUY` | | `status` | Typically `PROCESSING` for an in-flight transaction | ## OpenAPI ````yaml openapi-v2.json GET /api/v2/wallet/w/transaction/{transaction_type}/{transaction_id} openapi: 3.1.0 info: title: Saber Money API (v2) version: v2 description: >- ## Authentication There is no standalone API-key auth — every request must be **signed**. An API key by itself authenticates nothing. Each call requires four headers together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey + timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required — keyed with your API secret), `X-Timestamp` (unix seconds), and `X-Request-Id` (any unique string per request). The signature must be computed by a client script; there is no way to derive it by hand. Use the HMAC Generator flow to compute valid values for manual testing. ## Common Authentication Errors - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id invalid","success":false} - **Invalid Secret**: {"error_code":6090,"message":"invalid secret","success":false} - **Timestamp (Older than 10 secs)**: {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false} servers: - url: https://api.saber.money security: [] paths: /api/v2/wallet/w/transaction/{transaction_type}/{transaction_id}: get: tags: - Onramp summary: Get External Buy Detail description: > Retrieve the details of an external buy transaction. This route currently supports only `transaction_type=BUY`. **Response field values** | Field | Possible Values | | --- | --- | | `transaction_type` (path) | `BUY` | | `transaction_type` (response) | `CRYPTO_BUY` | | `status` | Typically `PROCESSING` for an in-flight transaction | operationId: get-buy-transaction-details-v2 parameters: - name: transaction_type in: path required: true description: Must be `BUY`. schema: type: string description: Must be `BUY`. - name: transaction_id in: path required: true description: External buy transaction UUID. schema: type: string description: External buy transaction UUID. - name: X-Api-Key in: header required: true description: Your API key (configured in credentials) schema: type: string - name: X-Signature in: header required: true description: >- HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256 of `apiKey + timestamp` (or `apiKey + timestamp + userId` when X-User-Id is required), keyed with your API secret. The HMAC Generator flow computes this for you. schema: type: string - name: X-Timestamp in: header required: true description: >- Unix timestamp in seconds (auto-generated) Unix seconds, e.g. `Math.floor(Date.now() / 1000)`. Must match the timestamp used in the X-Signature computation. schema: type: string - name: X-Request-Id in: header required: true description: >- Unique request identifier (auto-generated) Any unique string per request, e.g. a UUID. schema: type: string - name: X-User-Id in: header required: true description: User UUID (set above) schema: type: string responses: '200': description: Successful response content: application/json: schema: type: object properties: success: type: boolean data: type: object properties: id: type: string transaction_type: type: string enum: - BUY - CRYPTO_BUY status: type: string enum: - PROCESSING crypto_symbol: type: string fiat_symbol: type: string source_id: type: string payment_method: type: string withdraw_address: type: string network: type: string tag: type: string crypto_amount: type: number fiat_amount: type: integer base_price: type: number final_price: type: number total_fee: type: number fee_currency: type: string fee_breakup: type: object created_at: type: integer updated_at: type: integer txn_hash: type: string example: success: true data: id: 019680e1-c74f-79b7-9a0b-cc316731bfd4 transaction_type: CRYPTO_BUY status: PROCESSING crypto_symbol: USDT fiat_symbol: EUR source_id: IT78R36772223000EM0005782376 payment_method: sepa_transfer withdraw_address: '0xf82010290b2c3169ffaB5354d7Bbd09Eb2822724' network: MATIC tag: '' crypto_amount: 108.4 fiat_amount: 100 base_price: 0.9225 final_price: 0.928 total_fee: 0.6 fee_currency: USDT fee_breakup: platform_fee: 0.2 network_fee: 0.3 client_fee: 0 discount: 0 tax_on_fee: 0.1 tds: 0 created_at: 1774346040000 updated_at: 1774346041000 txn_hash: '' '404': description: '`4004`: Transaction not found' content: application/json: schema: type: object properties: success: type: boolean enum: - false errors: type: array items: type: object properties: code: type: - integer - string text: type: string example: code: 4004 text: Transaction not found ```` ## Related topics - [Get External Sell Transaction Details](/api-reference/offramp/from-external-wallet/get-external-sell-transaction-details.md) - [Get Pool Buy Transaction Details](/api-reference/onramp/to-pool-wallet/get-pool-buy-transaction-details.md) - [Get Sell Transaction Details](/api-reference/offramp/from-user-wallet/get-sell-transaction-details.md) - [Get Crypto Deposit Transaction Details](/api-reference/wallet-operations/crypto-deposit/get-crypto-deposit-transaction-details.md) - [Get Pool Sell Transaction Details](/api-reference/offramp/from-pool-wallet/get-pool-sell-transaction-details.md)