Introduction

We have implemented a REST API as a method for (advanced) users to access and modify their LYNX data without needing the LYNX client. This is useful for:

• Users who want to retrieve a lot of data straight from the database instead of relying on exports from the reporting module.
• Users who want to build different applications to view their data dynamically. For example, a dashboard on a website, where they can feed the data directly from LYNX to their application.

The link to the REST API:  https://lynx.a-dato.com/api/

All the available endpoints for the different objects can be found in the swagger documentation.

Please note: the REST API is a new development and is still in progress, therefore it is subject to change. We will keep this documentation up to date as things change. If you find any issues or have any ideas for improvement, please contact our support via emailing support@a-dato.zendesk.com. 

What is REST API

API stands for application programming interface. It is a way for devices/applications to interact together and shares data. In this case, allowing a user to retrieve data from our system/database.

REST stands for representational state transfer. It is an architectural style for API which uses HTTP requests to interact with the data. This allows the data to be useable on the web.

Downside for using a REST API is the users using it are required to have some technical knowledge and be able to work with JSON and GET/PUT/DELETE API requests. Our documentation is meant to guide users with some background in the previously mentioned items.

Authentication

You can view all the available endpoints in the Swagger documentation that can be found here: https://lynx.a-dato.com/api/index.html. 

However, to be able to try out the endpoints in the Swagger documentation, you are required to login in the Swagger documentation, or another client via the following steps:

1. Login into Lynx.
2. Go to the user icon on the top right corner and choose "My Profile".
3. Under the "API Key" tab
4. Choose the expiring duration for the API Key.
5. Generate the key and copy the API key.
6. Click on the "Authorize" button.
7. Paste the API Key to login

Please note: The generated API Key is not stored anywhere, so we recommend that you store it somewhere.

• If you lose the API key, you can generate another one, which will over-ride the old one.
• If you no longer need the API key, you can use the "Revoke API Key" to disable access using that key.

Please note: To access the REST API, you will need the REST API key for authorization.

• Using Swagger Docs: Simply click the "Authorize" button and enter your REST API key.
• Using Other Clients: Include your REST API key in the Authorization header of your HTTP request, like this:

Authorization: Bearer <REST API key>

Important: The REST API key is a JWT bearer token, so make sure to use the Bearer keyword before the token when including it in the Authorization header.

Available objects:

The API endpoints takes care of the following objects:

• Me: This contains the information of the current session and the logged in user.
• Users: This contains the list of users and their information that are invited to the current active space.
• Projects: This contains the information of projects in the current active space. 
• Spaces: This contains the list of workspaces the current user has access to. Each user can have access to multiple spaces with different roles, and each space can have different settings and projects.
• Resources: This contains the list of resources configured in the current active space. Resources are the specific items working on a task, for example, employees. 
• ResourceClasses: This contains the list of skills configured in the current active space. Skills come with different types (Normal, Virtual, Team, and Global) and can be configured differently.
• UnitsOfMeasure: This contains the list of Units of Measures configured in the current active space. Units of Measure are used in (project, task, card, and note) custom fields, workpackage type tasks, skill outputs, and budget management. 
• Tasks: This contains the information of tasks in the current active space.
• Cards: This contains the information of cards in the current space. Cards are added to tasks of type workpackage.
• Notes: This contains the information of notes in the current space. Notes can be added to projects, tasks, or cards.
• Documents: This contains the documents in the current space. Documents can be added to projects, tasks, or cards.
• ResourceRequirements: This contains the resource requirements in the current space. Resource requirements are skills (with or without resources) or resources added to a task as the workload / effort and resource / skill working on the task.
• Calendars: This is the list of calendars in the current active space. 
• BudgetGroups: This is the list of budget groups in the current active space, which are used for resource requirements. 
• TimeTracking: This contains the tracking information in the current active space. Projects, tasks, and cards have time tracking.
• BudgetItems: This contains the budget information assigned to resource requirements or tasks in the current space.
• MyTasks: This contains all the data that's required for the "My activities" view for the current user in the current active space.

You can check the Swagger documentation for the valid endpoints for each object and child object. At the end of the documentation, you can also see the schemas of each object which shows the structure of the objects.

What can be done?

Using the REST API, you can:

• Use GET request: retrieve data from your spaces.
  • Use filters to filter your retrieved data.
• Use POST request: add new data from/to your spaces.
• Use PUT request: replace data from/to your spaces.
• Use PATCH request: modify data with specific fields in your current space.
• Use Delete request: delete data from your spaces.

Please check the links above for more details on each.