pyawe
Python client library for the AWE (Advanced Workflow Engine) API.
Installation
pip install pyawe
Quick start
from pyawe import AweClient
client = AweClient(
api_url="http://localhost:8080",
auth_url="http://localhost:8081", # ullav-user-management service
)
client.login(email="user@example.com", password="secret")
# Workflows
workflows = client.workflows.list()
wf = client.workflows.create("Q1 Onboarding", is_template=False)
detail = client.workflows.get(wf.id) # WorkflowWithTasks
# Tasks
task = client.tasks.create("Review docs", workflow_id=wf.id, is_start=True)
client.tasks.update(task.id, status="In Progress")
mine = client.tasks.list_mine() # tasks assigned to me / my roles
# Jobs
job = client.jobs.create("Q1 Campaign")
client.jobs.clone_workflow(job.id, workflow_template_id)
# Automated tasks
client.task_scripts.upsert(
task.id,
script_type="python",
script_body="print('hello')",
timeout_secs=60,
)
runs = client.task_runs.list(task.id)
Example: list your tasks
Print every task assigned to the authenticated user, along with its status and the workflow (and job, if any) it belongs to:
import os
from pyawe import AweClient
client = AweClient(
api_url=os.environ["AWE_API_URL"],
auth_url=os.environ.get("AWE_AUTH_URL", os.environ["AWE_API_URL"]),
)
client.login(email=os.environ["AWE_EMAIL"], password=os.environ["AWE_PASSWORD"])
for twc in client.tasks.list_mine():
context = twc.workflow_name
if twc.job_name:
context = f"{twc.job_name} / {twc.workflow_name}"
print(f"[{twc.task.status}] {twc.task.name} ({context})")
A runnable version of this script is at examples/list_my_tasks.py.
Authentication
AweClient authenticates against the ullav-user-management service, which
issues the JWT accepted by the AWE server.
api_url— AWE server base URL (e.g.http://awe-server:8080)auth_url— auth service base URL (e.g.http://ullav-user-management:8081); omit if both services are behind the same proxy
Call client.login(email, password) before any other method. Tokens expire
according to the server's configuration; call login() again to refresh.
Resource clients
| Attribute | Resource |
|---|---|
client.workflows |
Workflow CRUD, merge, duplicate, duplicate-of, team |
client.tasks |
Task CRUD, mine, decide, rework |
client.task_links |
Link create/delete, next/previous tasks, data bindings |
client.task_ports |
Port spec CRUD, input/output values, workflow-wide ports |
client.task_scripts |
Automated task script upsert/delete |
client.task_secrets |
Task secret value set/clear |
client.task_runs |
Execution run history |
client.task_team_roles |
Team-role assignment |
client.jobs |
Job CRUD, clone workflow, team, workflow allocations |
client.projects |
Project CRUD |
client.execution_profiles |
Kubernetes execution profile CRUD |
client.loop_blocks |
Loop block CRUD |
client.task_history |
Task status transition history |
client.connections |
Reusable credential ("connection profile") CRUD, secret set, test, MCP tool listing |
client.work_items |
Reusable task template CRUD, ports/script/checks/branches, instantiate |
client.checkpoint_checks |
Checkpoint check CRUD, manual verify, script run |
client.scheduled_scripts |
Cron-scheduled script CRUD, trigger, run history |
client.ai_chat_sessions |
The authenticated user's own AI chat session/message history |
Removed in this version:
client.notes,client.note_folders, andclient.idea_boards— awe-server has dropped the Notes/Note Folders/Idea Boards HTTP surface entirely; that functionality now lives in a separate service (tack-server). This is a breaking change if you used any of them.
Error handling
from pyawe import AweAuthError, AweNotFoundError, AweValidationError
try:
wf = client.workflows.get("non-existent-id")
except AweNotFoundError:
print("not found")
except AweAuthError:
client.login(email, password) # token expired — re-authenticate
except AweValidationError as e:
print("bad request:", e)
| Exception | HTTP status |
|---|---|
AweAuthError |
401 / 403, or login() not called |
AweNotFoundError |
404 |
AweValidationError |
400 |
AweServerError |
5xx |
AweError |
base class |
Status values
Use the Status and ScheduleStatus enumerations or plain strings:
from pyawe import Status, ScheduleStatus
client.tasks.update(task_id, status=Status.IN_PROGRESS)
client.tasks.update(task_id, status="In Progress") # equivalent
Licence
MIT
Metadata
Release files for pyawe 26.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyawe-26.7.0.tar.gz | 77.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyawe-26.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 133.2 kB
Release files / pyawe-26.7.0.tar.gz
| Download URL | pyawe-26.7.0.tar.gz |
|---|---|
| Size | 77.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be3b9b30fd664fafd8ea10511cdd6324fe4bca1c8de46bbedc0bd63a7f8629b4
|
|
BLAKE2b-256 checksum How to use checksums |
98e4ace6db45de9fa659d6c10154047391e6b80e7088623cfec987e73413b080
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / pyawe-26.7.0-py3-none-any.whl
| Download URL | pyawe-26.7.0-py3-none-any.whl |
|---|---|
| Size | 55.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58fe289ff47c2726673a929d712c914549b9d705d9a9906f4ae3895ce89f7b57
|
|
BLAKE2b-256 checksum How to use checksums |
7f6a8cdb3e9fa6a001a0b456ee872f515a81080c637e087b1859b4fdc181c7bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for pyawe 26.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyawe-26.7.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.