Tasks API
The core building block in Skyvern
Tasks are the building block of Skyvern. They represent a single instruction (goal) to the browser to go do something using language models. Ex. “Go to alibaba and extract this information”
Request - Initiate a task
Request type: POST
Production:https://api.skyvern.com/api/v1/tasks/
Header
Body
Example Request (Apply for a job)
Response
Each task has an associated task_id
— a unique identifier you can use to look up information about any task.
Response Webhook - Task conclusion (POST)
If a webhook_callback_url
is specified within your task request, Skyvern will make a callback to your system letting you know that it has either finished, terminated or failed a task execution.
The following headers can be used to validate it’s an authentic Skyvern request.
Headers
Body
These parameters are returned in the body of the webhook_callback_url
.
Request - Task Details (GET)
You can use this API to poll for task status updates if you don’t want to wait for webhook callbacks.
Request type: GET
Production:api.skyvern.com/api/v1/tasks/{task_id}
Request - List Task Details (GET)
Request type: GET
Production:api.skyvern.com/api/v1/tasks/
Response - Task Details (GET)
Request - List Steps (GET)
Each task is made up of “steps” which are the individual actions Skyvern takes to complete the task. You can use this endpoint to get all the steps of the task.
Request type: GET
Production: https://api.skyvern.com/api/v1/tasks/{task_id}/steps
Response - List Steps (GET)
The response is a list of Step Object.
Step Object
Request - Cancel A Task (POST)
A task that’s in any of thsese states can be canceled: [“created”, “queued”, “running”]. This stops the execution of a task.
Request type: POST
Production: https://api.skyvern.com/api/v1/tasks/{task_id}/cancel