Platform API and access tokens

One API, three ways in

The scope works per project and per area. A token at Edit on Scripts and Read on Runs may update a script and list runs, and nothing else; the same token on a project it was not given answers as if the project did not exist. And whatever the scope says, the token is also limited by what its owner may do right now: if an admin lowers the owner’s access, every token of that person narrows at once.

Create an access token

1. 1
   Open Access tokens

   Open Settings → Access tokens and press New token.

2. 2
   Choose what it reaches

   Turn on each project it may reach, at Read, Edit or Delete — or open Customize areas to give each area (Scripts, Flows, Runs, Schedules…) its own level, or none.

3. 3
   Set when it expires

   Pick an expiry, or never. It is shown once: copy it now. The list then shows its first characters, when it was last used and how many calls it made.

Revoke a token from the same list: the next call with it is refused. Admins see every token of the workspace under All tokens.

Call it over HTTP

curl -H "Authorization: Bearer $WAISO_TOKEN" \
  "https://waiso.dev/api/projects/$PROJECT_ID/runs?status=failed&limit=5"

The same calls inside a script

In a script, waiso.api needs no token and no address: it acts as whoever started the run (the project owner for schedules and endpoints), and a call that names no project acts on the script’s own.

import waiso

def main():
    failed = waiso.api.runs.list(status="failed", limit=20)["items"]
    for run in failed:
        waiso.api.runs.cancel(run["id"]) if run["status"] == "running" else None
    return {"failed": len(failed)}