Endpoints
Partner Transactions
Access detailed financial ledgers for every credit and debit event across your Vobiz reseller ecosystem - essential for monthly billing reconciliation and dispute resolution.
GET
List customer transactions
← Partner API Reference
Detailed financial ledgers for every credit and debit event across your partner ecosystem. Use these for monthly billing reconciliation, dispute resolution, and auditing balance movements between your account and your customers.
All Partner API requests use
X-Auth-ID and X-Auth-Token headers. See Authentication for details.Overview
Two endpoints cover different scopes of transaction data:- Customer Transactions - All debits and credits for one specific customer. Use for per-customer invoicing and customer-facing statements.
- All Transactions (Global) - Global ledger across every customer under your partner account. Use for platform-wide reconciliation and monthly financial close.
Customer Transactions
Returns a paginated transaction ledger for one specific customer. Filter by transaction type and date range to generate statements for a specific billing period.Query Parameters
| Parameter | Default | Description |
|---|---|---|
page | 1 | Page number (1-indexed) |
per_page | 20 | Items per page (max 100) |
from_date | - | Start date in YYYY-MM-DD format |
to_date | - | End date in YYYY-MM-DD format |
transaction_type | - | Filter to recharge, debit, refund, or transfer |
All Transactions (Global)
Global reconciliation log - all transaction events across every customer under your partner account in a single paginated response. Same filter parameters as the per-customer endpoint. Essential for platform-wide monthly financial close.If you only need a single customer’s ledger, prefer the per-customer endpoint above - it returns a
summary block scoped to that customer. To reconcile across all customers when the global endpoint is unavailable to you, page through GET /accounts and call the per-customer ledger for each auth_id.Response fields
| Field | Notes |
|---|---|
transactions[].id | UUID of the ledger entry. |
transactions[].account_id | The customer auth_id the entry belongs to. |
transactions[].type | Ledger direction - credit or debit. This is not the same vocabulary as the transaction_type filter (see below). |
transactions[].amount | Positive integer in the account currency. The sign is implied by type, not by the number. |
transactions[].reference | Machine reference. Partner balance transfers use the form ptc:<partner_id>:<customer_auth_id>:<unix_ts>. |
transactions[].status | completed for settled entries. |
summary | Aggregates for the filtered window: total_transactions, total_debit, total_credit, net_amount, and a by_reference_type breakdown. |
total / page / per_page / total_pages | Pagination over the full filtered result set. |
Transaction types (filter values)
recharge- Wallet top-up credited to the customer. Reflected as acreditrow. Amount is positive.debit- Automatic usage deduction for completed calls and DID fees. Reflected as adebitrow. Generated per call or in daily batches depending on configuration.refund- Credit issued for a disputed charge or service outage. Reflected as acreditrow.transfer- A partner-to-customer balance transfer. On the customer ledger this lands as acredit(with descriptionTransfer from partner …); on your partner ledger the matchingdebitappears.
Monthly Billing Guide
Use transactions to generate accurate invoices for your customers:- Pull all debits for the billing period - Filter by
transaction_type=debitand the billing window dates. Sum the absolute amounts. - Add your margin - Apply your reseller markup on top of the raw usage cost before invoicing.
- Check recharge history - Confirm the customer has covered their previous balance transfers before issuing the next invoice.
- Global reconciliation - Use the global endpoint at month-end to reconcile your master ledger against the sum of all customer ledgers.
Authorizations
Your Vobiz account Auth ID
Your Vobiz account Auth Token
Path Parameters
Query Parameters
Example:
"2026-03-01"
Example:
"2026-03-31"
Available options:
recharge, debit, refund, transfer