Endpoints
Ungrouped Endpoints 3
What is the Email and SEO Metadata Extraction API?
Fast API to validate email syntax, detect disposable domains, and extract SEO Open Graph tags.
Email and SEO Metadata Extraction API is available on the JoJ API marketplace. Subscribe with a single JoJ API key, call it through one gateway, and pay from one wallet — no separate account or contract with the provider.
Email and SEO Metadata Extraction API endpoints
- GET
/validate-emailValidate Email
Checks email syntax and flags known disposable-email domains. It does not verify mailbox existence.
- GET
/extract-seoExtract SEO Metadata
Fetches a public HTML page and extracts its title, meta description, og:title, and og:image. Eligible successful results may be cached internally for up to 5 minutes (shorter when required by the target cache policy). Set optional fresh=true to bypass cache reads and writes; false or omission allows caching. Only exact true/false are accepted; invalid or duplicate fresh parameters return HTTP 400. Response headers X-SEO-Cache (HIT, MISS, BYPASS) and X-SEO-Cache-Age (whole seconds; 0 for MISS/BYPASS) report cache use. Reading can stop once all four non-empty fields are complete. Missing fields remain null; JavaScript is not executed. Authentication and marketplace request quotas still apply to cache hits.
- GET
/healthHealth Check
Returns the current API status and server timestamp.
Frequently asked questions about Email and SEO Metadata Extraction API
Does email validation verify that a mailbox exists?
No. GET /[email protected] checks address syntax and matches the domain against a built-in list of known disposable email services. It does not send email, contact an SMTP server, check MX records, or guarantee deliverability. A syntactically invalid address is returned as a successful HTTP 200 result with validSyntax=false. An omitted or empty email parameter returns HTTP 400.
Which SEO fields are extracted and what are the limits?
GET /extract-seo?url=https%3A%2F%2Fexample.com reads the HTML returned by a public HTTP or HTTPS page and returns its title, meta description, og:title and og:image. Missing fields are null; relative image URLs are resolved against the final page URL. JavaScript is not executed. The request has an 8-second timeout, follows at most 3 redirects and scans at most 256 KiB of HTML, so tags beyond that limit may be absent. URLs containing credentials, custom ports, IP literals, local hostnames or the service itself are rejected.
Are SEO results cached, and how do I request fresh metadata?
Eligible successful SEO results may be reused for up to 5 minutes; target cache policies, response age, redirects and cache availability can shorten or prevent reuse. Set fresh=true to bypass both cache reads and writes. It does not invalidate or refresh an existing cache entry. Omit fresh or use fresh=false to allow caching. Only exact true and false are accepted; invalid values or duplicate fresh parameters return HTTP 400 (INVALID_PARAMETER). X-SEO-Cache reports HIT, MISS or BYPASS; X-SEO-Cache-Age is the whole-second age for HIT and 0 otherwise. Errors, no-store/private/no-cache responses, responses setting cookies or declaring Vary: *, and recognized sensitive URL parameters are not cached. Do not submit secrets or private URLs. Client responses remain Cache-Control: no-store. Authentication and marketplace request quotas still apply to cache hits. Reading stops early when the complete non-empty title and all three supported meta values are available; otherwise the normal 256 KiB and 8-second limits apply. Performance depends on the target site, network and cache availability; no fixed speed-up is guaranteed.