Queues
A queue represents a manual process and works like a queue
The following parameters might be required as part of the request URL:
Organization ID. Visible in Settings.
Queue ID. Found in the URL when inside a queue.
A queue is denoted as an object with the following fields:
active_users
: A list with the names of the users currently assigned to at least one pending task in the queue.created_at
: The queue's creation timestamp.id
: The queue's identifier.n_tasks
: The number of pending tasks in the queue, waiting to be completed.name
: The queue title.data
: The queue's data configuration, which consists of a list of Block objects. This field is only included when explicitly fetching a queue by its identifier.
Here is an example of how a queue object looks like:
List all queues
GET
https://api.humanlambdas.com/orgs/$ORGANIZATION_ID/queues
Lists all queues that exist within the organization.
Path Parameters
ORGANIZATION_ID
integer
The ID of your organization.
Headers
Authorization
string
Token $API_KEY
or visit the Introduction page for more details.
Sample request:
Get queue by ID
GET
https://api.humanlambdas.com/orgs/$ORGANIZATION_ID/queues/$QUEUE_ID
Retrieves a queue's information given a queue identifier.
Path Parameters
ORGANIZATION_ID
string
The ID of your organization.
QUEUE_ID
string
The ID of your queue.
Headers
Authorization
string
Token $API_KEY
or visit the Introduction page for more details.
Flush a queue
PUT
https://api.humanlambdas.com/orgs/$ORGANIZATION_ID/queues/$QUEUE_ID/flush
Deletes all tasks in a queue whose status is not completed. Successful requests will result in an empty task queue.
Path Parameters
ORGANIZATION_ID
integer
The ID of your organization.
QUEUE_ID
integer
The ID of your queue.
Headers
Authorization
string
Token API_KEY
visit the Introduction page for more details).
Last updated