Account

Billing

Billing is secondary to the API reference, but it still matters for planning throughput, monthly credits, and subscription lifecycle behavior.

Account4 min

View as Markdown

Getting startedSee how auth and job requests fit into the paid API lane.OverviewReturn to the full API map.

Section

Billing Topics

Plans and access

API access is available on Starter, Pro, Growth, and Scale. Starter is API-only; Pro, Growth, and Scale add signed webhooks. Keys remain owned by the user who creates them.

Monthly credits

Credits do not roll over. Monthly credits reset each paid billing cycle, and DocuShell does not auto-charge overages.

Cancellation

Cancel-at-period-end keeps API access active until the paid term actually expires.

Invoices and receipts

DocuShell stores invoice and payment references without exposing provider-specific terminology in the public docs.

Refund policy

Unused paid purchases may be reviewed within 7 days. Completed jobs and expired unused credits are not automatically refunded.

Section

Operational Notes

Insufficient credits return 402 insufficient_credits from the public API lane with hard_limit: true, overages_available: false, the credits required, credits remaining, reset time, and an upgrade URL.
Rate limiting still applies even on paid plans.
Authentication failures, validation failures, rate-limit rejections, and requests rejected before queueing do not deduct credits.
If an internal DocuShell worker fails after credits are reserved, the refund path is designed to return those credits idempotently.
Standard Checkout access is opt-in and does not silently auto-renew; renew before period end to avoid API interruptions.
Billing support and subscription management live in the dashboard.