Xenia
  • Introduction
  • Getting Started
  • Authentication
  • Reference
    • Users
      • Invite User
      • Retrieve User
      • Update User
      • Delete User
      • Retrieve All Users
    • Teams
      • ☕Create Team
      • Retrieve Team
      • Update Team
      • Delete Team
      • Retrieve All Teams
    • Locations
      • Create Location
      • Retrieve Location
      • Update Location
      • Delete Location
      • Retrieve All Locations
    • Templates
      • Retrieve Template
      • Archive Template
      • Mange Template Access
    • Submissions
      • Retrieve Submission
      • Search Submissions
      • Download Submission Report
      • Delete Submission
    • Requests
      • Create Request
      • Retrieve Request
      • Delete Request
    • Folders
      • Create Folder
      • Retrieve Folder
      • Update Folder
      • Delete Folder
      • Retrieve All Folders
Powered by GitBook
On this page

Authentication

Connecting securely to Xenia's API

The API requires an authorization token for each request. A token can be generated from your Xenia account.

🚧

Please note that API tokens expire after 30 days of inactivity, at which point you would need to generate a new token to use. If a token is used to make API requests within that period, then it would not expire unless it's made invalid from new tokens.

Once you've obtained a token, it needs to be passed in the Authorization header on requests to the API. For example, Authorization: Bearer b7f8f791...f26e554d.

The Xenia API uses OAuth 2.0 as the means of authorization for individual requests. The initial authorization uses the Resource Owner Password Credentials Grant method and currently doesn't support any other flows.

The token used by the API is a Bearer token. It should be considered as a "personal access token" that you control yourself, for your own Xenia account. A pre-registered client ID and secret are not required to create an authorization token.

PreviousGetting StartedNextUsers

Last updated 1 year ago