Executions API

View execution history and results for a watch.

Naming during the transition

URLs still address watches as tasks (/api/v1/tasks/{task_id}/executions). The rename to webwhen is a later phase.

Overview

Base URL: https://api.webwhen.ai/api/v1/tasks/{task_id}/executions

Supports both authenticated and unauthenticated access (for public watches).

Endpoints

Get execution history

Get every execution for a specific watch. Returns a bare JSON array (no pagination wrapper).

Endpoint: GET /api/v1/tasks/{task_id}/executions

Query parameters:

Parameter	Type	Description
limit	integer	Max results to return (default: 100)

Response: 200 OK

[
  {
    "id": "770e8400-e29b-41d4-a716-446655440000",
    "task_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "success",
    "started_at": "2025-01-15T09:00:00Z",
    "completed_at": "2025-01-15T09:00:05Z",
    "result": {
      "evidence": "Search results confirm Apple announced iPhone 16 release...",
      "confidence": 95,
      "sources": ["https://apple.com/newsroom/..."]
    },
    "notification": "Apple has officially announced that the iPhone 16 will be released on September 20, 2025.",
    "grounding_sources": [
      {
        "uri": "https://www.apple.com/newsroom/2025/09/apple-announces-iphone-16/",
        "title": "Apple announces iPhone 16"
      }
    ],
    "error_message": null,
    "created_at": "2025-01-15T09:00:00Z"
  }
]

Examples:

# Get all executions (up to 100)
curl -X GET https://api.webwhen.ai/api/v1/tasks/550e8400.../executions \
  -H "Authorization: Bearer sk_..."

# Limit results
curl -X GET "https://api.webwhen.ai/api/v1/tasks/550e8400.../executions?limit=10" \
  -H "Authorization: Bearer sk_..."

Access control:

• Watch owner: full access
• Public watch: anyone can view executions (no auth required)
• Private watch, non-owner: 404

Execution object schema

Fields

Field	Type	Description
id	UUID	Unique execution identifier
task_id	UUID	Parent watch ID
status	enum	pending, running, success, retrying, failed, cancelled
started_at	timestamp	When execution started
completed_at	timestamp/null	When execution completed (null if still running)
result	object/null	Agent result with evidence, confidence, sources
notification	string/null	User-facing trigger message (null if condition not met)
grounding_sources	array/null	Source URLs backing the evidence
error_message	string/null	Error details if status is failed
created_at	timestamp	Execution creation time

Key difference: notification vs result

• notification: user-facing message, present only when the condition was met. This is what gets delivered via email or webhook.
• result: internal agent result with evidence and confidence. Present on every completed execution, whether the condition was met or not.

Execution statuses

pending

Initial state before execution starts.

running

Execution in progress (searching, evaluating the condition).

success

Execution completed successfully. Check the notification field to see if the condition was met.

retrying

Transient failure — retried automatically.

failed

Persistent or user-actionable failure. Check error_message for details.

cancelled

Execution was cancelled (for example, by a manual "Run now" that overrode a stuck execution).

Per-watch trigger feed

Filter executions to only those where the condition was met.

Endpoint: GET /api/v1/tasks/{task_id}/notifications

Query parameters:

Parameter	Type	Description
limit	integer	Max results to return (default: 100)

Response: 200 OK

Returns the same execution object array, filtered to only executions where notification IS NOT NULL.

[
  {
    "id": "770e8400-e29b-41d4-a716-446655440000",
    "task_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "success",
    "notification": "Apple has officially announced the iPhone 16 release date...",
    "grounding_sources": [],
    "started_at": "2025-01-15T09:00:00Z",
    "completed_at": "2025-01-15T09:00:05Z",
    "result": {},
    "error_message": null,
    "created_at": "2025-01-15T09:00:00Z"
  }
]

Same access-control rules as the executions endpoint.

Error responses

Not found

Status: 404 Not Found

{
  "detail": "Task not found"
}

Returned when the watch doesn't exist, or is private and the requester isn't the owner.

Next steps

• See the Notifications API for notification send history
• Check the Watches API for watch management
• Read the Error Handling guide