The Creditsafe DateCheck REST API has been developed to allow you to monitor changes and avoid fetching more data than necessary. The DateCheck REST API is designed to avoid unnecessary credit checks and letters of disclosure. The API itself never triggers letters of disclosure to be sent.
With DateCheck, you can verify if any of the included categories has changed on a consumer or company since a specific date. The API enables you to compare the date of your most recent credit decision with the latest date of change. The input is a social security number or organization number, and the response is a list of dates when the last change was made in each category.
DateCheck serves as an intelligent change detection service that:
- Monitors data changes - Tracks when specific data categories have been updated
- Avoids unnecessary credit checks - Enables you to make informed decisions about when new credit checks are needed
- Prevents disclosure letters - The DateCheck API itself never triggers disclosure letters to be sent
- Optimizes costs - Reduces the number of full credit report requests by identifying when no relevant changes have occurred
- Supports compliance - Helps minimize unnecessary disclosure letters by identifying what has changed before fetching credit data
The Integration team is available to assist with any technical questions that may arise during development or post-launch. You can reach them at integration@creditsafe.se
Customer Responsibility:
- The responsibility for tracking the date of the last credit decision and its outcome lies with the customer; the DateCheck REST API does not maintain this information
- It is mandatory to include a reference date in the request, which should correspond to the date of the last credit decision
- The response will contain any changes that have occurred since this date
Reference Date Limitations:
- The change date in the response cannot be older than:
- 36 months for consumers or sole traders (enskilda firmor)
- 60 months for limited companies (aktiebolag), trading companies (handelsbolag), or partnerships (kommanditbolag)
API Evolution:
- We reserve the right to add new information, tags, or attributes to the service at any time without prior communication
- We will not remove any existing elements without notifying you in advance
- We do not guarantee the JSON response will be delivered in the same order for all requests
Implementations using this service should primarily process requests sequentially, particularly when handling batch operations with large request volumes. Sequential processing helps ensure predictable behaviour and optimal use of the service.
A limited degree of parallelism is supported; however, client implementations must be designed to tolerate temporary request throttling if traffic exceeds allowed thresholds. Clients are expected to pause request execution and resume once additional requests can be accepted.
Creditsafe reserves the right to restrict access for implementations that generate excessive load or do not properly handle enforced request limitations. Please read more about rate limiting in the section about error codes.
Before requesting a full credit report for a returning customer, use DateCheck to see if any relevant data has changed since your last credit decision:
- No changes detected? → Use your previous credit decision without additional costs or disclosure letters
- Changes detected? → Evaluate if the changes are relevant to your credit decision logic
Set up periodic DateCheck calls for your customer portfolio to identify when credit profiles have changed, enabling proactive risk management:
- Monitor for negative changes (payment remarks, bankruptcies)
- Track positive changes (improved ratings, cleared debts)
- Trigger alerts for significant changes requiring review
Minimize disclosure letters by using DateCheck to determine what has changed before fetching credit data:
- Check if only "basic" category data changed (no disclosure required for GetData basic block)
- Identify if "credit" category data changed (may require disclosure for GetData credit block)
- Make informed decisions about when disclosure is truly necessary
Verify that no material changes have occurred between initial credit check and final decision:
- Perform DateCheck immediately before finalizing credit approval
- Ensure your decision is based on current information
- Catch late-breaking changes that could impact credit risk
- Store Decision Date - When you make a credit decision using GetData, store the date and outcome
- Check for Changes - For returning customers, call DateCheck with the stored decision date as reference
- Analyze Response - Review which categories changed and when they changed
- Make Informed Decision:
- No changes? → Reuse previous decision
- Basic changes only? → Fetch basic data (no disclosure)
- Credit changes? → Evaluate relevance before fetching credit data (may trigger disclosure)
Change Detection:
- Returns list of change codes with dates
- Covers both consumer and company data
- Shows most recent change date per category
Integration-Friendly:
- Simple REST API with JSON responses
- Works seamlessly with GetData API
- Supports both production and sandbox environments
- Includes health check endpoint for monitoring
Flexible:
- Optional transaction ID for tracking
- Language support (English/Swedish)
- Legacy format support for migration scenarios
The response tells you when a category changed, but not whether the change was positive or negative. You must fetch the actual data using GetData to see the new values.
Example:
- DateCheck shows "Rating" changed on 2024-06-15
- You don't know if the rating improved or worsened
- Call GetData to fetch the current rating value
Review the Step-by-Step Integration Guide to understand:
- When to use basic vs. credit blocks in GetData
- How to minimize disclosure letters
- Best practices for new vs. returning customers
Not all changes are equal. Some categories can be fetched without triggering disclosure letters:
- Basic categories (marked with * in documentation) - Can be fetched with GetData basic block, no disclosure
- Credit categories - Require GetData credit block, may trigger disclosure depending on entity type
See Change Categories for the complete list.
Before using DateCheck, you must authenticate using the CONNECT Authenticate API. The generated JWT token is valid for 1 hour and can be used across all Creditsafe Sweden REST APIs.
Authentication endpoint:
POST https://connect.creditsafe.com/v1/authenticateSee the Authenticate API documentation for details.
- Set up authentication - Review Authenticate API documentation
- Understand environments - Review Sandbox for testing guidelines
- Learn the integration flow - Read Step-by-Step Integration Guide
- Study change categories - Review Change Categories to understand what can change
- Review API details - Check Requests and Responses for technical specifications
- Plan error handling - Review Error Codes for troubleshooting
For technical questions during development or post-launch:
- 📧 Email: integration@creditsafe.se
For sales-related questions or service agreements:
- Contact your Creditsafe account manager