Creditsafe Connect (1.10.9)

Metadata

KeyValue
tagsFull Connect API

Introduction

Creditsafe Connect is a REST API that provides access to the Creditsafe Global Company Database. This allows you to:

  • Control your master data
  • Utilize up-to-date Business and Director information, enhancing your onboarding and qualification processes
  • Receive alerts when your customer's and supplier's Credit Report changes

Check the status of Creditsafe Services HERE

Quick Start

To start your Creditsafe Connect API integration you will need to have activated your account and set a password by following the instructions in your Welcome Email. If you have not received a Welcome Email please contact your Creditsafe Account Manager.

By default, you will have been setup on our Sandbox environment.

Using a REST API client construct an /authenticate POST request and enter your username & password (case-sensitive) into the POST body. A successful response will return an authentication token.

Use the authentication token in an Authorization header on all other Creditsafe Connect calls as proof of your authenticity.

Download OpenAPI description
Languages
Servers
Mock server
https://creditsafe-connect-api.redocly.app/_mock/connect-apis-catalog/product-catalog/connect-api-full/connectapi/
Sandbox server
https://connect.sandbox.creditsafe.com/v1/
Production server
https://connect.creditsafe.com/v1/

Authentication

Endpoints for user authentication into the Connect API.

Operations

User Administration

Endpoints for user management.

Operations

Schema Structure

Endpoints to retrieve the structure of the Company and Director Search Criteria's and Reports.
The JSON schema is a blueprint of the data structure that will be returned in the response of the Company and Director Report endpoints. The schema can be used to validate the response data and understand the structure of the data returned. The schema is available for all countries and is a superset of all country's JSON schemas.

Operations

Companies

Endpoints to search for Companies in the Creditsafe Global Company Database. Companies are uniquely identified by the connectId - the identifier used to order a Company Credit Report. The Company Credit Report is a JSON object comprising of key business and financial data points such as Credit Score & Limit, Industry Code, Directors, Balance Sheet and Negative Information. A full list of Company data points can be found in the Data Matrix, in the help resources.

Operations

People/Directors

Endpoints to find People/Directors and order Director Reports. A Director Report will contain a person's registered information and Active & Previous Directorships, where available. This endpoint is not advised to get a list of directors for a specific Company. Instead, order a Company Credit Report using the /companies/{id} endpoint, and use the directors section in the response.

Operations

GB Consumers and AML

Operations

Images

Endpoints to order official Company Image/Filing Documents from

source. Company Filings such as Annual Account Statements, Annual Returns,

Liquidations and Changes of Registered Information can be downloaded as

PDFs, and are typically used as a resource in extended company

auditing/compliance.

Operations

Fresh Investigations

Endpoints to manage Fresh Investigation requests. With the need for accurate data, you can check on any company that is not available within our instant online database by placing a Fresh Investigation (Offline Order). Depending on the market, the information we obtain will vary. Using official sources and registries we are able to quickly answer questions about a company's stability and financial health. Where official information is not available we will conduct a direct interview with the business.

Operations

User Details

Operations

Create and View All Portfolios

Operations

Importing Portfolios

Operations

User Management of Portfolios

Operations

Individual Portfolio Management

Operations

Event Rules and Notifications

Operations

List Company Events

Request

Endpoint to return a collection of events for the given company, optionally filtered on the supplied search criteria. Event information will only be returned if the company exists in at least one of your portfolios.

Path
idstringrequired

The connectId of the company that you wish to retrieve events for.

Query
startDatestring(date-time)

The start date on which results are filtered.

endDatestring(date-time)

The end date on which results are filtered.

pageinteger

Starting page number inGlobal Monitoring is 0. If all items are displayed on one page this can also be left blank.

Default 0
pageSizeinteger

Number of items to return per Page.

curl -i -X GET \
  'https://creditsafe-connect-api.redocly.app/_mock/connect-apis-catalog/product-catalog/connect-api-full/connectapi/monitoring/companies/{id}/events?endDate=2019-08-24T14%3A15%3A22Z&page=0&pageSize=0&startDate=2019-08-24T14%3A15%3A22Z' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Bodyapplication/json
correlationIdstring

A unique ID assigned to this request.

Example: "23921650-c073-11ea-860f-06bc8182190e"
totalCountnumber

The total number of events returned for the given company.

Example: 1
dataArray of objects
pagingobject(ConnectMonitoringPaging)

