Authentication

Overview

The WeSeeDo API uses OAuth2 authentication. The password and client_credentials grant types are currently supported.

The flow to obtain an access token is depicted below.

Production and Sandbox environment

To be able to test your API integrations, a Sandbox environment is available. The Sandbox environment is equal to the Production and environment and allows you to test your API integrations.

Obtaining API credentials

API credentials can be created using our administrative interface (https://admin.weseedo.nl).
After logging in, API credentials can be managed using the API tab in the main menu. A client_id and client_secret will be generated.

NOTE: The client_secret is exposed only once. Make sure to copy it after creating the API credentials. If the client_secret is lost, it can only be reset to a new client_secret.

Authentication (client_credentials)

To authenticate using client_credentials flow, send the following request.

Send the following JSON body:

{ 
  "grant_type": "client_credentials", 
  "client_id": "REPLACE_WITH_YOUR_CLIENT_ID", 
  "client_secret": "REPLACE_WITH_YOUR_CLIENT_ID" 
} 

The server will reply with the following response:

{
	"access_token": "d33...59b",
	"expires": "2021-12-31T23:59:59.999Z",
	"token_type": "Bearer"
}

Use the generated access token to make authenticated API calls.

Authentication (password)

To authenticate using the password flow, send the following request.

Send the following JSON body:

{ 
  "grant_type": "password", 
  "client_id": "REPLACE_WITH_YOUR_CLIENT_ID", 
  "client_secret": "REPLACE_WITH_YOUR_CLIENT_ID",
  "username": "email_adress@weseedo.nl",
  "password": "TheAccountPassword#123"
} 

The server will reply with the following response:

{
	"access_token": "d33...59b",
	"expires": "2021-12-31T23:59:59.999Z",
	"token_type": "Bearer"
}

Use the generated access token to make authenticated API calls.

Making authenticated requests

To make an authenticated API request, the access token that was obtained in the previous step, needs to be sent along the request using the Authorization header.

Authorization: Bearer d33...59b