Credits

Conversions made through the API use the same credits as the website: one balance per organization, shared by the dashboard and every API key. Test-mode keys never use credits (see Test mode).

See Pricing for current plans, credit packs, the free allowance and what a credit costs.

What is charged

Credits are measured in reference conversion-minutes: 1 credit = 1 reference conversion-minute. A completed job costs max(1, ceil(billable_ms × speed_factor / 60000) × weight) credits. The speed factor is 1 by default. The weight depends on the conversion: video transcodes and iWork are 2, PDF to Office is 4, and other conversions are 1. GET /operations shows the estimate for each pair.

Failed conversions are not charged. A job can be cancelled while it is waiting or queued, and its reserved credits are released. Jobs that are already processing cannot be cancelled yet, see Jobs.

In the API

• GET /operations lists every supported conversion with a credits_estimated value.
• A job reports credits_estimated (the credits held for it, which it is never charged above) when it is created and credits_used (the final charge) once it has finished. A job that fails or is cancelled before processing uses no credits.
• GET /me returns your organization's current credits.balance.
• If your balance cannot cover a job, POST /jobs answers 402 insufficient_credits with credits_required, credits_available and pricing_url (a link to Pricing) in error.details, and nothing is created.