A unique api key will be issued for each user account wishing to access the api. An example key would look as follows:
QW9uLlRCUy52MS40RUQ0N0JDMy1COTk2LTQ1QkMtQTc5MS1BRUM0NkE0RDFCOEI=
This api key needs to be base64 endoded and placed in the authorization header of each request:
Authorization: UVc5dUxsUkNVeTUyTVM0MFJVUTBOMEpETXkxQ09UazJMVFExUWtNdFFUYzVNUzFCUlVNME5rRTBSREZDT0VJPQ==
Many of the endpoints require a tenant identifier which can be retrieved using the '/tenant' endpoint.
CE150D1B-FE27-498A-8783-F0FE1DA23D03
To make a request to an endpoint which requires a tenant identifier you add the identifier to the api key using a '|' (pipe) delimiter and base64 encode the result.
QW9uLlRCUy52MS40RUQ0N0JDMy1COTk2LTQ1QkMtQTc5MS1BRUM0NkE0RDFCOEI=|CE150D1B-FE27-498A-8783-F0FE1DA23D03
Becomes:
UVc5dUxsUkNVeTUyTVM0MFJVUTBOMEpETXkxQ09UazJMVFExUWtNdFFUYzVNUzFCUlVNME5rRTBSREZDT0VJPXxDRTE1MEQxQ
i1GRTI3LTQ5OEEtODc4My1GMEZFMURBMjNEMDM=
This new value is then placed in the authorization header of each request:
Authorization: UVc5dUxsUkNVeTUyTVM0MFJVUTBOMEpETXkxQ09UazJMVFExUWtNdFFUYzVNUzFCUlVNME5rRTBSREZDT0VJPXxD
RTE1MEQxQi1GRTI3LTQ5OEEtODc4My1GMEZFMURBMjNEMDM=