Provides you with accesss to Bisnode Company Risk and Credit data for Sweden, Finland and Denmark.

If you are looking for version v1 you can find it here.

Changes in v2

1. Introduced a new date model.

Instead of the ISO 8601 format "yyyy-MM-dd" we added a model for setting year, month and day separately:

before:

"someDate": "2019-01-16"

after:

"someDate": {
    "year": 2019,
    "month": 1,
    "day": 16
}

This gives us the flexibility to deliver dates where we only have a fraction of the data, For instance we may only have the year.

2. Introduced a new Identifiers construct where we earlier had duns and/or registrationNumber

before:

"dunsNumber": "343630447"

after:

"identifiers": {
      "registrationNumber": "260428882",
      "dunsNumber": "343630447"
    }

3. Changed all type double to plain string.  This is to avoid losing precisions in some cases where a float may not be sufficient.

4. Updated amount model and renamed monetaryAmount —> amount

before:

"amount": {
    "currency”: "SEK",
   "monetaryAmount": 70000
}

after:

"amount": {
    "currency": "SEK",
   "amount": “70000"
}

5. Refactored registeredAddress
  

Introduced an Address model which may contain either a StreetAddress or a PostalOfficeBox.

before:

"registeredAddress": {
        "town": "Søborg",
        "countryCode": "DK",
        "postalCode": "2860",
        "street": "Gyngemose Parkvej 50, 8."
      }

after:

"registeredAddress": {
        "streetAddress": {
          "town": "Søborg",
          "countryCode": "DK",
          "postalCode": "2860",
          "street": "Gyngemose Parkvej 50, 8."
        }
      }

    
6. Some minor changes. Typo’s etc ...

Authentication

 To use the Credit Information B2B REST API - v2, you need a client ID and a secret. Bisnode uses OAuth2 for authentication. More information here.

 Get started

You'll need 3 things to get started.

• Bisnode ID (contact api-support@bisnode.com for one if you don't have it yet)
• Sandbox API Key (you need to be logged in with your Bisnode ID to get it)
• Subscribe to the API (you need to be logged in with your Bisnode ID to subscribe)

For easy access we have provided you with a postman collection here.

Key Features

Company data available through an API

Provides you with high quality analyzed risk and credit data.

• High quality credit rating for profitable decisions
• Avoid credit losses by doing business with the right customers
• Get stable customers that you know can pay on time
• Get new insights by combining your own customer data with Bisnode analyzed company data

How to use the API

This guide is intended to help you get going with your integration against the Bisnode Credit Information B2B API. It serves as a complement to the  Endpoint Reference  and aims to bring a high level understanding of the key concepts of the platform. 

For questions and support, please contact Bisnode at api-bisnode@bisnode.com

A more detailed view of the swagger documentation can be found on swaggerhub:https://app.swaggerhub.com/apis-docs/bisnode-apis/CompanyCreditDataAPI/2.0.0

A postman collection for accessing sandbox data can be found here:  https://github.com/Bisnode/api-stuff/tree/master/apis/brigs/company/postman-collections

Instructions on how to generate keys to access sandbox and production environments can also be found on the link above.

Search

Name and address control. Do a search on name, duns-number or registration-number.

Credit information

Fetch credit data on a specific company by supplying registration-number.

Changes and versioning

API version is provided in the base of the requested URL in the form of "v1", "v2" etc. Only major version numbers are used.

API versions are raised only on breaking (i.e. backwards incompatible) changes in the API. Fields may be added but will never be removed during an API version lifecycle. When developing your application, take care to ensure that your application is able to handle additional fields.

How to test

Test data available in sandbox:

Authentication 

Authentication using OAuth2

Bisnode's newest APIs use OAuth2 for authentication. For all API requests, you need to supply an access token in order to authenticate yourself. To obtain such an access token you need to submit your CLIENT_ID and CLIENT_SECRET to Bisnode's authentication endpoint at https://login.bisnode.com/as/token.oauth2. The access token is then passed along in the Authorization header to all API requests. Follow the instructions below to learn how to do this.

Get and Use the Access Token

Step 1. Get the Access Token

To get an access token you need to make a POST request to https://login.bisnode.com/as/token.oauth2 using the following HTTP header: Content-Type: application/x-www-form-urlencoded and the following request body: grant_type=client_credentials&scope=credit_data_companies. The request must be authenticated using HTTP Basic authentication and your CLIENT_ID and CLIENT_SECRET.

Example in cURL

curl -X POST \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d 'grant_type=client_credentials&scope=credit_data_companies' \
     -u "$CLIENT_ID:$CLIENT_SECRET" \
     https://login.bisnode.com/as/token.oauth2

Example response

{
  "access_token": "eyJhb....seAtPCCQ",
  "token_type": "Bearer",
  "expires_in": 7199
}

Step 2. Use the Access Token

Supply your access token with all requests to the API using the HTTP Authorization header: Authorization: Bearer <your access token here> You should reuse the access token for multiple calls to the API. See the next section on recommended usage.

Example in cURL - search for company

curl -X POST \
     -H "Authorization: Bearer eyJhb...seAtPCCQ" \
     -H 'Content-Type: application/json' \
     -d '{"name": "bisnode", "country": "SE"}' \
     https://api.bisnode.com/credit-data-companies/v2/companies

Reusing the Access Token

After you have fetched an access token you should save it and use it for subsequent calls to the API. There is no limit on the number of calls it can be used for, but it will expire after a certain time.

We recommend that you use the expires_in field to determine when to request a new access token. It specifies the number of seconds the token will be valid for. Because of possible delays in network communication as well as delays between checking the timestamp and transmitting the actual API request, it is a good idea to request a new token a few seconds before it is about to expire. This minimizes the risk of accidentally using an expired token.

The following pseudo code illustrates how to use the authentication endpoint together with the API.

function make_authorized_api_request():
    token = get_cached_access_token()
    if token == null or is_soon_to_be_expired(token):
        token = get_new_access_token()
        save_to_cache(token)
    make_api_call(token)


function get_new_access_token():
    token = get_token_from_auth_endpoint()
    token.expiration_timestamp = now().add_seconds(token.expires_in)
    return token


function is_soon_to_be_expired(token):
    # Add time margin to avoid token expiring during call
    if now().add_seconds(60) >= token.expiration_timestamp:
        return true
    return false