Skip to main content

Documentation Index

Fetch the complete documentation index at: https://stabyl.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Use wallet transaction reads to reconcile account activity across fiat deposits, stablecoin deposits, fees, adjustments, refunds, and withdrawals initiated from Stabyl Pro.
EndpointPurpose
GET /partner/wallets/transactionsList wallet activity
GET /partner/wallets/transactions/{id}Read one transaction by public identifier
The timeline can include deposits, fees, adjustments, refunds, and withdrawals initiated from Stabyl Pro web. Use transaction id as the stable public identifier. Use rail, currency, and settlement_rail to distinguish NGN fiat, USD cash, USDT, and USDC activity.

​
Listing Transactions

curl "https://api-staging.stabyl.com/v1/partner/wallets/transactions?currency=USD&limit=50" \
  -H "X-Api-Key: $STABYL_API_KEY"
Use cursor pagination for backfills. Do not assume a page boundary is stable while new activity is happening; store the highest processed transaction timestamp and transaction ID in your own reconciliation job.

​
Reading One Transaction

curl https://api-staging.stabyl.com/v1/partner/wallets/transactions/0198b755-a2a2-76ee-9f4f-a650cd51586c \
  -H "X-Api-Key: $STABYL_API_KEY"
Use the detail route when an operator opens a record, when a reconciliation job finds a gap, or when your system needs to refresh the status of a known transaction.

​
Status Handling

StatusMeaning
pendingActivity is known but not final
completedWallet balance has been updated
failedActivity did not complete
cancelledActivity was cancelled before completion

​
Reconciliation Pattern

  1. Poll the list endpoint with conservative page sizes.
  2. Upsert transactions by public id.
  3. If a known transaction changes status, update your local record instead of creating a duplicate.
  4. Stop polling individual transactions after they are terminal.
  5. Keep raw request IDs and timestamps in your logs for support.

​
Required Headers

Transaction reads require X-Api-Key enabled for wallet reads. Common failures include invalid filters, requesting a transaction outside the account context, or querying a transaction before it appears in the timeline.