Skip to main content
Your organization holds a prepaid credit balance in cents. Processing is metered at a per-hour rate (see GET /v1/balance → rate_cents_per_hour, currently $5.00/hour), billed per second of video actually processed and rounded up to the cent.

​
How a job is charged

1

Hold at submit

POST /v1/sessions places a hold for the estimated cost (from duration_seconds if you sent it, otherwise from the file size, otherwise 2 hours). The response headers tell you what was held and what remains:
If the balance can’t cover the estimate you get 402:
2

Settle on success

When the job finishes, the hold is settled for the measured length — the estimate is replaced by the real duration, and credits are drawn from the oldest-expiring balance first. cost_cents on the session is the final figure.
3

Void on failure

If processing fails for any reason — including a video over the size/resolution limit or a job that never reports back — the hold is voided and nothing is charged.

​
Balance

  • available_cents = credit_cents − held_cents. This is what a new submit is checked against.
  • Credits expire one year after purchase; soonest_expiry is the next date the balance shrinks on its own.

​
Usage

GET /v1/usage lists one usage event per billable job:
status is held, settled or voided. Filter by status, api_key, and created[gte] / created[lte].

​
Topping up

Credits are added by Hooper — on invoice, or through a card top-up link your Hooper contact can send you. Organizations with a saved card can also enable auto-recharge: when a settle drops the balance below your threshold, Hooper charges a fixed amount off-session (at most once an hour). Contact Hooper to set it up.