List 0Gate transactions

0Gate is the primary public integration path for hosted payment, ramp, and swap experiences. Keep secret-key operations on your server and hand only browser-safe values to the widget.

This endpoint returns the partner-scoped PartnerTransaction records behind your sessions, newest first, as a cursor-paginated list. Use it to reconcile orders against your own ledger and to power support tooling — never depend on browser callbacks alone for the source of truth.

Endpoint

Use it for

List partner transaction records for support and reconciliation. The list is scoped to the authenticated partner: records that belong to another partner are never returned and are not distinguishable from records that do not exist.

Use this endpoint only for the partner-scoped resource it describes. Store your own reference id, the returned refid, the request id, timestamps, and the current status so support and reconciliation do not depend on browser callbacks alone.

For local payment or payout rails, transaction records can include local_rail_transaction_id. Use that generic field for rail-side reconciliation; facilita_transaction_id may still appear as a deprecated compatibility alias on older records.

Production rules

• Keep secret keys on your server. This endpoint requires an sk_* key.
• Page with the cursor. Loop on has_more until it is false — do not stop because a page returned fewer rows than limit (see below).
• Filter server-side with status and session_id rather than pulling everything and filtering in your app.
• Branch on machine-readable status, error code, object id, and request id.
• Treat examples and placeholder ids as fake data only.

Request

This is a GET with no request body. All inputs are query parameters.

Response

The response is a standard list envelope whose data array holds PartnerTransaction objects.

The PartnerTransaction object

This is the REST shape returned by both list and retrieve. Every monetary and amount value is a decimal string, never a float.

Action values

Examples

curl 'https://gate-api.0bit.app/v1/transactions?limit=10&status=completed' \
  -H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

{
  "object": "list",
  "data": [
    {
      "object": "transaction",
      "refid": "0g_txn_abc123",
      "session_id": "gs_test_000000000123",
      "action": "BUY",
      "status": "completed",
      "token": "USDT",
      "network": "tron",
      "currency": "EUR",
      "payment_method": "sepa_credit_transfer",
      "fiat_amount": "100.00",
      "token_amount": "93.20",
      "total_pay_or_receive": "100.00",
      "exchange_rate": "1.0731",
      "total_fees": "1.20",
      "created_at": "2026-01-01T00:00:00Z",
      "updated_at": "2026-01-01T00:02:15Z",
      "status_timeline": [
        { "status": "CREATED", "at": "2026-01-01T00:00:00Z" },
        { "status": "completed", "at": "2026-01-01T00:02:15Z" }
      ]
    }
  ],
  "has_more": true,
  "url": "/v1/transactions"
}

async function listAll() {
  const out = [];
  let cursor = null;
  do {
    const params = new URLSearchParams({ limit: '100' });
    if (cursor) params.set('starting_after', cursor);
    const res = await fetch(
      `https://gate-api.0bit.app/v1/transactions?${params}`,
      { headers: { Authorization: 'Bearer sk_test_...' } },
    );
    const { data, has_more } = await res.json();
    out.push(...data);
    // Advance the cursor only when the page is non-empty.
    if (data.length) cursor = data[data.length - 1].refid;
    // Keep going while has_more is true — even on a short/empty page.
    if (!has_more) break;
  } while (true);
  return out;
}

Errors

All errors use the unified envelope and carry an X-Request-Id response header. Branch on code/type/statusCode, not on the free-form message.

{
  "type": "unauthorized",
  "code": "unauthorized",
  "message": "Example error using fake data.",
  "request_id": "req_test_000000000123",
  "doc_url": null,
  "statusCode": 401
}

Public boundary

This reference covers partner-scoped endpoint behavior, authentication, idempotency, webhook verification, and support-safe records. Internal operations, settlement venues, rail providers, administrative routes, and unsupported availability claims are outside the public API contract.

Related pages