API endpoints
The base URL of the APIs is: /onelistserver/api/datasync
e.g. https://iqx.onelistapprovals.com/onelistserver/api/datasync/synctasks. These APIs can be viewed and tested using Swagger which is accessible via /onelistserver/swagger
. The full API signatures can also be found here.
Authentication
The source system must use the API key that is assigned to it by OneList to interact with the data sync APIs. The API key should be specified in the X-API-Key
header in every HTTP request. Below is an example of a HTTP POST request:
POST https://iqx.onelistapprovals.com/onelistserver/api/datasync/SyncTasks HTTP/1.1
X-API-Key: TQUIteYnrxqHkBvh2{
Content-Type: application/json
{"activeTasks":[….]}
The key terms used in the APIs
Term | Description |
---|---|
TaskType | This constant value must match the Task Adapter Task Type in OneList configured to handle the request. |
TaskId | This is the source system unique identifier of the task. The value must be consistent in the whole lifecycle of the task. |
BusinessObjId | This is source system identifier of the business object associated with the task. For example,
|
ActionId | This is the source system workflow action identifier. |
Assignee | The user id of the source system user who is assigned to the task as the approver / agent. |
Delegator | The user id of the source system user who is delegating the task. |
Delegate | The user id of the source system user who is the task delegate. |
HashValue | The string value can be used to compare if the task has been changed. The following can be used as the hash value for a task:
|
The key APIs for integration
Note: only the key parameters of each API are listed here, please view the full API signature via /onelistserver/swagger
.
Function | Description |
---|---|
| This API synchronizes OneList tasks with source workflow tasks.
|
| This API returns the list of source system user who has outstanding task but is not yet mapped to an OneList user. The source system should call the SyncUsers API to map these users before they can view their tasks in OneList. |
| This API returns the profile of active OneList users. It can be used to detect user changes in the source system.
|
| This API adds or updates OneList user account with the source system user information. It also creates the user mapping between the OneList user account and the source system user account.
|
| This API synchronizes OneList task attachment cache with source system files.
|
| This API returns the list of user task actions. The source system should perform the requested task action in the workflow.
|
| Source system calls this API to notifiy OneList of the requested task action.
|
What needs to integrate with OneList
An adapter will generally implement these integration processes: