Call an app's webhook
const url = 'http://127.0.0.1:7700/hook/example/start';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"title":"From a webhook"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url http://127.0.0.1:7700/hook/example/start \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "title": "From a webhook" }'Runs the webhook an app registered with the webhook trigger (or box.onWebhook). The JSON body
and the headers go to the app, which usually starts a task. The response is the new task, or
{"ok": true} when the app returns nothing. This route has no /api form. From outside the box it
needs a device token like any other route.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The app’s name.
Example
exampleThe webhook’s name, letters, digits, _ and -.
Example
startRequest Body
Section titled “Request Body”object
Example
{ "title": "From a webhook"}Responses
Section titled “Responses”What the app returned.
object
A short name for people.
What the worker should do. For the fake worker, one command per line.
A folder in BOX_HOME/workspaces. The task works on its own copy of it.
droid is Droid with Claude. fake runs scripted steps with no model, for tests.
Tool names the task may call through its broker, such as wallet.pay.
Hosts the task’s network may reach: example.com (any port), example.com:8080 (one port) or *.example.com (subdomains).
Spending above this, in US cents, pauses the task for an OK. Default Settings defaultBudgetCents, 0 unless changed.
Who started it, for the log and the portal: api, schedule, asi1, jira:BOX-12.
Personal: the first real folder the task works on a copy of.
Personal: every real folder the task works on.
queued created, not started. running the worker is working. waiting paused until an
approval is answered. done finished; its changes are part of the workspace. failed stopped with
an error; its changes are not applied. undone removed; its changes are gone and other tasks keep
theirs.
The Linux user the task runs as, box-<id>.
Finished tasks whose changes this task saw when it started, newest first.
Tool spending plus model cost, in US cents. Not rounded.
The latest step
Why it failed. A worker that exited with an error ends with its own last error line: worker exited with 1: Error: ....
Personal, for a task on real folders: done and waiting for the owner, kept, stopped by a conflict, or undone.
object
Example
{ "workspace": "home", "worker": "droid", "tools": [], "hosts": [], "source": "api", "id": "t3k9x2a1b2", "state": "queued", "user": "box-t3k9x2a1b2", "review": "pending"}The app’s handler failed or the body was not JSON.
object
What went wrong
Example generated
{ "error": "example"}GurtOS is open source under the Apache License 2.0.Source code on GitHub.