Credits and transactions - Karta API

Read your balance

curl --fail-with-body 'https://api.getkarta.ai/public/v1/billing' \
  -H "Authorization: Bearer $KARTA_API_KEY"

{
  "credit_balance": 125.5,
  "feature_scoped": [{"feature": "voice", "credit_balance": 30}]
}

The top-level balance is general-purpose credit. feature_scoped balances are restricted to their named features.

Find transactions

Filter by a request context:

curl --fail-with-body --get 'https://api.getkarta.ai/public/v1/billing/transactions' \
  -H "Authorization: Bearer $KARTA_API_KEY" \
  --data-urlencode "request_id=$REQUEST_CONTEXT_ID"

Or provide both dates:

curl --fail-with-body --get 'https://api.getkarta.ai/public/v1/billing/transactions' \
  -H "Authorization: Bearer $KARTA_API_KEY" \
  --data-urlencode 'start_date=2026-09-01' \
  --data-urlencode 'end_date=2026-09-07' \
  --data-urlencode 'limit=50'

If you provide both filters, request_id takes precedence over dates. Results include credit and debit entries only, sorted newest first. Amounts are positive; entry_type determines direction. Preserve transaction IDs as strings. Advance offset by the page limit until you reach pagination.total.

Pricing

GET /client returns account-specific pricing rules. A rule can include its feature, credit rate, call type, direction, rounding, interval, minimum duration, and billing pulse. An empty list does not define the default price. Confirm pricing for your account before production calling.