The Robinson list check, inside your own system.

Q: What if an address can't be read?

match.level is null and the reason is addressunreadable. status is manual, never allowed, whatever level you chose.

Send a name and a Danish address. Get back exactly what we found: a level from 0 to 5, what matched, and which list version we checked against. Up to 1,000 people per call, large lists in the background.

The API is included in the annual plan. Write to us and your developer gets a test key.

One call, one answer per person

Send up to 1,000 people at a time. The answer comes straight back, in the same order.

RequestPOST /v2/checks

curl https://api.robinsontjek.dk/v2/checks \
  -H "Authorization: Bearer rl_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "people": [
      {
        "id": "42",
        "name": "Jens Hansen",
        "address": "Vestergade 12, 2. tv, 8000 Aarhus C"
      }
    ]
  }'

Response200 OK

{
  "list_version": {
    "published_on": "2026-10-01"
  },
  "results": [
    {
      "id": "42",
      "match": {
        "level": 5,
        "code": "name_address",
        "label": "Same name and address",
        "on": ["first_name", "last_name", "address", "unit"],
        "previous_address": false
      },
      "status": "blocked",
      "stop_level": 1,
      "reasons": ["name_and_address"]
    }
  ]
}

Each result starts with match: what we found (match.level, 0 to 5), a code and what matched. You decide what to do with it. If an integration needs a ready yes or no, it's in status, computed from the level you chose (stop_level, 1 by default). Send the address as one string or split into street, number, floor, door, postcode and city. See the levels in the documentation.

API documentation

Every endpoint, field and example.

Open the documentation

What you get

1,000people per call, answered straight away

1,000,000people per background job, with a callback when done

0 to 5a level for what we found, with what matched

Testkeys that behave like live ones and aren't billed

What the API does

The same rules and the same answers, whether you use the API, a file or one of our integrations.

People

Check up to 1,000 people in one call.

Large lists

Send a file or a long list. We check it in the background and let you know when the result and the check receipt are ready.

Companies

Checking CVR numbers for advertising protection is available as an add-on by agreement. Write to us.

List version

See which edition of the Robinson list is in use and when it was published.

Safe retries

Repeat a call with an idempotency key without anything being checked or billed twice.

OpenAPI

A full OpenAPI 3.1 description, so you can generate a client in your language.

We build the integration

No time or no developer? We build the connection to your system. It's included.

Write to us

You build it

The API is included in the annual plan. Write to us and we send your developer a test key. Read the docs while you wait.

Read the docs

API questions

Didn't find the answer? Write to us

What does the API cost?

It's included in the annual plan at DKK 15,000 excl. VAT. Write to us and your developer gets a test key.

How fast is it?

A single check answers in a fraction of a second. We don't call other systems while checking, so the answer doesn't depend on them being up.

What if an address can't be read?

match.level is null and the reason is address_unreadable. status is manual, never allowed, whatever level you chose.

Do you store the people we send?

We keep names and addresses for the number of days you choose, up to 90 and 30 by default, then delete them. Counts and the check receipt remain, and they hold no personal data.

Ready to connect?

Write to us and we send your developer a test key, and a person to ask.

Write to us See how it works