Journeys
  • Introduction
  • Getting access
  • Authentication
  • Terminology
  • API reference
    • Authorization
      • Authorize
    • Company
      • Retrieve company
      • Update company
    • Company lists
      • Retrieve company list
      • List company lists
      • Create company list
      • Update company list
      • Delete company list
    • Journeys
      • List journeys
      • Retrieve journey
      • Delete journey
      • Edit journey
    • Journey actions
      • List journey actions
      • Retrieve journey action
      • Delete journey action
    • Traveller journeys
      • List traveller journeys
      • Retrieve traveller journey
      • Retrieve actions
      • Start traveller journey
      • Create traveller journey
      • Delete traveller journey
    • Traveller journey actions
      • List journey traveller actions
      • Retrieve journey traveller action
    • Users
      • Invite
      • List users
      • Create user
      • Retrieve user
      • Delete user
      • Update user
  • Specification
Powered by GitBook
On this page
  • Authentication
  • Using the token

Authentication

Authentication

The API uses a Bearer token for authentication. To get one, we must first make an call to our authentication endpoint with the credentials we get from the Journeys system Client ID and a Client Secret.

When requesting a token, we use a JSON body to authenticate.

The endpoint to use is:

https://journeys-api.50skills.app/v1/auth/token/
{
  "client_id": "8s236ed66a5233443783ff7ffb0d91",
  "client_secret": "167632e0971219af444cab35d11858ac18ad9f70",
  "token_type:": "Bearer"
}  
{
  "expires_in": 35999,
  "access_token": "b8a281906f575c63c79a1d25b72b54ef3a2ecfa0",
  "token_type": "Bearer"
}    

Using the token

After receiving the Token, you are ready to start using the public endpoints available.

Authorization type we use is Bearer where the Token generated earlier is used along with the Prefix Bearer

Last updated 1 year ago

Example using Insomnia