Programmatically submit work into Tasks via bearer API key authentication or inbound webhook URLs.
Create a task synchronously. text (or title) is required.
low, medium, high, or urgent. Optional.YYYY-MM-DD) and time (HH:mm). Optional.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"
}'{ "id": "task_123", "ticketKey": "ENG-42", "listId": "list_789" } (includes {"misrouted": true} if fallback list was used).{ "id": "task_123", "duplicate": true } for idempotent re-submissions.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.
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