Skip to content

Credits

Live projects are paid with the account’s credits: one credit is one minute of audio, charged by the second for what we measure in the files (all tracks of a project), with a small per-project minimum. Every processing setting costs the same. Credits don’t expire.

  • A live project’s credits are taken when it’s validated (submitting needs credits:spend). Not enough credits: the project is rejected with insufficient_credits.
  • A project that fails for good, or is cancelled before processing, gets its credits back automatically.
  • Each run is charged: a project copied to process it again costs what a new project would. When a result is wrong because of us, we reprocess it for free: write to support@podsworth.com.
  • Test projects show their price in creditsSeconds and are never charged.

Buy credits as bundles, or as a monthly plan, on the account page (or podsworth.com/pricing).

A plan adds its hours every month, for a little less than the same bundle. They’re spent before any other credits. Unused plan hours roll over, at most one month’s worth: at each renewal anything above a month’s hours is dropped before the new month’s are added. Bundle hours are never touched. Change or cancel a plan in Billing details on the account page; changes start at the next renewal, and after a cancellation the hours you have stay usable.

GET /v1/subscription (account:read) shows the plan, or the last one the account had (null if none): its planId, seconds and amountCents per month, status, live (true while it’s the account’s plan), and currentPeriodEnd (when it renews, or ends if cancelAtPeriodEnd). Subscribing, changing and cancelling happen on the account page, for signed-in people only: a key or an assistant can read the plan but not change it.

status
activePaid up.
past_dueA renewal’s payment failed and the card is tried again. The new month’s hours wait for the payment; the hours already in stay usable.
canceledIt ended. The hours it added stay usable.

When a renewal can’t be charged, the account’s owners and billing members get one email for that renewal, with a link to pay it (with the same card or another) and when the card will be tried again. A subscription.payment_failed event (data.invoiceId) goes out on every failed charge: the renewal’s, each retry’s, and a first payment that fails in checkout (that one gets no email: the person is there). Once it’s paid, the month’s hours are added and subscription.renewed follows.

Auto top-up buys a bundle with the saved card whenever the balance drops below a threshold, at most a set number of times a month (3 by default, up to 20), so an integration never runs dry and a runaway one can’t drain a card.

PUT /v1/auto-top-up (billing:purchase)
{ "enabled": true, "thresholdSeconds": 7200, "bundleId": "5h", "monthlyCap": 3 }

thresholdSeconds is between 10 minutes and 100 hours (invalid_threshold), monthlyCap 1 to 20 (invalid_cap). Turning it on needs a bundle on sale (invalid_bundle, unknown_bundle) and a saved card, which the account gets from its first purchase through checkout on the account page (409 no_saved_card). The month runs on US Central time. People and API keys change auto top-up; a connected assistant can’t (403 not_for_apps), since its purchases have their own monthly cap.

If a charge is declined (or the bank wants 3-D Secure, which nobody is there to answer), auto top-up pauses, the account’s owners and billing members get an email, and a billing.topup_failed event goes out. Saving the settings again turns it back on. GET /v1/auto-top-up shows the settings, a pause and its reason, and this month’s purchases.

Teams that pay through a finance department can ask us (info@podsworth.com) to be invoiced. On an account set up for it, a person signed in as an owner or billing member can buy a bundle on a net-30 invoice from the account page: Stripe emails the invoice to the billing address, and the hours are added at once. Pay it within 30 days by bank transfer (ACH or wire, to the account number on the invoice), ACH debit or card.

  • Each account has a limit on what it may owe on invoices at once; an invoice that doesn’t fit is refused with 409 invoice_limit_reached (error.details has limitCents and owedCents).
  • While an invoice is past due, or one was written off unpaid, no new ones can be sent (409 invoice_overdue). Buying with a card still works.
  • An account that isn’t set up for invoices gets 403 invoice_billing_off.
  • The hours arrive as a purchase line in the ledger and a credits.added event when the invoice is sent. Paying it changes the purchase’s status, with no event.
  • If an invoice is cancelled, or written off unpaid, the hours it added that are still unspent come back out (an invoice_void line in the ledger).

GET /v1/credits/invoicing (billing:purchase) shows whether the account pays by invoice, its limit, what it owes and its open invoices with their due dates. In the purchase list and the ledger, an unpaid invoice’s purchase has the status invoiced and an invoiceDueAt; it becomes paid when the payment arrives. Asking for an invoice is for people on the account page: keys and connected apps buy with the card (below).

GET /v1/balance (account:read)
GET /v1/ledger (account:read)

GET /v1/balance answers totalSeconds and buckets (seconds left in each: plan, promo, purchased). Projects spend plan hours first, then promotional ones (the trial), then purchased ones. GET /v1/ledger lists every change, newest first, each with its kind, bucket and deltaSeconds (negative when credits go out):

kind
purchaseA bundle, an auto top-up or an invoice’s hours (purchase has what was paid).
plan_grantA plan’s month.
rollover_capPlan hours over one month’s, dropped at a renewal.
trialThe free trial.
admin_grant, admin_revokeOur team added or took back credits (note says why).
debitA project’s or an order’s charge.
refundA failed or cancelled project’s credits back.
keep_feeKeep’s fee.
purchase_refundA refunded purchase’s unspent hours taken back.
invoice_voidA cancelled or written-off invoice’s unspent hours taken back.

GET /v1/usage adds up what projects used, by day or by show: see Shows and usage.

With a live key that has billing:purchase, POST /v1/credits/buy buys a bundle with the account’s saved card (the card used for its last purchase on the account page):

{ "bundleId": "5h" }

status is paid when the credits are in (a credits.added event follows), or pending when the card’s bank wants 3-D Secure. A person has to complete that in a browser, so buy ahead of need when you automate it, and watch credits.low. A declined card is 402 card_declined with the bank’s reason; an account with no saved card yet is 409 no_saved_card. GET /v1/credits/purchases lists the account’s purchases, and GET /v1/credits/purchases/{id} one of them.