Sandbox Environment - Coming Soon

The Company.info sandbox provides a safe environment to develop and validate API integrations without using production data.

The sandbox follows the same REST and JSON:API conventions as the production APIs. It uses synthetic or predefined data so that requests return predictable results during development and testing.

T0 availability

The sandbox is currently available for a selected set of APIs. Supported functionality and test data may be expanded over time.

Before you start

To use the sandbox, you need:

1. A Company.info Sandbox API key.
2. Access to the Sandbox environment.

A Sandbox API key provides access to all APIs currently supported in the Sandbox.

Authenticate each request by including your sandbox API key in the X-API-Key header:

X-API-Key: YOUR_SANDBOX_API_KEY

Use the following base URL for all Sandbox requests:

https://sandbox.api.company.info/

curl --request GET \
  --url 'https://sandbox.api.company.info/{endpoint}' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Accept: application/vnd.api+json'
  --globoff

Do not use production API keys or production data in the sandbox.

Choose your Sandbox access

Company.info provides two access models for the same Sandbox environment:

Organization Search and Organization Profile share one combined daily quota. Sandbox limits are applied separately from Production limits.

Available APIs

NL Organizations API

The NL Organizations sandbox contains a seeded dataset of synthetic organizations and branches. Use it to test search, profile retrieval, branch retrieval, pagination, and response handling.

Supported endpoints

Test data

The following seeded organization can be used for profile and branch requests:

Example: search for an organization

curl --request GET \
  --url 'https://sandbox.api.company.info/nl/organizations/profiles/v1/entities?query=Transport&page[number]=1&page[size]=10' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Accept: application/vnd.api+json'

Example: retrieve an organization profile

curl --request GET \
  --url 'https://sandbox.api.company.info/nl/organizations/profiles/v1/organizations/92016710' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Accept: application/vnd.api+json'

NL Official Documents API

The NL Official Documents sandbox returns a deterministic catalog of documents and predefined orders. It allows you to validate the complete ordering flow without requesting documents from the Dutch Trade Register.

Supported endpoints

Test data

Only the predefined identifiers are supported. The sandbox catalog includes multiple document types and formats, such as extracts, company history, statutes, and deposits.

Example: discover available documents

curl --request GET \
  --globoff \
  --url 'https://sandbox.api.company.info/nl/organizations/official-documents/v1/?filter[organizationID]=11111111' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Accept: application/vnd.api+json'

Example: place an order

curl --request POST \
  --url 'https://sandbox.api.company.info/nl/organizations/official-documents/v1/orders' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Content-Type: application/vnd.api+json' \
  --header 'Accept: application/vnd.api+json' \
  --data '{
    "data": {
      "type": "orders",
      "attributes": {
        "organizationID": "11111111",
        "documentType": "standardExtract",
        "mimeType": "application/json"
      }
    }
  }'

The order response contains an id. Use this value to retrieve the order and download the corresponding test document. When downloading a document, provide an Accept header matching one of the formats returned for the order.

NL Monitoring API

The NL Monitoring sandbox allows you to test the list, item, and update workflow. Lists and items are isolated to the authenticated sandbox customer.

After an item is added, the sandbox generates synthetic change updates for the requested collections. These updates normally become available after a short delay.

Supported endpoints

Test data

Use the seeded NL Organizations sandbox entity when adding an organization to a monitoring list:

List names must contain only alphanumeric characters. For example, use sandboxlist1 instead of sandbox-list-1.

Example workflow

1. Create a list

curl --request POST \
  --url 'https://sandbox.api.company.info/nl/organizations/monitoring/v1/lists' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Content-Type: application/vnd.api+json' \
  --header 'Accept: application/vnd.api+json' \
  --data '{
    "data": {
      "type": "lists",
      "attributes": {
        "name": "sandboxlist1"
      }
    }
  }'

Save the returned list id as LIST_ID.

2. Add an organization

curl --request POST \
  --url 'https://sandbox.api.company.info/nl/organizations/monitoring/v1/lists/LIST_ID/items' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Content-Type: application/vnd.api+json' \
  --header 'Accept: application/vnd.api+json' \
  --data '{
    "data": [
      {
        "type": "items",
        "attributes": {
          "entity": {
            "id": "92016710",
            "type": "organization"
          },
          "eventType": "change",
          "collections": ["activities", "address", "contact"]
        }
      }
    ]
  }'

3. Retrieve synthetic updates

Wait a few seconds after adding the item, then request the generated updates:

curl --request GET \
  --url 'https://sandbox.api.company.info/nl/organizations/monitoring/v1/lists/LIST_ID/updates' \
  --header 'X-API-Key: YOUR_SANDBOX_API_KEY' \
  --header 'Accept: application/vnd.api+json'

The sandbox generates one update for each requested collection. Use the returned entity.id and collection to test the same processing flow that your integration will use in production.

Important differences from production

The sandbox is intended for functional integration testing. Keep the following differences in mind:

• All organization, branch, document, order, and update data is synthetic or predefined.
• The available dataset is intentionally limited. Valid production identifiers may not exist in the sandbox.
• Monitoring updates are generated for testing and do not represent real-world changes.
• Document orders do not retrieve live documents from the Dutch Trade Register.
• Prices and processing times included in sandbox responses are test values and must not be treated as commercial terms or performance guarantees.
• The sandbox is not intended for load, capacity, or production performance testing.
• Sandbox data and behavior may be reset or updated as the environment evolves.

Moving to production

Before switching your integration to production:

1. Replace the sandbox base URL with https://api.company.info.
2. Replace the sandbox API key with a production API key.
3. Remove dependencies on predefined sandbox identifiers and responses.
4. Verify your production API permissions, commercial terms, rate limits, and quotas.
5. Confirm that your integration handles empty results, validation errors, rate limits, and temporary server errors.

The endpoint paths and JSON:API structures are designed to remain compatible, but production data and operational behavior may differ from the sandbox.

Support

If you need sandbox access or encounter an unexpected response, contact Company.info and include:

• The API and endpoint used
• The request timestamp
• The HTTP status code
• The X-Correlation-Id response header, when available
• A sanitized request and response without API keys or confidential data