API and Integrations

Expected Release Date: June 2026

To ensure continued compliance with the terms and conditions of our data providers, we will be making updates to Dutch (NL) Director data within our platform.

What is changing?
Effective June 9th 2026, we are implementing the following changes:

• Removal of NL Director Search: All NL Directors will be removed from the standalone Director Search tool.
• Discontinuation of Director Reports: Dedicated Director reports for NL individuals will no longer be available for retrieval.
• Director product (search and report) is being removed from our web and Connect API platforms.

How to access NL Directorship information

While the standalone search is being retired, this data remains available through our company-level insights. To check the directorships of NL individuals moving forward, please view the directorships section within the specific Company Report.

What do you need to do? If you have automated processes or internal workflows that rely on the standalone NL Director Search or specific Director reports, you will need to update your procedures to pull this information from the Company Reports instead. 

Expected Release Date: May 2026

There will be an upcoming update to the Creditsafe Connect API to improve the structure and consistency of our Swedish Company Reports.

Effective Thursday 28th May 2026, we are implementing several changes to how director and official data are mapped within our API response. While these updates are designed to better align our data models with official registries, they may require action from your technical team.

What is changing?
To provide a more structured and reliable experience, we are making the following adjustments to the JSON response for Swedish reports:

• Value/Field Removals: We are removing the field resignationDate. Additionally, values in the fields id, idType and pnr will be removed for foreign directors. The roles 29, 30 in the positions array has been replaced with a new field named residentAbroad.
• Identifier Format: The format of the id field is changing. Please note that this identifier can no longer be used to retrieve a company report. It will now only be returned for directors and can be used to request a director report.
• Current ID: “id”: “SE-0-5560296740"
• New ID: “id”: “SE-5560296740"
• New Data Elements: We are adding several new data elements to the response to provide more comprehensive information. These additions are non-breaking and do not require logic changes. For more information on these changes, you can learn more here.
• Certificate Data: From April 13th, it will no longer be possible to obtain certificate information in Swedish reports.

Why are we making this change?
These updates enhance the overall consistency of the API and ensure that director information, including resignation details, is retrieved from a structured list rather than a single field. The changes also help ensure that identifiers are used for their intended purpose and align with our global data standards.

What do you need to do?
Whether you need to take action depends on your current system configuration.

• Action Required: If you have automated integrations or scripts that rely on the changed/removed fields (id, idType, pnr, for foreign directors, or resignationDate) or the previous identifier format, you will need to update your parsing logic.
• No Action Needed: If your system does not rely on these specific fields or behaviours, you should not be affected by this update.

Expected Release Date: May 2026

There is an upcoming update to our Connect and GGS APIs regarding how company searches are conducted for Colombia, Ecuador, and Venezuela.

What is changing?
As part of our commitment to providing best-in-class solutions, we have recently migrated to a new, more robust integration for our South American data.

Effective May 28th 2026, we are making the following adjustment to the search functionality for these specific countries:

• Removal of Company ID Search: The ability to search for companies using a specific provider "Company ID" will be removed.
• Continued Search Support: You will continue to have full access to search for companies using all other standard criteria, including:
  • Company Name
  • City
  • Registration Number
  • VAT Number
  • Province

Why are we making this change?
This update is part of a wider project to move our services onto modern, more reliable integrations that align with our global data standards. These changes ensure a more stable and consistent experience when retrieving reports for these regions.

What do you need to do? Whether you need to take action depends on your current system configuration.

• Action Required: If you have automated integrations or scripts that rely specifically on searching via the "Company ID" field for Colombia, Ecuador, or Venezuela, you will need to update your logic to use alternative identifiers such as the Registration Number or Company Name.
• No Action Needed: If your system uses Name, City, or Registration Number for searches, which represents the vast majority of our user activity, you should not be affected by this update.

Expected Release Date: June 2026

Creditsafe has embarked on a major data migration project as part of our ongoing efforts to modernise our infrastructure and enhance system reliability. As part of this project, we’re moving away from some legacy database software that supports several of our backend APIs.

As part of this transition, a small amount of German search and company report data in GGS will be impacted. There will be some changes to the data in the company report response.

When will this change happen:
This change will take effect on Thursday 4th June.

What do you need to do:
If your systems or reports currently depend on any of the affected data fields, we recommend the following:

• Review the impacted data fields in the document linked in the button below.
• Make any necessary adjustments to your processes before Thursday 4th June.

If you do not use these fields, no action is required.

