Bedrijfsdata icon

Bedrijfsdata

Get data from the Bedrijfsdata API.
Join our community

Actions31

Overview

This node integrates with the Bedrijfsdata API to perform validation and cleansing of various data types. Specifically, for the Validation & Cleansing resource with the Validate LEI Number operation, it validates Legal Entity Identifier (LEI) numbers. LEI numbers are unique identifiers assigned to legal entities participating in financial transactions worldwide.

Use cases include:

  • Verifying the correctness of LEI numbers before processing financial or regulatory data.
  • Ensuring data quality in customer or partner databases by validating entity identifiers.
  • Automating compliance checks that require valid LEI numbers.

Example: You have a list of LEI numbers from your clients and want to confirm their validity before submitting reports to regulators. This node can validate each LEI number via the API and return validation results.

Properties

Name Meaning
Legal Entity Identifiers (LEI) Number The LEI number string to validate. Must be provided. Example: "5493001KJTIIGC8Y1R12"

Output

The node outputs JSON data containing the validation result returned by the Bedrijfsdata API for the given LEI number. The exact structure depends on the API response but typically includes fields indicating whether the LEI is valid, details about the entity, and possibly error messages if invalid.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Bedrijfsdata API.
  • Requires an API key credential configured in n8n for authentication.
  • The node sends a GET request to the /lei endpoint of the Bedrijfsdata API with the LEI number as a query parameter.

Troubleshooting

  • Common issues:

    • Invalid or malformed LEI number input will cause the API to return errors or invalid status.
    • Network connectivity problems or incorrect API credentials will cause request failures.
    • Exceeding API rate limits may result in throttling errors.

  • Error messages:

    • Errors from the API are surfaced as node execution errors with messages describing the failure.
    • If the node throws an error like "Failed to fetch cities" or similar, it indicates an unexpected API response or network issue (note: this message is from a different operation but similar patterns apply).

  • Resolution tips:

    • Ensure the LEI number is correctly formatted and complete.
    • Verify API credentials and network access.
    • Check API usage limits and retry after some time if throttled.

Links and References

Discussion