Overview API Documentation

Using the APIs

Only the KVK Zoeken API delivers multiple results, the other APIs all return a single result. If a search with Basisprofiel, Vestigingsprofiel or Naamgeving results in multiple registrations, the first result will be shown. Therefore, we recommend using a combination of fields to make your search in the Zoeken API as specific as possible. For instance you could combine

• KVK number and branch number (vestigingsnummer).
• KVK number and RSIN number (RSIN: Rechtspersonen en Samenwerkingsverbanden Informatienummer - Legal Entities and Partnerships Identification Number)
• KVK number and type (branch, main branch, and/or legal entity)

For free format search, the other input parameters (e.g. trade name, street name, etc.) can be used.

Data model

The Zoeken API contains 2 separate entities that differ in their property "type":

• Branch
• Legal entity

Example of legal entity in Zoeken API

Copy
{
  "pagina": 1,
  "aantal": 10,
  "totaal": 1,
  "resultaten": [
    {
      "kvkNummer": "69599068",
      "handelsnaam": "Test Stichting Bolderbast",
      "adresType": "bezoekadres",
      "straatnaam": "Oosterwal",
      "plaats": "Lochem",
      "type": "rechtspersoon",
      "_links": {
        "basisprofiel":  {
          "href": "https://api.kvk.nl/test/api/v1/basisprofielen/69599068"
        }
      }
    }
  ]
}

Example of type branch in Zoeken API

Copy
{
  "pagina":1,
  "aantal":10,
  "totaal":1,
  "resultaten":[
    {
      "kvkNummer":"68750110",
      "vestigingsnummer":"000037178598",
      "handelsnaam":"Test BV Donald",
      "adresType":"bezoekadres",
      "straatnaam":"Hizzaarderlaan",
      "plaats":"Lollum",
      "type":"hoofdvestiging",
      "_links":{
        "basisprofiel": {
          "href": "https://api.kvk.nl/test/api/v1/basisprofielen/68750110"
        },
        "vestigingsprofiel": {
          "href": "https://api.kvk.nl/test/api/v1/vestigingsprofielen/000037178598"
        }
      }
    }
  ]
}

HATEOAS

The Zoeken API offers the possibility to search for company data, location data and/or legal entities. The Basispofiel and Vestigingsprofiel APIs are linked to the Zoeken API. Search results contain URLs to the related Basisprofiel en Vestigingsprofiel resources. Within REST this is also known as HATEOAS. We used the HAL standard for these APIs to implement HATEOAS.

Results

• Registrations that are no longer active are not shown in the results by default.
• Search works on whole-text d-matching. For example, "koophand" has zero results while "koophandel" has about 1,000 results.
• The KVK Zoeken API displays a maximum of 100 results per page (default = 10 results per page).
• The API does not guarantee that the results are in order (branches or legal entities). But there is a preference for sorting by headquarters, branches, legal entity.

Output standard

An http GET-request is the only allowed http request. The KVK APIs use the standard JSON object (JavaScript Object Notation) as output. This facilitates generic results for the API output. It also contains a number of metadata elements that are included with every JSON output (page, count, total, next and previous). We use the specifications prescribed by JSON.org. However, there are 2 very specific features related to the KVK API JSON output:

Registratiedatum

The date registered in the Trade Register can contain zeros as the date is unknown. If the full date is known then the format is: YYYYMMDD (year/month/day). Only numeric values are allowed (including 0 for unknown parts of the date).
For example:

• complete date: 20150622
• day unknown: 20150600
• month unknown: 20150000
• date unknown : 00000000

Geo-data

GEO data is geographic data used to determine the location of addresses and buildings to indicate. Using the BAG IDs (addressableObjectId and numberIndicationId) can be entered in the BAG (Basic Registration Addresses and Buildings) are searched for, among other things, surface area and purpose of use.
Geo-data is retrieved by including an extra parameter “?geoData=true” in the call to location profiles. By default, this parameter is set to false. The coordinates are only provided if they are known (for PO boxes for example, this will be empty).

Example of GEO-data as part of an address:

Copy
{
  "adressen":[
    {
      "type":"bezoekadres",
      "indicatieAfgeschermd":"Nee",
      "volledigAdres":"Watermolenlaan 1 3447GT Woerden",
      "straatnaam":"Watermolenlaan",
      "huisnummer":1,
      "postcode":"3447GT",
      "plaats":"Woerden",
      "land":"Nederland",
      "geoData":{
        "addresseerbaarObjectId":"0632010000010090",
        "nummerAanduidingId":"0632200000010090",
        "gpsLatitude":52.08151653230184,
        "gpsLongitude":4.890048011859921,
        "rijksdriehoekX":120921.45,
        "rijksdriehoekY":454921.47,
        "rijksdriehoekZ":0
      }
    }
  ]
}