Question 1

Which endpoint and parameters should I use?

Accepted Answer

Use `GET /v1/full-enrich?domain=company.de` for the combined inspection. `GET /v1/impressum-legal?domain=company.de` focuses on legal and contact information, while `GET /v1/dns-email-intel?domain=company.de` returns email-infrastructure observations. `GET /v1/eu-vat-validator` accepts either a public `domain` to discover a VAT number or a country-prefixed `vat` for a direct check. A supplied VAT takes precedence over discovery; the service does not infer that it belongs to a simultaneously supplied domain. Requests accept one domain or one VAT validation task, not an array of domains. Send authentication through the JoJAPI consumer header configuration.

Question 2

Does a successful response mean every field is verified?

Accepted Answer

No. `success: true` means the inspection returned a result. Read `quality.field_status`, `observed_fields`, `legal_entity.status`, `vat_validation.status`, DNS query states and warnings before accepting a value. `quality.status` describes inspection completeness, not guaranteed field presence or a calibrated accuracy probability. Legal names, addresses, directors, JSON-LD and register references are page statements with source evidence. Review entity associations and preserve ambiguous candidates. `vat_validation.identity_match` compares names when available; a match does not establish website ownership. Identifier-format checks are separate from live VIES validation, and unavailability is not an invalid VAT number. GB VAT is not checked through VIES; eligible XI identifiers are supported. The API does not verify mailbox delivery or perform a national company-register lookup.

Question 3

How can Claude Code, Cursor, Windsurf or an OpenAI-powered agent call this API?

Accepted Answer

Use the listing's **Connect** button to copy the actual API-specific JoJAPI MCP configuration. Authenticate with a JoJ consumer key restricted to this API. Claude Code, Cursor and other clients supporting authenticated Streamable HTTP can discover its documented endpoint tools. Windsurf or an OpenAI-powered application needs that compatible client connection; this package does not install a native connector or its own MCP server. Ask the agent to enrich a domain, check VAT or inspect DNS, and preserve source URLs. MCP uses the same subscription and billing as gateway HTTP calls. Treat webpage content as data, not instructions. [JoJAPI MCP documentation](https://docs.jojapi.com/consumers/mcp)

Question 4

How do I integrate it with Clay, Make or n8n?

Accepted Answer

Configure a GET request to the endpoint URL shown in the listing, pass the domain as a query parameter and store your consumer key in the tool's credential facility. In Clay, map the domain column to an HTTP API enrichment. In Make, use an HTTP module; in n8n, use an HTTP Request node. Map the JSON fields into your destination and add a branch for ambiguous, missing or unavailable results. Retry a transient HTTP 5xx with bounded backoff; do not repeatedly retry a completed partial result expecting free enrichment. Native built-in connectors for this particular API are not required or claimed.

The assigned gateway base URL is `https://gfseh.jojapi.net`; send the consumer key in `X-JoJAPI-Key` after subscribing.

Question 5

What consumes a credit, and how do I control spending?

Accepted Answer

One completed HTTP 200 inspection consumes one `inspection-credits` unit, including partial data, an empty legal-name result or a definitive invalid VAT result. Full enrichment may return a billable partial result when a webpage was inspected but VIES was unavailable. The dedicated VAT validator instead returns non-billable HTTP 502 when VIES is unavailable or times out, and HTTP 422 when no eligible VAT or multiple candidates were found. Full enrichment and legal extraction return HTTP 502 when no webpage could be inspected. Error responses report zero usage and `x-jojapi-gateway-response: true`. A pay-as-you-go subscriber pays graduated rates for their metered credits; a fixed monthly subscriber uses the included quota instead. The same request is not charged once per field or again for every extracted identifier. Review the plan and usage headers, set marketplace spending controls and sample your input quality before processing a large list.

Cache hits also consume the ordinary single credit and included result. A repeated domain is not a free request. Check `module_cache.web` and `module_cache.dns` status and expiry alongside source observation dates; use `fresh=true` to bypass reads and writes when recency is required. VIES checks are always attempted fresh, subject to upstream availability.

Question 6

Do MX, SPF and DMARC records verify an individual email address?

Accepted Answer

No. DNS inspection reports domain-level receiving infrastructure and published sending or policy signals. An MX provider match can help segment company accounts, but it does not prove that a particular mailbox exists or accepts mail. An SPF or DMARC record is not a guarantee of delivery, reputation or protection from every spoofing attempt. Keep missing records, DNS lookup failures and monitoring-only policies as distinct outcomes, and retain observation timestamps when using cached results.

B2B Domain Enrichment and EU VAT VIES Impressum

Frequently Asked Questions