API and Integrations

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 gracefully.

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.

Expected Release Date: April 2026

We’re pleased to inform you that our PDF Company Reports are getting 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 is currently planned for release on Wednesday 15^th April, the new design for our PDF reports will reflect the modern look of our web-based Company Reports.

Along with the improvement in design, we will also be upgrading 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.

Connect API Sandbox environment should be available Wednesday, 1^st of April. We strongly recommend that you check the PDFs at this point to ensure there is no impact on downstream processes.

Expected Release Date: 26th 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: 5th 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.