QR6 endpoints
QR Code Generator API with Logo
PNG/SVG QR codes for URLs, WiFi, vCards, email, and SMS, with branded colors and optional logo overlay.
New7 live API categories on RapidAPI
Ship faster with 28 production-ready APIs.
Developer utilities, AI content, email and domain validation, website and SEO checks, QR codes, and public social data — all returning clean, predictable JSON. Skip the scrapers, the proxy pools, and the weeks of glue code.
Keys, plans, and billing are handled by RapidAPI — no separate ApiMask account.
instagram.profile
HOST="instagram-api.p.rapidapi.com"
curl --request GET \
--url "https://$HOST/v1/instagram/profile?username=nasawebb" \
--header "X-RapidAPI-Key: $RAPIDAPI_KEY" \
--header "X-RapidAPI-Host: $HOST"Representative response
{
"success": true,
"data": {
"id": "549313808",
"username": "nasawebb",
"full_name": "NASA Webb Telescope",
"is_verified": true,
"followers_count": 3547801,
"following_count": 35,
"media_count": 1302,
"source": "apify",
"fetched_at": "2026-07-20T10:10:24.746979+00:00"
},
"error": null,
"meta": { "request_id": "req_example" }
}RapidAPIdistribution and billing
7live API categories
28documented endpoints
JSONconsistent response envelope
Documentation
Docs you can actually build from.
Most of the time lost integrating an API goes into working out what it really returns. Every ApiMask endpoint is documented with the call, the response, and every field it contains.
A real request and a real response on every page
Every endpoint page shows the exact call and the exact JSON it returns — not a schema you have to mentally render.
Copy-paste snippets in cURL, JavaScript, and Python
Correct hosts, correct headers, correct body. Paste it into a terminal and it works.
Every parameter and response field documented
Types, whether it's required, what it does, and what it can be null. No guessing from example payloads.
- Read the quickstart
POST /v1/dev/email/validateemail-validation
curl --request POST \
--url https://apimask-developer-utilities-api.p.rapidapi.com/v1/dev/email/validate \
--header "Content-Type: application/json" \
--header "X-RapidAPI-Key: $RAPIDAPI_KEY" \
--data '{"email":"[email protected]"}'200 OKapplication/json
{
"success": true,
"data": {
"is_valid": true,
"email": "[email protected]",
"domain": "example.com",
"is_disposable": false,
"has_mx_records": true,
"is_role_account": false,
"reason": null
},
"error": null,
"meta": {}
}Catalog
Browse by category.
Seven live categories today, with more on the public roadmap. Every live category links straight into its documentation.
Developer utilities
11Regex, stacktraces, JSON, Base64, hashing, IDs, URL parsing
AI content
1SEO meta tags, summaries, rewrites, descriptions, captions
Email & domain
4Validation, bulk lists, MX/DNS, deliverability
Website & security
4SSL, security headers, URL safety, CORS
QR codes
3URL, WiFi, vCard, branded logo QR codes
SEO
3Meta tags, robots.txt, sitemaps
Social & app intelligence
2Twitter/X and Instagram profile and content data
On the roadmap
OCR & PDF
SoonPDF-to-Markdown, table & field extraction, OCR cleanup
Resume & ATS
SoonATS scoring, keyword gaps, resume rewrite
App Store / ASO
SoonMetadata, keywords, release notes, review sentiment
Data enrichment
SoonCompany, email, and domain enrichment
Security & threat intel
SoonURL safety, breach checks, header hardening
AI agents & workflows
SoonTool endpoints and structured extraction for agents
Products
Three products with their own RapidAPI listing.
Each bundles a set of related endpoints behind a single subscription, with its own plans and quota.
AI8 endpoints
AI Content Generator API
Summaries, rewrites, SEO meta tags, blog outlines, product descriptions, social captions, headlines, and FAQs.
@5 endpoints
Bulk Email Verification API
Validate JSON batches and CSV uploads, flag disposable and role-account emails, and check MX, SPF, and DMARC readiness.
Built to integrate
Predictable in the ways that cost you time.
The expensive part of consuming an API isn't the first call — it's every inconsistency you discover afterwards.
One envelope
Every endpoint returns the same { success, data, error, meta } shape, so error handling is written once and reused everywhere.
Versioned paths
Endpoints are namespaced under /v1. Breaking changes ship as a new version, never as a silent change to an existing one.
Documented errors
A single error catalog covers every product, with the status codes and payloads to expect and what to do about each.
No stored payloads
Requests are processed and returned. Bodies are not retained after the response is sent.
Security
Fewer secrets to look after.
Because distribution runs through RapidAPI, most of the surface area you'd normally have to review simply isn't yours to manage.
Keys never touch ApiMask
RapidAPI issues, rotates, and revokes your key, and enforces your plan's quota. There is no second credential to manage or leak.
TLS on every call
All traffic to *.p.rapidapi.com is encrypted in transit. Plain HTTP is not served.
Request bodies aren't retained
Payloads are processed to build the response and then discarded — relevant if you're passing customer emails or page content.
Public data only
The social and website endpoints read publicly accessible data. Nothing requires you to hand over end-user credentials.
- How authentication works
Use cases
Pick the problem you're solving.
For developers
Stop rewriting the same utilities in every project. Regex, hashing, IDs, JSON, URL parsing, CORS, and stacktrace analysis behind one key.
For SaaS and growth teams
Keep junk out of the funnel. Validate emails at signup, clean CRM imports in bulk, and qualify domains before they reach analytics.
For SEO and agencies
Turn one-off technical checks into repeatable audits: SSL, security headers, robots.txt, sitemaps, and generated metadata.