Please note, that there may be minor changes to the namespaces of data elements within the <additionalinformation> element. Most integrations will not be affected. However, if your integration is built using .NET, we recommend testing it against the GGS API to ensure the <additionalinformation> data continues to parse correctly.

Expected Release Date: May 2026

There will be some upcoming changes to Finnish company data available via our website and Connect API expected to take place on Thursday 14th May. These updates form part of broader improvements to the data we provide. For API customers, some changes will require action ahead of the release date.

What is changing?
1. Removal of "Previous Score" and "Latest Rating Change Date" fields

The previousScore and latestRatingChangeDate fields will be removed from Finnish company report responses to improve accuracy and consistency across all our products, in particular, our Monitoring service.

For API customers, please ensure any logic in your integration that reads or depends on these fields is updated ahead of the release to avoid unexpected errors.

2. Changes to VAT Registration Number (vatRegistrationNumber)

We are making two improvements to the vatRegistrationNumber field for Finnish companies:

• Format change: VAT numbers will now be returned with a standardised "FI" country prefix in line with the internationally recognised format. For example, a value previously returned as 12345678 will now be returned as FI12345678. If your API integration stores, validates, or processes this field, you will need to account for the additional 2 characters in the returned value.
• Accuracy improvement: The field will now only be returned for companies that hold an active VAT registration. Where a company does not have an active VAT number, the field will no longer be present in the response. Please ensure your integration handles the absence of this field.

What do you need to do before the release? 

• Remove any dependencies on previousScore and latestRatingChangeDate from your integration
• Update any field length or format validation for vatRegistrationNumber to support the new "FI" prefixed format (e.g., FI12345678)
• Ensure your integration handles Finnish company responses where vatRegistrationNumber is not returned

We strongly recommend reviewing and testing your integration ahead of the go-live date to minimise any disruption.

Released: April 2026

We’re pleased to inform you that our PDF Company Reports have been updated with a new look in the following countries:

Afghanistan, Algeria, Burkina Faso, Bahrain, Benin, Cambodia, Democratic Republic of Congo, Egypt. Iraq, Iran, Jordan, Kuwait, Laos, Lebanon, Libya, Malaysia, Mexico, Morocco, Myanmar, Oman, Palestine, Qatar, Saudi Arabia, South Sudan, Sudan, Syria, Thailand, Tunisia, United Arab Emirates, Vietnam, Western Sahara, Yemen and Worldwide PLCs.

This update went live on Wednesday 15^th April, and the new design for our PDF reports now reflects the modern look of our web-based Company Reports.

Along with the improvement in design, we have also upgraded the PDF report content in line with the availability of data via our Web and API JSON response. We expect to see between a 10-30% increase in data fields available on each Connect API PDF response per Country. 

As part of the PDF redevelopment, we are also utilising a new PDF rendering engine that enhances the performance of the PDF rendering process. This reduces latency on the Connect API responses when making requests to PDFs.

Released: March 2026

On March 26th 2026, we are restructuring how Key Financials are delivered in the Connect API response. Currently, these data points reside within localFinancialStatements. To improve data consistency and ensure the API aligns with the data displayed on our website, Key Financials will be moved to their own dedicated section.

What is changing?

• New Location: Key Financials are moving out of localFinancialStatements and into a new "Key Financials" section within the API response.
• Data Availability: All underlying data remains available; only the location within the JSON structure is changing.
• Logic: The key financial summary in the website will be updated to use the same key financials section.

Why are we making this change?

This update addresses historical inconsistencies where data was occasionally missing from the local section. This change ensures that the API response matches exactly what is displayed on the website, providing a more reliable experience across all historical years.

What do you need to do?

If you have automated scripts or coding that pulls this specific data, you will likely need to update your file paths. Please review the following Technical Document.

Released: March 2026

We have updated the Industry classification codes used in our Austrian data. The fields Main Code and Principal Activity, which previously used the Austrian NACE 2008 classification, have moved to the NACE 2025 classification.

The updated classification reflects the latest industry standards and ensures business activities remain accurately aligned with current economic structures.

To support the transition, both NACE 2008 and NACE 2025 codes will be provided in parallel as additional information until 31 December 2026.

Customers should use the NACE 2025 code as the primary reference for Main Code and Principal Activity. The NACE 2008 code should be treated as supplementary information only during the transition period.

If your internal processes, reports, integrations, or data mappings currently rely on NACE 2008, we recommend reviewing and updating these to ensure compatibility with NACE 2025.