Skip to content
Project Hollowâ„¢Docs
Hollow AIHollowScriptAppsPlatformDocs
GuidesAPILanguage
Start hereOverviewAuthenticationConventions
Tasks APIOverviewCreate a taskWebhooksRouting rules
Lumen APIOverviewSend logsSend metricsCreate a monitorList monitorsMonitor status

Tasks API

Tasks API

Tasks

Programmatically submit work into Tasks via bearer API key authentication or inbound webhook URLs.

On this pageCreate taskInbound webhooksRouting rules
POST/v1/tasks

Create a task synchronously. text (or title) is required.

text, title
Task title string (up to 500 characters). Required.
description
Plain text description or notes. Optional.
listId, listName, list
Target list identifier or list name. Optional.
priority
Priority level: low, medium, high, or urgent. Optional.
labels
Array of tag string labels. Optional.
dueDate, dueTime
Date (YYYY-MM-DD) and time (HH:mm). Optional.
idempotencyKey
Unique request key (or pass via Idempotency-Key header). Optional.

Example Request

curl -X POST https://api.projecthollow.com/v1/tasks \
  -H "Authorization: Bearer hlw_sk_…" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Investigate checkout latency regression",
    "description": "p95 latency doubled after recent release",
    "list": "Engineering",
    "priority": "high",
    "labels": ["perf"],
    "idempotencyKey": "deploy-9876"
  }'
201 Created
Returns { "id": "task_123", "ticketKey": "ENG-42", "listId": "list_789" } (includes {"misrouted": true} if fallback list was used).
200 OK
Returns { "id": "task_123", "duplicate": true } for idempotent re-submissions.
POST/hook/{hookId}

Inbound webhook URL for integrating external services (such as GitHub, Zapier or custom scripts). Configure webhooks under Tasks → Integrations to map incoming JSON paths to task attributes.

https://api.projecthollow.com/hook/{hookId}?token=hook_…

The unguessable security token can be supplied via query parameter or X-Hollow-Token header.

sync mode
Default mode. Task is created immediately and returns HTTP 201 with task ID.
queue mode
Asynchronous staging for high-volume sources. Staged and created asynchronously, returning HTTP 202.

Routing rules

Define automated intake routing rules using HEL expression predicates evaluated against incoming task payloads.

Supported rule fields include title, description, priority, label, emaildomain and source.

title:billing OR title:invoice        → Route to "Finance" list
priority>=high emaildomain:acme.com   → Route to "VIP Support" list

Project Hollow

Hollow AIAppsPlatform

Documentation

OverviewGetting startedHollow StudioApp reference

Account

Sign inCreate accountEarly access

Legal

PrivacyTermsContact
© 2026 Project Hollow