GET /orders/info/{identifier}
- Method:
GET - URL:
https://pos.b4bit.com/api/v1/orders/info/{identifier} - Authentication:
X-Device-Idheader.
Parameters
Section titled “Parameters”| Param | Type | Description |
|---|---|---|
identifier | UUID v4 | The identifier returned by POST /orders/. |
Examples
Section titled “Examples”curl -H "X-Device-Id: $B4BIT_API_KEY" \https://pos.b4bit.com/api/v1/orders/info/1040095a-737d-41a2-a2e1-d031d19ec8cdconst id = '1040095a-737d-41a2-a2e1-d031d19ec8cd';const res = await fetch(`https://pos.b4bit.com/api/v1/orders/info/${id}`, {headers: { 'X-Device-Id': process.env.B4BIT_API_KEY },});const payment = await res.json();console.log(payment.status, payment.safe);import os, requests
identifier = '1040095a-737d-41a2-a2e1-d031d19ec8cd'r = requests.get( f'https://pos.b4bit.com/api/v1/orders/info/{identifier}', headers={'X-Device-Id': os.environ['B4BIT_API_KEY']},)payment = r.json()200 response
Section titled “200 response”The response is an array with the (single) Payment matching the identifier:
[ { "identifier": "1040095a-737d-41a2-a2e1-d031d19ec8cd", "reference": "ORD-123", "created_at": "2026-04-17T10:00:00+02:00", "edited_at": "2026-04-17T10:12:45+02:00", "status": "CO", "fiat_amount": 125.02, "fiat": "MXN", "crypto_amount": 0.00245, "unconfirmed_amount": 0.0, "confirmed_amount": 0.00245, "received_amount": 125.02, "currency_id": "BTC", "merchant_device_id": 42, "merchant_device": "caja-tienda-3", "address": "bc1q...", "tag_memo": "", "url_ok": "https://tu-sitio.com/pago/ok", "url_ko": "https://tu-sitio.com/pago/error", "url_standby": null, "expired_time": "2026-04-17T11:00:00+02:00", "good_fee": true, "safe": true, "rbf": false, "percentage": 100.0, "language": "es", "notes": "Pedido de prueba", "internal_data": null, "transactions": [ { "confirmed": true, "currency": "BTC", "amount": 0.00245, "tx_hash": "abc123...", "block": 834212, "created_at": "2026-04-17T10:08:30+02:00" } ] }]See payment-fields for the semantic detail of each field.
Use cases
Section titled “Use cases”- State polling when you cannot receive webhooks (for example, local dev without a tunnel).
- Reconciliation: after a questionable webhook, query this endpoint to validate the authoritative state.
- Detail for the customer: expose the current state of their order in your UI using the
percentage,status,unconfirmed_amount,confirmed_amountfields.
Errors
Section titled “Errors”403— Missing or invalidX-Device-Id.404— No order with thatidentifierexists for this device/merchant.500— Internal error.