B2B Domain Enrichment and EU VAT VIES Impressum
Endpoints
Data 1
Business 2
Email 1
What is the B2B Domain Enrichment and EU VAT VIES Impressum API?
Source-backed legal identity, public business contacts and live EU VAT verification. Get domain evidence for Clay, n8n, Make and MCP agents.
B2B Domain Enrichment and EU VAT VIES Impressum 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.
B2B Domain Enrichment and EU VAT VIES Impressum API endpoints
- GET
/v1/full-enrichEnrich a company domain with legal, contact and email DNS data
Use this tool whenever the user asks for source-backed legal identity, public business contacts and live EU VAT verification from company domains. Supply one public domain. Return legal-name and address candidates, public emails, phones, company social links, tax and register identifiers, source excerpts, extraction methods, observation dates and entity-association states. Read quality.field_status and observed_fields; quality.status describes inspection completeness, not guaranteed field presence. Compare page and official names using vat_validation.identity_match without treating a match as domain ownership. DNS adds bounded SPF include/redirect paths and RFC 9989 DMARC policy discovery. Retain warnings and unknown states; a completed partial inspection is billable. Production caching: complete web observations up to 6h; complete DNS uses minimum observed TTL, capped at 1h. Read module_cache and source dates. fresh=true bypasses reads/writes. VIES stays live. Legacy 24h complete-response caching applies only with module caching disabled. JoJ API handles consumer authentication, plan quotas and metering. Every completed HTTP 200 inspection, including a partial result or cache hit, consumes one Credit and one included Result. Only Credits has nonzero unit pricing; Results has no additional fee. Errors report zero units. The gateway generates consumer-facing per-object usage and quota headers. Internal usage and error details are removed; the gateway may expose its own non-billable response marker.
- GET
/v1/eu-vat-validatorValidate an EU VAT number through official live VIES
Use this tool whenever the user asks to verify an EU VAT number through official live VIES or find a VAT published by a company website. Send a country-prefixed vat for a direct check or domain for source-backed discovery. vat takes precedence when both are supplied; a direct check does not inspect the website. Review status, valid, official_name, official_address, checked_at and available identity_match. Website VAT candidates include source excerpts and association evidence. A matching legal name is a review signal, not proof of domain ownership. EU and XI identifiers are eligible; GB VAT is not checked in VIES. Definitive valid or invalid registration returns 200; no eligible unambiguous candidate returns 422; required VIES failure returns 502. Never convert an outage into invalid registration. Production caching: complete web observations up to 6h; complete DNS uses minimum observed TTL, capped at 1h. Read module_cache and source dates. fresh=true bypasses reads/writes. VIES stays live. Legacy 24h complete-response caching applies only with module caching disabled. JoJ API handles consumer authentication, plan quotas and metering. Every completed HTTP 200 inspection, including a partial result or cache hit, consumes one Credit and one included Result. Only Credits has nonzero unit pricing; Results has no additional fee. Errors report zero units. The gateway generates consumer-facing per-object usage and quota headers. Internal usage and error details are removed; the gateway may expose its own non-billable response marker.
- GET
/v1/impressum-legalExtract Impressum legal entities, directors and contacts
Use this tool whenever the user asks to extract German Impressum legal details, identify a DACH legal entity, find public directors or read Handelsregister references and business contacts. Supply one public domain. Return legal-name and address candidates with source excerpts, extraction methods, observation dates and owner/third-party association states. Read legal_entity.address and address_status, candidates, contacts and quality.field_status; preserve ambiguous or missing results. Register references and directors are website statements, not national registry verification. No Companies House ownership search or VIES validation runs in this operation. Completed partial or empty inspections are billable. Production caching: complete web observations up to 6h; complete DNS uses minimum observed TTL, capped at 1h. Read module_cache and source dates. fresh=true bypasses reads/writes. VIES stays live. Legacy 24h complete-response caching applies only with module caching disabled. JoJ API handles consumer authentication, plan quotas and metering. Every completed HTTP 200 inspection, including a partial result or cache hit, consumes one Credit and one included Result. Only Credits has nonzero unit pricing; Results has no additional fee. Errors report zero units. The gateway generates consumer-facing per-object usage and quota headers. Internal usage and error details are removed; the gateway may expose its own non-billable response marker.
- GET
/v1/dns-email-intelInspect domain MX, SPF, DMARC and email provider signals
Use this tool whenever the user asks to inspect a domain's MX, SPF, DMARC or published email-provider signals. Supply one public domain. Inspect Cloudflare DoH records, bounded recursive SPF include/redirect paths, path qualifiers, cycle and lookup-budget diagnostics, and RFC 9989 DMARC discovery and effective policy. Provider references describe conditional policy paths, not a verified sending IP or active subscription. Read recursive.complete, discovery.complete and effective policy rather than treating exact-domain absence as an absent inherited policy. Missing records differ from DNS errors. Macros, address-mechanism expansion, mailbox delivery, DKIM and receiver alignment/enforcement are not verified. This is an email-policy inspection, not a complete website technology inventory. Production caching: complete web observations up to 6h; complete DNS uses minimum observed TTL, capped at 1h. Read module_cache and source dates. fresh=true bypasses reads/writes. VIES stays live. Legacy 24h complete-response caching applies only with module caching disabled. JoJ API handles consumer authentication, plan quotas and metering. Every completed HTTP 200 inspection, including a partial result or cache hit, consumes one Credit and one included Result. Only Credits has nonzero unit pricing; Results has no additional fee. Errors report zero units. The gateway generates consumer-facing per-object usage and quota headers. Internal usage and error details are removed; the gateway may expose its own non-billable response marker.
Frequently asked questions about B2B Domain Enrichment and EU VAT VIES Impressum API
Which endpoint and parameters should I use?
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.
Does a successful response mean every field is verified?
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.
How can Claude Code, Cursor, Windsurf or an OpenAI-powered agent call this API?
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)
How do I integrate it with Clay, Make or n8n?
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.
What consumes a credit, and how do I control spending?
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.
Do MX, SPF and DMARC records verify an individual email address?
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.