What changed on provable.io and the API, newest first.
v1.20.0 (2026-11-18)
Draw badge: every outcome page offers an embeddable /o/<id>/badge.svg that shows the draw's status and links to its proof.
New use-case page for prize competition draws.
One getting-started email to accounts whose keys have made no API call a day after sign-up; notification opt-out applies.
Privacy policy updated for the getting-started email.
v1.19.0 (2026-11-17)
Account security log: sign-ups, sign-ins, email, password and two-factor changes, webhook changes and account deletion are recorded with time, IP address and browser, and kept 180 days.
Admin account detail lists the account's events; the IP filter also matches past events.
Privacy policy updated for the security log.
v1.18.1 (2026-11-17)
Search: the dice roller, provably fair calculator and /verify have titles and descriptions that match what people search for (verify a dice roll, server seed calculator, provably fair verifier).
The dice roller and /verify point casino-bet checks to the calculator; the calculator FAQ explains why a provably fair predictor cannot work.
v1.18.0 (2026-11-16)
Admin: account detail shows email confirmation, two-factor and admin status, sign-up source, live sessions and webhook delivery attempts.
Admin: account list filters for email state, failing webhooks and session IP; sign-up email domains in the funnel.
Admin: open tickets and failing webhooks lead the page; support opens on open tickets and links each ticket to its account.
Admin: the action log hides routine page views by default, shows device and session, and lists admins with their last sign-in.
Admin: sign-ins expire after 12 hours and send a sign-in notice by email.
Admin: the page renders once in the browser instead of twice, and the draws count uses an index.
Tightened request checks on signed-in changes.
v1.17.2 (2026-11-16)
New accounts and email changes can't use provable.io or redpkt.com addresses.
App logs now survive deploys.
v1.17.1 (2026-11-16)
Changing your email now takes effect only when you open the link sent to the new address. The old address gets a notice, and a password reset cancels a pending change.
Webhook test sends are limited to 20 an hour.
v1.17.0 (2026-11-11)
Admin overview: a sign-up funnel card shows the sites and first pages behind new accounts, and how many anonymous calls the limits turned away (hits and distinct callers); the Draws card splits keyed, anonymous and test draws.
A new account records where its sign-up visit started: the first page and the site that linked to it. It is kept with the account and deleted with it.
Privacy policy: monthly API usage totals are kept while your account exists and deleted with it (it said 24 months, which nothing enforced); it now names Cloudflare Web Analytics (cookieless page-view totals) and the sign-up source. The cookie notice and About page no longer say there is no analytics.
v1.16.0 (2026-11-10)
Docs: the Node and Python quickstarts and the transparency-log audit script now fail on a mismatch instead of printing ✅; the TypeScript SDK, commit-reveal, streaming, batch, NFT-mint and card-shuffler samples run as printed against the real API and SDK.
Docs and llms.txt updated for v1.15.0: batch and streaming samples send an API key (PROVABLE_API_KEY everywhere), the core library and SDKs are described as MIT-licensed open source, and the hosted API is no longer called open source.
Every guide, comparison, use-case and tool page ends with a free-account card (an API key, 10,000 draws a day, plus batch and streaming); "Sign up free" stays in the top nav on phones and the footer links to sign-up.
Hitting the anonymous limit in the docs runner, the home demo, a tool or Get started now explains the limit and links to a free account, instead of raw JSON or a lost-result warning.
After you create an API key, the dashboard shows a ready-to-run first call with that key.
The /docs index lists all 23 guides; back links on compare and use-case pages go to their section; tool pages link to the other tools.
Tools keep keyboard focus on the button you pressed, announce the result to screen readers, and "Share this result" copies the proof-page link.
Sign-up, sign-in and verification show a plain message when the server or network fails, and announce errors against the right field.
Added a "Skip to content" link; each page's heading now sits inside the main landmark; the dashboard Restrictions dialog is fully keyboard-reachable.
Phones: long inline code wraps instead of widening the page, the cookie notice no longer covers buttons, the footer is about a third shorter, and API reference parameter tables stack.
Pages load lighter: icon fonts are cut from 244 KB to 13 KB and logos are served at display size; /brand downloads keep the full-resolution files.
Article structured data includes headline and image.
v1.15.0 (2026-11-10)
The home page's latest-draws feed is real time: each public draw appears as it happens, pushed over server-sent events from /o/stream, instead of every 10 seconds.
Each row also shows the draw's client seed and nonce; /o.json returns them too.
If the live stream is unavailable, the page falls back to refreshing every 10 seconds.
Breaking: calls without an API key are capped at 10 draws a minute and 100 a day per IP (code anonymous_limit, with a signupUrl). Verification and lookups stay open at 120 requests a minute, and keyed calls are unchanged.
Breaking: /api/batch and /api/stream need an API key; anonymous calls get 401 with code account_required.
The home demo and the tools link to sign-up when a visitor reaches the anonymous limit; the docs, terms and llms-full.txt state the new limits.
v1.14.0 (2026-11-09)
The home page shows the latest draws on the API, each linked to its proof page, and refreshes them every 10 seconds while the tab is open. It replaces the static curl example in "A proof page for every draw".
/o.json returns those draws as JSON; the /o wall now reads from the same 5-second cache.
v1.13.0 (2026-11-07)
Breaking: new accounts confirm their email before they can sign in, and sign-up no longer creates a test key; create the first key on the dashboard.
Admin tools now require two-factor sign-in on the admin's account.
New free tool: client seed generator at /tools/client-seed-generator, made in the browser and never sent to the server.
New page: sweepstakes casino API at /use-cases/sweepstakes-casino-api.
The SDK copies under sdk/ and their release workflows are removed; the SDKs live in provableio/provable-core.
Fixed the SDK source links on /api-docs and the TypeScript guide, and added the Python one.
npm audit reports no vulnerabilities in any dependency, development ones included.
v1.12.3 (2026-11-06)
Search: every page title now ends in "Provable.io", and the longer titles are shortened so search results show the whole thing.
v1.12.2 (2026-11-06)
Search: free tool headings now say what sets them apart (for example "Provably Fair Dice Roller").
Search: five guides are retitled for the problems developers search for: a verifiable Math.random() alternative, a Fisher-Yates card shuffle, weighted random selection, deterministic A/B bucketing and the commit-reveal scheme.
Search: clearer titles for the lottery API, the deck of cards API and the free tools page.
v1.12.1 (2026-11-06)
Search: the provably fair checker is linked from every page, and it and the outcome verifier have clearer titles.
API reference: the Python SDK install command now works (pip install from the GitHub repository).
Search: sign-in and sign-up pages stay out of search results.
v1.12.0 (2026-11-05)
Accounts: two-factor sign-in. Turn it on under Settings with any authenticator app; you get 10 one-time recovery codes for a lost phone.
Accounts: turning on two-factor sign-in signs out your other sessions.
Admin: an Activity tab records every admin page view, API call and sign-in, with time, status and IP.
Privacy policy: lists the two-factor data we store and how it is protected.
v1.11.1 (2026-11-05)
Accounts: adding a webhook also needs a confirmed email address, like creating a live key.
Fixed a concurrency issue when an older hash chain made its first draw.
Admin: long account emails no longer push the overview off the side of a phone or out of the Top accounts card.
v1.11.0 (2026-11-05)
Accounts: new accounts confirm their email address with a link we send at sign-up. Until then they get test keys (pk_test_); live keys need a confirmed address. Existing accounts count as confirmed.
Accounts: changing your email signs out your other sessions and asks you to confirm the new address. Resetting your password also confirms it.
Breaking: API input limits. clientSeed is at most 256 characters; shuffle and pick items at most 256 characters each and 32 KB in total; dice modifiers at most 1,000,000 either way; gaussian mean and stddev at most 1e12.
API: /api/verifyServerHash requires serverHash to be a string.
API: outcome permalinks always point at https://provable.io.
Usage export (CSV) prefixes cells that spreadsheets would read as formulas.
Notification settings: saving now returns the saved value.
Webhooks: two more reserved IPv6 ranges are refused as destinations; the docs show the real User-Agent (Provable-Webhook/2.0).
Admin: the overview no longer scrolls sideways on phones.
New /.well-known/security.txt saying where to report security issues.
Security hardening: caching headers, sign-in rate limits, IP allowlist matching, and nodemailer 10.
v1.10.1 (2026-11-05)
Security: hash-chain cursor updates are now atomic, so a concurrent rotation always takes effect.
Webhook attempts now have a hard 5-second limit for the whole request, and a response body over 64 KiB counts as a failed delivery.
Batch requests cap the total work of Poisson draws at 100,000 random floats per batch.
Inbound support email with oversized headers is refused before parsing (the message still reaches a human).
API reference: on phones and tablets, a sticky "Jump to" bar shows the section you're in and opens the full endpoint list. Before, the list sat at the top of the page and was gone once you scrolled past it.
API reference: new "Endpoints at a glance" table listing every endpoint with a one-line description of what it does.
API reference: each endpoint now shows its example request and response first. The "Try it" form sits below them, collapsed until you open it.
API reference: long cURL examples wrap instead of running off the edge of the box.
API reference: sidebar topics use the normal text font; endpoint paths stay in code font.
v1.9.0 (2026-10-20)
Terms of Service: a product that other people use and that calls the API must show a visible link to provable.io, ideally a "Verify" link next to each result that opens its verification page. A rel="nofollow" or rel="sponsored" link is fine, internal tools are exempt, and products already live have until November 19, 2026. See /terms, section 5.
/brand has copy-paste snippets for the verification link and the footer link.
v1.8.0 (2026-10-20)
This changelog. The footer shows the current version and links here.
v1.7.0 (2026-10-17)
Sealed commits, for apps that compute outcomes themselves, like real-time games: POST /api/commit with sealed: true and a label (live key) returns the seed to your key only, one commit per key and label, ever.
GET /api/commits?label= lists every sealed commit for a label publicly; each seed becomes public once revealed, or after 7 days.
v1.6.0 (2026-10-08)
New /brand page: how to name, show and link to Provable.io, with logo files and a brand guidelines PDF.
v1.5.0 (2026-10-05)
New free tool: the provably fair calculator at /tools/provably-fair-calculator.
The sweepstakes, lottery, raffle and giveaway examples reveal the committed seed, and state how long a commitment lasts correctly.
v1.4.0 (2026-10-04)
Support tickets work over email: notifications carry the full message, each ticket keeps one thread, and you can reply straight from your inbox.
v1.3.0 (2026-10-03)
Each day's transparency-log root is stored with its exact leaf list and never rebuilt, so inclusion proofs keep matching the published root. /transparency lists the 33 earlier days that can't be proven.
Inclusion proofs work for client seeds that contain :.
The verifier keeps revealed seeds and checks an outcome by replaying it; the permalink recipe includes the cursor.
Outcome permalinks show pick, bytes and dice values, and long hashes wrap on phones.
v1.2.1 (2026-10-02)
The lottery guide draws without replacement: it shuffles the 49 balls with /api/shuffle and takes the first 6. Six separate /api/ints draws repeat a number about 27% of the time.
v1.2.0 (2026-09-29)
Forgot your password? Reset it from an email link; the reset signs you out everywhere.
New homepage: a live API console, a ledger of recent draws you can replay in your browser, and a bias slider.
The API reference has Try it forms that pass a draw straight into its verification, and a filter for the endpoint list.
The public API accepts browser requests from any origin, so the TypeScript SDK runs in a web page. /api responses are never cached.
Webhooks retry for about 15 minutes (6 attempts), and every event carries an eventId.
Breaking: webhook signatures include the send time (X-Provable-Signature: t=<unix>,sha256=<hex>, an HMAC of <t>.<body>), so a captured delivery can't be replayed. Update your check as shown in /docs/webhooks.
All 12 use-case pages show a real draw with its proof steps and replay it in your browser.
Reorganized dashboard tabs, and a cleaner look across the site: type, corners, navigation and footer.
v1.1.0 (2026-09-28)
Breaking: ints, dice, shuffle and pick are now unbiased (provable-core 3.0.0), so the same seeds can give a different result than before. Ranges are capped at 2^32, and every outcome records the nonce that was actually hashed.
Security fixes from an audit of sign-in, sessions, account deletion, webhooks and API input handling.
Signed-in visitors can use the docs' Run buttons and Get started's Create commitment again; both failed with 403.
Get started is easier to read, and the menu icons show again.
v1.0.0 (2026-09-26)
Provable.io moved to its own servers behind Cloudflare. Versions are numbered from this release.
An API call with an unknown or revoked key gets 401 invalid_api_key instead of a 200 drawn as anonymous.