API Enrichment

German B2B data.
One API key away.

Create a key and enrich from your own stack: verified work emails and company profiles, returned as JSON. No sales call between you and the data.

Deep German coverage No commitment Pay per result

5 min

To your first call

sign up, create a key, send a request

100%

Self-serve

no sales call, no contract

0

Credits on a miss

you only pay for results

Simple to integrate

One POST per lookup, JSON back

POST /v1/email/finder
Response 200 OK

...

{
  "found": true,
  "credits_consumed": 1,
  "message": "Found [email protected].",
  "email": "[email protected]",
  "deliverability": "valid"
}
{
  "found": true,
  "credits_consumed": 2,
  "message": "Found Muster Maschinenbau GmbH.",
  "legal_name": "Muster Maschinenbau GmbH",
  "legal_form": "GmbH",
  "domain": "example.com",
  "register": {
    "country": "DE",
    "type": "HRB",
    "number": "HRB 12345",
    "authority": "Amtsgericht München",
    "status": "active",
    "incorporated_at": "1998-05-12",
    "purpose": "Herstellung und Vertrieb von Maschinen und Anlagen.",
    "capital": {
      "amount": 100000.0,
      "currency": "EUR"
    },
    "representatives": [
      {
        "name": "Max Mustermann",
        "role": "Geschäftsführer"
      }
    ]
  },
  "address": {
    "street": "Musterstraße 1",
    "postal_code": "80331",
    "city": "München",
    "country": "DE"
  },
  "imprint": {
    "email": "[email protected]",
    "phone": "+49891234567",
    "url": "https://example.com/impressum"
  }
}

sample data, real response format

Simple process

From signup to enriched data

1

Create your API key

Sign up and create a key in the dashboard. No credit card, no call.

2

Call the endpoints

POST a name, a domain or a company. Every endpoint follows the same request and response conventions.

3

Get JSON back

Verified emails and firmographic profiles, ready for your CRM, your product or your waterfall. Misses are free.

An API you can build on.
Without reading the source.

Few endpoints, one set of conventions, public docs. What the docs say is what the API does.

One envelope everywhere

Every lookup returns found, credits_consumed and message, plus the endpoint's data fields. Every key is always present, hit or miss.

Errors you can handle in code

Machine-readable error codes, one flat error shape, and rate limits that answer with a Retry-After header.

Waterfall friendly

Synchronous responses that stay inside the time limits tools like Clay enforce, so a slow lookup never breaks your table.

Billing without surprises

Credits are spent only when we deliver a result. A miss or an outage on our side never costs you anything.

Docs that never drift

The reference is generated from the same definitions the API runs on, so it is always up to date. Inputs, outputs and error codes are specified exactly, with example requests and responses for every endpoint.

Read the docs

Pay for results, not attempts

A found email or profile costs credits. A miss costs nothing. Plans start small and scale with your volume.

See pricing

Frequently asked questions

Sign up, create an API key and send the first request in minutes. The docs cover every endpoint with example requests and responses.

Email finder and company enrichment today, with more on the way. All endpoints share one key and one set of conventions.

Machine-readable error codes in one flat shape, and rate-limit responses that carry a Retry-After header. All documented.

Yes. Endpoints respond synchronously within the time limits those tools enforce, so Treffer slots into a waterfall as one HTTP call.

Credits, spent only on found results. The pricing page lists plans and per-endpoint costs.

Your first API call in minutes

Free to try. Pay only for results.