Endpoints

Both customer facing environments has an available Swagger front with available documentation.

<aside> ❗

Please note that some of the schemas is not correct when customer configuration is applied - so please verify the output when the customer configuration is applied.

</aside>

QA: https://api.qa.deepalpha.app

Production: https://api.deepalpha.app

Authentication

<aside> 💡

Using the Swagger, the client_id + client_secret can be entered directly into the Authorize dialog box - which will handle the token issue.

</aside>

All usage of the Public API credentials will be using client_id and client_secret which is provided from Quantfolio AS upon getting access to using the endpoints.

Obtaining a token can be done as follows (HTTP example):

POST <https://api.qa.deepalpha.app/v1/auth/token>

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

The response obtained looks like this:

HTTP/1.1 200 OK
Content-Type: application/json

{
  "access_token": "eyJ..."
}

Doing requests with the Bearer token

The APIs is using stateless JWT-bearer tokens, sent in the Authorization header with prefix Bearer.

This means that when sending an API call to Quantfolio DeepAlpha Platform, the header looks like this:

Authorization: Bearer eyJ...