Authentication
Getting access to our endpoints and functionality
Last updated 22 May 2024
Before using any endpoint provided by Skrym you need to be able to authenticate your calls to our system. š Find out more below.
Users & Systems
In the Skrym ecosystem there are two different kinds of agents. These agents use different methods of authenticating themselves but have similar capabilities in what they can request. The different agents are:
Agent | Access through | Authenticates with |
---|---|---|
š©š»āš» Users | https://scope.skrym.com | Username and password |
š¤ Systems | https://api.skrym.com | Tokens |
Obtaining accessSkrym is currently only available to select clients and partners. If your organization does not have access but you would like to try out Skrym, you can reach out to us.
We have an ambassador program for developers and professionals.
š©š»āš» User
Through the initial onboarding with Skrym an organization will be set-up for you. Users are provided with a sign-up link to create an account for our dashboard and tool SCOPE. The account will then be tied to the users organization with the permissions for that user set by the organization.
There are two levels of SCOPE access Admin and Standard. SCOPE Admins can send invites to their organization.
š¤ System
Skrym uses Bearer Authentication for authenticating API-requests. This requires the user to provide a token with each request to the system.
During the onboarding process Skrym will provide the necessary information to obtain a token.
WarningKeep your credentials secret! If your user or system credentials have been compromised please contact Skrym.
Using different products
The authentication provided by both systems for users also contain information regarding which products they have available at their disposal.
- š¦ Optimization
- š± Emission calculation
- š Transport Management
If you find yourself wanting to use one of the APIs that you currently are not authorized to use, please contact your Skrym representative.
Authenticating an API-request
For the request to return a successful result you have to provide the provided token in the request header.
Setting the Authorization
Here are some examples of how you can set the authentication token in the header