Bedrijfsdata icon

Bedrijfsdata

Get data from the Bedrijfsdata API.

Overview

This node integrates with the Bedrijfsdata API to validate Dutch Chamber of Commerce (KvK) numbers. It sends a KvK number to the API and receives validation results indicating whether the number is valid according to official records.

Common scenarios:

  • Verifying user input for KvK numbers in forms or databases.
  • Cleaning and validating company registration data before processing.
  • Automating compliance checks where valid KvK numbers are required.

Practical example:
You have a list of companies with their KvK numbers, and you want to filter out invalid entries automatically. This node can be used in an n8n workflow to validate each KvK number and route or flag invalid ones accordingly.

Properties

Name Meaning
Kamer Van Koophandel (KvK) Number (Required) Enter a KvK number to validate

The property expects a string representing the KvK number to be validated.

Output

The node outputs JSON data containing the validation result from the Bedrijfsdata API. The exact structure depends on the API response but typically includes fields indicating:

  • Whether the KvK number is valid.
  • Possibly additional metadata about the company associated with the KvK number if valid.
  • Error or status messages if the validation fails.

No binary data output is involved.

Dependencies

  • Requires an active API key credential for the Bedrijfsdata API.
  • The node makes HTTP GET requests to https://api.bedrijfsdata.nl/v1.2/kvk with the KvK number as a query parameter.
  • Proper network access to the Bedrijfsdata API endpoint is necessary.

Troubleshooting

  • Invalid KvK number errors: If the API returns that the KvK number is invalid, verify the input format and correctness of the number.
  • API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network or timeout issues: Check internet connectivity and API availability.
  • Unexpected API responses: Could indicate changes in the API or malformed requests; review the KvK number input and node configuration.

Links and References

Discussion