Validate data before it breaks your app.
Stop bad emails, invalid phones, and toxic content with APIs that catch issues at the source.
Use cases
POST /v1/validation/email
Catch bad addresses before campaigns and CRM sync
Prevent invalid emails from entering your database. Cleaner lists mean better deliverability and less wasted spend.
Example
A SaaS signup flow calls email validation after blur. Disposable domains and typos are rejected before the welcome email is sentβsupport stops fixing βone letter wrongβ addresses.
GET /v1/validation/phone
Reach real numbers on SMS and OTP flows
Validate phone numbers for SMS campaigns. Reach real users and cut failed sends.
Example
An e-commerce brand validates E.164 and line type on the OTP step. Invalid or landline numbers never hit the SMS gateway, cutting OTP cost and failed-delivery tickets.
POST /v1/validation/profanity
Keep public feeds and forums civil at scale
Filter profanity in user-generated content. Keep communities safe without manual review on every post.
Example
A community app runs comment text through a profanity filter server-side. Obvious abuse is blocked; borderline posts queue for moderator review instead of going live.
POST /v1/validation/email
Faster corporate signup with fewer IT retries
Streamline onboarding with email checks at the edge. Fewer retries, fewer support tickets.
Example
Enterprise self-serve checks domain and MX before sending SSO invites. Dead hosts and typos fail fast so IT is not waiting on bounces that never surface in the UI.
GET /v1/validation/phone
Validate subscriber data before porting and tickets
Catch phone errors before they cause issues downstream. Support spends time on real problems.
Example
A carrier portal validates subscriber numbers when a customer files a porting request. Bad inputs return same-day instead of after a week of βnumber not foundβ churn.
POST /v1/validation/profanity
In-game chat moderation without huge client blocklists
Moderate text automatically for safer platforms. Scale trust and safety with your product.
Example
In-game chat is checked on send. High-risk strings are dropped or masked; repeat senders get a cooldown without shipping a huge blocklist in the client bundle.
Reliability at a glance
APIS you can trust.
99.99%
Platform uptime target
~500ms
Average API response time
10,000+
Peak validations per minute (tier-dependent)
How it works
Three short steps from picking a pattern to measuring impact in your own metrics.
Pick a pattern that sounds familiar
Choose a card that mirrors where you lose time today (bounces, SMS failures, or noisy UGC). Each outcome maps to endpoints you can try with a small change in your form or pipeline.
Wire it into your stack
Use the reference examples, add your API key, and call the HTTPS endpoints from your backend or edge. Most teams ship the first version the same week they read the docs.
Prove it with your own metrics
Compare before and after in dashboards you already trust: fewer failures, shorter queues, calmer support, or faster pages once bad inputs stop propagating.
Wire endpoints for this division
Use the cards above for scenarios; request shapes, parameters, examples, and errors are in the technical directory for this category.
Industries we serve
What customers say
"Fake signups were a real problem for us. Requiems validation APIs stopped bad data at the door without adding friction for real users."
"We rely on Requiems validation to keep our user database clean and their recognition services to deliver a tailored experience to every athlete."
Start validating data today.
Integrate in minutes. Catch issues before they cost you.