Evisort

OpenAPI specification for Evisort API for integration with 3rd party services

Evisort Workflow API

authentication

Generate a new token

intake forms

Get an intake form for a workflow

intake forms field options

Get options for an intake form field

Set options for an intake form field

workflows

Get all published workflows

tickets

Get ticket participants by ticket id

Get ticket details

Update a ticket

Create a ticket

Move the ticket to the next stage

Move the ticket to completed status

activities

Get activities of an entity

ticket judgments

Approve, reject or reset ticket judgments

Changes the assignee of a review and returns a ticket judgment. The current_user and new_user both need to be specified. The current_user must be specified because a ticket judgment may have multiple approvals pending and the current user is used to resolve which approval will be changed. both current_user and new_user can be specified by id only, but also by name and email. If id is supplied name and email are ignored for user resolution. If the id is not supplied, both name and email must be supplied.

Reassign a jugment result to another user

ticket documents

Create a new version of the document and mark some judgment results as signed

Upload a document with signatures

Get versions of a ticket document

Create and return a new version of ticket document

Upload a new version of ticket document

Get version of a ticket document

Returns the data for a ticket document version

Get the version data as a file

Default

Prod Workflow API

Production

Sandbox

API tokens are used to authenticate requests to Evisort APIs. When calling an API endpoint, you must supply a valid API token in the HTTP <code style="background-color:rgb(255, 255, 255);color:rgb(29, 29, 33);font-size:16px" class="slate-code">Authorization</code> header, with a valid token specified as the header value. You need to prefix the value with the <code style="background-color:rgb(255, 255, 255);color:rgb(29, 29, 33);font-size:16px" class="slate-code">Bearer</code> identifier, which is required for the authentication scheme that Evisort uses.

The Intake Forms section of the Workflow API allows users to access and retrieve various forms needed for intake processes.

The Intake Forms Field Options section provides users with access to a comprehensive list of field options for intake forms within the Workflow API. By exploring this section, users can customize and configure various field options to tailor their intake forms according to specific requirements and preferences. This functionality streamlines the process of collecting and organizing data through intake forms, enhancing the overall efficiency and user experience of the application.

The Tickets section of the Workflow API allows users to retrieve information about tickets. Users can access details such as ticket number, status, and any associated comments. This section provides essential data for tracking and managing tickets within the production environment.

The Activities section of the Workflow API allows users to retrieve a comprehensive list of all activities associated with a particular project. Users can use this section to track and monitor the progress of various tasks, view status updates.

The Ticket Documents section allows users to access various documents related to tickets. Users can view, download, and manage documents such as specifications, test results, and approval forms to track the progress of their projects. This section provides a centralized hub for all necessary documentation to support development and testing processes.

Sections