The 2025 Proofy Platform Update: Release Notes and Feature Highlights

In mid-2025, Proofy shipped its largest platform update since the service launched. The headline numbers are speed and accuracy, but the real story is everything underneath — a rebuilt admin panel, a new API surface, a JS widget for signup forms, expanded bulk-file limits, and a payment system that finally handles the cases real customers actually run into. This page is the long version of the release notes: what changed, what it means for your day-to-day workflow, how to migrate from the old account, and how to get the most out of the new features.

What Shipped in the 2025 Release

The update touched almost every part of the platform. Here is the full feature list with enough context to know whether each one matters for your use case:

• Rebuilt admin panel. The dashboard was redesigned around the workflows users actually run — upload a list, watch progress, download results — with fewer clicks between steps and clearer status indicators on long-running jobs.
• Faster verification with tighter accuracy. The way the engine talks to mailbox providers was refactored to handle larger lists with fewer false positives. The same address now returns a cleaner verdict, and a list of ten thousand contacts finishes noticeably faster than it did under the previous engine.
• Bulk uploads up to 65 MB. The previous file-size cap forced large lists into multiple uploads. The new bulk verification handles files up to 65 MB in a single pass — enough for most six-figure subscriber lists without splitting the export.
• New API surface. The validation API now ships in four shapes: a real-time single-address endpoint, a batch endpoint for queued processing, a bulk-file endpoint that matches the dashboard upload, and webhooks for asynchronous result delivery. Pick the shape that matches your latency and volume profile.
• Multiple API keys per account. Teams running several products or environments can issue separate keys per project, rotate them independently, and track usage per key — instead of sharing a single global key across staging, production, and one-off scripts.
• JS widget for signup forms. A drop-in JavaScript snippet runs verification inline on signup forms — bad addresses get flagged before the contact is submitted, so they never enter your email tool in the first place.
• Cleaner API documentation. The docs were rewritten around concrete examples for each endpoint, with copy-paste request bodies and explanations of every status code the API can return.
• Per-key usage metrics. Each API key now reports its own usage in the dashboard, making it possible to attribute verification spend to specific products or campaigns without guesswork.
• New payment flow. The checkout supports bank cards, Link, and additional payment methods that the previous flow did not. Payment history and invoices are now accessible directly from the dashboard.

Why This Update Actually Matters

Speed and accuracy were always the explicit goals — but the deeper change is that the platform now handles real-world edge cases gracefully. Lists with mixed catch-all domains return cleaner confidence flags. Bulk jobs that used to time out finish reliably. The API behaves the same way under load as it does for a single test request.

For teams running outreach at scale, that translates into fewer surprises on the day a campaign goes out — and a steadier sender reputation across every mailbox provider that scores you. The cumulative effect across a quarter of campaigns is usually larger than any single feature suggests.

Migrating From the Old Account

The 2025 platform runs on a new infrastructure, so existing users go through a one-time migration:

• Register a new account. The legacy account credentials do not carry over automatically. Sign up at proofy.io and click "Get Started" to provision the new dashboard.
• Transfer your remaining credits. Contact the support team after registering and ask for a credit transfer from the old account. The team will move the balance manually, usually within one business day.
• Regenerate API keys. Old API keys do not work against the new endpoints. Generate fresh keys in the dashboard and update them in any scripts, Zaps, or backend services that previously called Proofy. The new keys support per-project scoping if you want to split them now.
• Confirm webhooks if you used them. The webhook signing and payload format changed in the rebuild. If you had webhook handlers on the old platform, point them at the new endpoint and adjust the signature verification.

As a returning user, you also get loyalty discounts on the first purchase after migration — the support team applies these on request.

Making the Most of the New Features

• Use the JS widget on every public signup form. Inline verification at the form layer is the cheapest place to catch bad addresses. Pair it with the batch API for cleaning lists that arrived before the widget went live.
• Split API keys by environment. Production, staging, and one-off scripts should each have their own key. Per-key usage metrics make it easy to see which environment is consuming credits unexpectedly.
• Send large historical lists through bulk, not batch. The bulk endpoint and bulk dashboard upload share the same underlying engine, which is optimized for files. The batch API is built for queued real-time work, not for ten-million-row CSVs.
• Connect the platform to your existing stack via Zapier. Proofy is a native Zapier app, which is how it plugs into Mailchimp, HubSpot, and most modern CRMs. The new API surface makes this faster than under the previous platform.
• Schedule a quarterly bulk audit. Even with the JS widget catching most issues at signup, lists drift — contacts change jobs, addresses go stale. A quarterly full audit catches what real-time checks cannot.

Frequently Asked Questions

What changed in the 2025 release?

The 2025 release delivered faster processing, tighter accuracy on edge-case domains, a rebuilt dashboard, an expanded API surface with four endpoint types, multiple API keys per account, a JS widget for signup forms, higher bulk-file limits, cleaner documentation, per-key usage metrics, and a new payment system. Each piece is detailed above; the cumulative effect is a platform that handles real-world list-cleaning workflows with fewer rough edges.

Do my old verification credits transfer to the new account?

Yes, but the move is manual. After registering a new account, contact support and ask for the transfer. The remaining balance gets moved from the legacy account to the new one, typically within a business day. You only need to do this once.

Will my old API keys still work?

No. The 2025 API runs on a new infrastructure and accepts only newly-issued keys. Generate fresh keys in the dashboard and update every script, Zap, or backend integration that previously called Proofy. While you are at it, consider splitting one global key into per-project keys to make usage tracking easier later.

How does this update affect deliverability?

By catching unreachable and risky addresses more precisely before they enter your campaigns, the cleaned list reaches more active inboxes and triggers fewer bounce-based reputation hits. Mailbox providers reward consistent senders with better placement, and the update's accuracy improvements feed directly into that loop.

Where do I report issues with the new platform?

The fastest path is the support chat from your new dashboard — it routes to the same team that handles credit transfers and onboarding questions. Bug reports with reproducible steps usually get a response the same day; product requests go onto the public roadmap for prioritization.