> ## Documentation Index > Fetch the complete documentation index at: https://docs.ouraicalling.com/llms.txt > Use this file to discover all available pages before exploring further. # List transactions > Workspace balance ledger, newest first. `workspace_balances` is the materialized balance for the API key's active workspace. `note` contains a customer-facing description; payment-provider IDs and internal reconciliation references are never returned. **Required scope:** `billing:read` (keys without scope restrictions have full access). ## OpenAPI ````yaml /api-reference/openapi.json get /transactions openapi: 3.1.0 info: title: OurAiCalling API version: 1.0.0 description: >- REST API for OurAiCalling. Authenticate with an API key (`fam_...`, created under **Settings → API Keys**) or an OAuth 2.0 access token (`fam_at_...`) as a Bearer token. Every response uses a consistent envelope: `{ "data": ... , "meta": { ... } }` on success and `{ "error": { "code", "message" } }` on failure. List endpoints paginate with `?limit=` (default 50, max 200) and `?offset=`; `meta.pagination.total` carries the total match count. Everything documented here is also exposed as MCP tools at `https://app.famulor.io/mcp` (Model Context Protocol, streamable HTTP) using the same credentials and permission model. servers: - url: https://app.famulor.io/api/v1 description: Hosted platform. - url: https://{domain}/api/v1 description: White-label tenant domain — same paths, tenant branding. variables: domain: default: app.famulor.io description: Your white-label tenant domain. security: - bearerAuth: [] tags: - name: Account description: Self-inspection of the calling credential. - name: Migrations description: Preview and import data from supported legacy platforms. - name: Assistants description: Create and manage voice assistants. - name: Tools description: >- Reusable tools (HTTP APIs and external MCP servers) assistants can call mid-conversation. - name: Voices description: Browse the text-to-speech voice library. - name: Calls description: Start outbound calls and read call history, transcripts and recordings. - name: History description: Unified conversation history across calls, messaging and assistant emails. - name: Campaigns description: Outbound calling campaigns with a compliant power dialer. - name: Leads description: Manage Audience contacts across campaigns, channels and Call QA metrics. - name: Segments description: >- Saved, dynamic lead filters — reusable audience definitions used for Audience search and campaign lead assignment. - name: Suppression description: Cross-channel marketing opt-outs and active workspace suppression records. - name: Callbacks description: >- Scheduled callbacks booked by the Schedule callback tool across voice, chat, and email. - name: Phone Numbers description: Marketplace numbers and customer-provided numbers. - name: SIP Trunks description: Bring your own SIP provider and numbers. - name: Carrier Connections description: Connect a supported carrier account and import its existing phone numbers. - name: Knowledge Bases description: RAG knowledge bases and documents for assistants. - name: Settings description: Workspace-level settings such as caller-memory defaults. - name: Billing description: Balance and minutes ledger of the key owner. - name: Automations description: >- Native workspace automations — list, create, update, trigger. Plan gate: automation_platform. - name: Integrations description: >- Calendar integrations (Cal.com, Calendly, Acuity Scheduling, Google Calendar, Outlook, native booking engine). Assign them to assistants to provide availability and booking tools, plus provider-supported appointment lookup, cancellation, and rescheduling. - name: Bookings description: >- Native booking engine — event types with weekly availability, public booking pages at /book/{workspace}/{slug}, and the bookings they produce. - name: Dashboards description: >- Custom analytics dashboards, reusable widgets, and tenant-scoped performance analytics. Requires the custom_dashboards plan feature. - name: Catalog description: >- Read-only platform catalogs — available models, supported assistant languages, and prompt templates. - name: Simulations description: Assistant simulation tests (plan-gated). - name: Versions description: Assistant configuration version history. - name: Caller IDs description: Outbound caller ID verification. - name: Widgets description: Web widget connectors. - name: Messaging description: >- Telegram, Slack, and Messenger text bots linked to assistants (Chat SDK). Includes conversation delay, inactivity end, and conversation-ended webhooks. - name: QA description: Cohort AI Quality Assurance runs over call transcripts. - name: White Label description: >- Manage the customers of your white-label workspace on their behalf — list, register, mint access tokens, log in, log out, and transfer credits. Available to reseller workspaces with white-label access, and to platform admins (scoped to direct platform customers). Requires `platform:read` / `platform:write`. - name: API Keys description: >- Self-service API keys for the calling workspace. A key can only mint further keys with a scope subset of its own. - name: SMS description: Outbound SMS from workspace phone numbers. paths: /transactions: get: tags: - Billing summary: List transactions description: >- Workspace balance ledger, newest first. `workspace_balances` is the materialized balance for the API key's active workspace. `note` contains a customer-facing description; payment-provider IDs and internal reconciliation references are never returned. **Required scope:** `billing:read` (keys without scope restrictions have full access). operationId: listTransactions parameters: - name: type in: query schema: type: string enum: - transfer - call_usage - purchase - plan_included - admin_adjust - email_usage - crawl_usage - sla_fee - retranscribe_usage - sms_usage - simulation_usage - reanalyze_usage - card_collect_usage - chat_usage - messaging_usage - qa_usage - automation_usage - milian_usage description: Filter by transaction type. - $ref: '#/components/parameters/limit' - $ref: '#/components/parameters/offset' responses: '200': description: Ledger entries. content: application/json: schema: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/Transaction' meta: type: object description: >- Response metadata. `pagination.total` is the total number of matching items (ignoring limit/offset). properties: pagination: type: object properties: limit: type: integer example: 50 offset: type: integer example: 0 total: type: integer example: 3 currency: type: string description: >- Denomination of any cents-based ledger fields — always EUR (canonical). example: EUR display_currency: type: string description: >- Workspace's resolved display currency (reseller customers inherit their reseller's currency). example: USD display_currency_rate: type: number description: >- Units of display_currency per 1 EUR; 0 when the platform has not configured a rate yet. example: 1.08 example: data: - id: tx1b2c3d-0000-4000-8000-000000000090 type: call_usage delta_minutes: -3.4 note: Call usage call_id: c1b2c3d4-0000-4000-8000-000000000010 created_at: '2026-07-01T10:03:30Z' - id: tx1b2c3d-0000-4000-8000-000000000091 type: plan_included delta_minutes: 1000 note: Plan payment call_id: null created_at: '2026-07-01T00:00:00Z' meta: pagination: limit: 50 offset: 0 total: 2 currency: EUR display_currency: USD display_currency_rate: 1.08 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' components: parameters: limit: name: limit in: query schema: type: integer minimum: 1 maximum: 200 default: 50 description: Page size (1–200). offset: name: offset in: query schema: type: integer minimum: 0 default: 0 description: Number of items to skip. schemas: Transaction: type: object properties: id: type: string format: uuid type: type: string enum: - transfer - call_usage - purchase - plan_included - admin_adjust - email_usage - crawl_usage - sla_fee - retranscribe_usage - sms_usage - simulation_usage - reanalyze_usage - card_collect_usage - chat_usage - messaging_usage - qa_usage - automation_usage - milian_usage delta_minutes: type: number description: Minutes credited (positive) or debited (negative). delta_credits: type: number description: Purchased-wallet credits credited (positive) or debited (negative). delta_plan_credits: type: number description: Plan-period credits credited (positive) or debited (negative). note: type: string description: >- Customer-facing description such as `Credit top-up`, `Automatic top-up`, or `Plan payment`. Internal payment, call, message, and reconciliation references are omitted. call_id: type: - string - 'null' format: uuid description: Set for `call_usage` entries. created_at: type: string format: date-time required: - id - type - delta_minutes - delta_credits - delta_plan_credits - created_at ErrorEnvelope: type: object description: Error envelope returned by every /api/v1 endpoint on failure. required: - error properties: error: type: object required: - code - message properties: code: type: string enum: - unauthorized - forbidden - not_found - invalid_request - rate_limited - conflict - telephony_configuration_error - telephony_unavailable - internal_error description: Stable, machine-readable error code. message: type: string description: Human-readable description of the error. responses: BadRequest: description: Invalid request body or parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: invalid_request message: '"to_number" is required (E.164 format, e.g. +4930123456).' Unauthorized: description: Missing, invalid, expired or revoked API key / access token. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: unauthorized message: Invalid API key. Forbidden: description: >- The API key lacks the required scope, or the plan does not allow this action. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: forbidden message: This API key is missing the required scope "assistants:write". securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API key description: >- API key (`fam_...`, created under **Settings → API Keys**) or an OAuth 2.0 access token (`fam_at_...`). Keys can be restricted to scopes such as `assistants:read`, `calls:write`, `campaigns:write`, `automations:read`, `dashboards:read`, `dashboards:write`, `leads:write`, `segments:write`, `phone_numbers:write`, `sip_trunks:write`, `knowledge:write`, `voices:read`, `billing:read`, `settings:write`, `platform:read`, `platform:write`; a `*:write` scope implies the matching `*:read`. Automation and dashboard endpoints also accept the legacy `calls:*` scope. Keys without scope restrictions have full access. ````