Paging parameters.

Response
application/json
{ "correlationId": "23921650-c073-11ea-860f-06bc8182190e", "totalCount": 1, "data": [ { … } ], "paging": { "size": 10, "prev": 0, "next": 2, "last": 3 } }

All EventRules

Request

Get all available notification event rules. Notification event rules allow you to control which events you wish to monitor for the companies contained within a given portfolio.

curl -i -X GET \
  https://creditsafe-connect-api.redocly.app/_mock/connect-apis-catalog/product-catalog/connect-api-full/connectapi/monitoring/eventRules \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Bodyapplication/jsonArray [
isActiveboolean

Shows whether the notification event rule has been enabled for the given portfolio.

Example: 0
ruleCodenumber

The unique identifier for the notification event rule.

Example: 101
ruleCountryCodestring

The ISO/Alpha 2 format country code for the notification event rule. "XX" is used for global rules that apply to companies from all countries.

Example: "XX"
ruleTypenumber

The unique identifier of the ruleType for the notification event rule.

Example: 4
ruleTypeNamestring

A short description of the ruleType for the notification event rule.

Example: "Rating band change - 3 input"
namestring

The name for the notification event rule.

Example: "International Rating | Reduce by {0} Band(s) OR Less than Band {1}"
param0string

Some notification event rules may include input parameters used to tailor the notifications generated to your preference.

Example: "1"
param1string

Some notification event rules may include input parameters used to tailor the notifications generated to your preference.

Example: "A"
]
Response
application/json
[ { "isActive": 0, "ruleCode": 101, "ruleCountryCode": "XX", "ruleType": 4, "ruleTypeName": "Rating band change - 3 input", "name": "International Rating | Reduce by {0} Band(s) OR Less than Band {1}", "param0": "1", "param1": "A" } ]

Filtered EventRules

Request

Get all available notification event rules for the given countryCode. Notification event rules allow you to control which events you wish to monitor for the companies contained within a given portfolio.

Path
countryCodestring= 2 charactersrequired

ISO/Alpha 2 format country code for which notification event rules will be returned.

curl -i -X GET \
  'https://creditsafe-connect-api.redocly.app/_mock/connect-apis-catalog/product-catalog/connect-api-full/connectapi/monitoring/eventRules/{countryCode}' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Bodyapplication/jsonArray [
isActiveboolean

Shows whether the notification event rule has been enabled for the given portfolio.

Example: 0
ruleCodenumber

The unique identifier for the notification event rule.

Example: 101
ruleCountryCodestring

The ISO/Alpha 2 format country code for the notification event rule. "XX" is used for global rules that apply to companies from all countries.

Example: "XX"
ruleTypenumber

The unique identifier of the ruleType for the notification event rule.

Example: 4
ruleTypeNamestring

A short description of the ruleType for the notification event rule.

Example: "Rating band change - 3 input"
namestring

The name for the notification event rule.

Example: "International Rating | Reduce by {0} Band(s) OR Less than Band {1}"
param0string

Some notification event rules may include input parameters used to tailor the notifications generated to your preference.

Example: "1"
param1string

Some notification event rules may include input parameters used to tailor the notifications generated to your preference.

Example: "A"
]
Response
application/json
[ { "isActive": 0, "ruleCode": 101, "ruleCountryCode": "XX", "ruleType": 4, "ruleTypeName": "Rating band change - 3 input", "name": "International Rating | Reduce by {0} Band(s) OR Less than Band {1}", "param0": "1", "param1": "A" } ]

Instance Management

Operations

Decision Trees

Operations

Decision Logs

Operations

Run Decision

Operations

Decision Outcome

Operations

Bank Verification

Operations

Land Registry

Operations

Finance Agreements

Operations

US Search Support

Operations

FR Bank Match

Operations

Create and View All Jobs

Create a Data Cleaning job and view all jobs in the system.

Operations

Individual Job Management

Operations

Administrator Resources

Operations

Audit

Operations

Profile Management

Operations

Profile Updates

Operations

Profile Key Parties

Operations

Batch Uploads

Operations

Profile Business / Individual Details

Operations

AML Screening - Profile Management

Operations

AML Screening - Businesses

Operations

AML Screening - Individuals

Operations

AML Bulk Screening

Operations

AML Monitoring Management

Operations

Async AML

Operations

Global Monitoring

Operations

Reporting

Operations

Consumers

Update this description.

Operations