API Documentation

This documentation describes how to use the Evolution API for searching Teledata, CVR, and the Robinson list.

---

Authentication

The API uses ClientId and ClientSecret for authentication. These are sent via:

• HTTP Basic Auth in the Authorization header

Example (Basic Auth):

Authorization: Basic {base64(ClientId:ClientSecret)}

---

Endpoint

POST /api/search
Content-Type: application/json

Request Body

{
  "type": "teledata",
  "phoneNumber": "22446688",
  "name": "Peter Hansen",
  "address": "Birkegade 12",
  "zipCode": "2200",
  "city": "København N"
}

• type: Required - one of: teledata, cvr, robinson
• Other fields depend on the type (see below)

Fields per type

• teledata:
  • Either phoneNumber,
  • Or all of: name, address, zipCode, city
  • Or: address, zipCode, city (without name)
• cvr:
  • Either cvrNummer
  • Or: name + address + zipCode + city
  • Or: address + zipCode + city
• robinson: Required: name and address

Example using curl

curl -X POST https://findnummernu.dk/api/search \
 -H "Content-Type: application/json" \
 -u clientid123:mysecretkey \
 -d "{\"type\":\"teledata\", \"address\":\"Birkegade 12\", \"zipCode\":\"2200\", \"city\":\"København N\"}"

---

Response Structure (Example)

[
  {
    "name": "Peter Hansen",
    "address": "Birkegade 12",
    "zipCode": "2200",
    "city": "København N",
    "phoneNumbers": ["22446688", "22223333"]
  }
]

Results with the same name + address will be grouped, and all associated phone numbers will be listed under phoneNumbers.

---

Error Handling

The API returns appropriate status codes and error messages:

• 400 Bad Request - Missing or invalid fields
• 403 Forbidden - No access to the requested type
• 401 Unauthorized - Incorrect login credentials

Example error

{
  "error": "You do not have access to."
}

---