Usage is billed on one number: how many new countdown timers you create each month. Reading a timer, updating it, controlling it, and receiving webhooks are all included, and no plan has a monthly cap on API requests. Start on the free Sandbox, then move to a paid plan when you need to publish and serve production traffic.
A full-fidelity test environment for building and evaluating the integration.
Free
included with any account
For production applications and automated workflows on a single product.
$9
per month
For higher volume, more integrations, and more services calling the API.
$49
per month
For volumes above Growth, or limits that need to be set individually.
Talk to us
tailored to your volume
| Feature | Sandbox | Starter | Growth | Custom |
|---|---|---|---|---|
| Monthly price | Free | $9 | $49 | Custom |
| New timers per month | 100 | 1,000 | 10,000 | Custom |
| Monthly API request cap | None | None | None | None |
| Requests per minute | 30 | 300 | 300 | Custom |
| API keys | 1 | 3 | 10 | Custom |
| Webhook destinations | 1 | 5 | 25 | Custom |
| Webhook rules per timer | Unlimited | Unlimited | Unlimited | Unlimited |
| Webhook deliveries per month | 100 | Unlimited | Unlimited | Custom |
| Fixed, duration, recurring, personalized | Included | Included | Included | Included |
| Publish hosted pages and embeds | Not included | Included | Included | Included |
| Email countdown images | Not included | Included | Included | Included |
| Webhook retry and replay | Included | Included | Included | Included |
One rule: creating a timer costs one, and nothing else costs anything. A countdown you created in January and still read a million times in March never counts again.
POST /timersCounts oncePOST /timers/{id}/duplicateCounts once — a duplicate is a new timerGET anythingDoes not countPATCH /timers/{id}Does not countPOST /timers/{id}/actionsDoes not countArchive, restore, publish, deleteDoes not countStarter and Growth are billed monthly through Gumroad. There is no annual plan today.
Change plans from the billing page in your developer dashboard whenever your volume changes.
Cancelling stops the next renewal. Your plan stays active until the end of the period you paid for.
Reaching the timer limit returns an error rather than an invoice. Nothing is billed beyond your plan price.
Only creating a new timer. POST /v1/timers counts once, and POST /v1/timers/{timer_id}/duplicate counts once because a duplicate is a new timer. Countdowns and duration timers share the same monthly allowance.
No. Reading a timer, its status, its activity, or its metrics never counts toward your monthly timer allowance, and no plan has a monthly cap on API requests.
Only by a per-minute rate limit that protects the service: 300 requests per minute in Production and 30 per minute in Sandbox. Exceeding it returns HTTP 429 with a Retry-After header, and the limit resets at the top of the next minute.
Creating a new timer returns HTTP 429 with the error code quota_exhausted, a Retry-After header, and details naming the metric, the limit, and when the cycle resets. Everything else keeps working: your existing timers keep running, your webhooks keep firing, and you can still read, update, and control every timer you already created. Upgrade or wait for the cycle to reset.
Yes. You can move between Starter and Growth at any time from the billing page in your developer dashboard. The new limits apply to your billing cycle once the change is confirmed.
There is no time-limited trial of a paid plan. Instead, every CountdownShare account includes a free Sandbox environment that does not expire: 100 test timers a month, a Sandbox API key, and one webhook destination, so you can build and verify the whole integration before paying. Sandbox timers cannot be published.
Yes, on every plan including Sandbox. Webhook rules are unlimited; plans differ in how many reusable webhook destinations you can register — 1 on Sandbox, 5 on Starter, 25 on Growth. Paid plans include unlimited webhook deliveries.
Yes. Cancelling stops the next renewal and your plan stays active until the end of the period you already paid for. Subscriptions are handled through Gumroad, and you can manage or cancel yours from the billing page in your developer dashboard.
No. The timer allowance is per billing cycle and resets when the cycle does. Unused timers do not carry into the next month.
Not at the moment. Starter and Growth are billed monthly. If you need annual billing or invoicing, contact us about a Custom plan.
Custom plans set your timer volume, rate limit, key and destination counts, and retention windows individually. Tell us the shape of your usage.