Overview
The reference tells you what an endpoint accepts. These guides show you how the pieces fit together once your integration is real: the webhooks that tell you when work changes, the bundles that move whole apps around, the memory your agents keep, and the SDK that wraps it all in TypeScript.
MEMORY INTELLIGENCE EXECUTION
────── ──────────── ─────────
Projects Agents Automations
Tasks Agent knowledge Webhooks out
Media Long-term memory Bundles in/out
Long-term memory 15+ frontier models Published apps
│ │ │
└────────────────────┴──────────────────────┘
│
one workspace, one token
What each guide covers
| Guide | Answers |
|---|---|
| Webhooks | How do I get told when something changes? |
| Bundles & App Kits | How do I move a whole app or workspace somewhere else? |
| TypeScript SDK | How do I call this from TypeScript without hand-rolling fetch? |
| SDK Cookbook | What do production integration patterns look like? |
| Long-Term Memory | Where does an agent's memory physically live, and can I edit it? |
| Autonomous Agents | How do agents run work without a human in the loop? |
Webhook events
Six event types fire outbound:
| Event | Fires when |
|---|---|
task.due |
A task reaches its due date |
task.assigned |
A task is assigned to someone |
comment.created |
A comment is added |
project.created |
A project is created |
project.assigned |
A project is assigned |
project.joined |
Someone joins a project |
Deliveries are signed with X-Taskade-Signature: sha256=<hex>, an HMAC-SHA256 over the raw body. Delivery is fail-closed: if the signature cannot be produced, the delivery is skipped rather than sent unsigned.
The payload is the bare packet with no event-name envelope. Receivers must infer the event from the payload shape, so branch on the fields you actually need rather than on a type discriminator that is not there.
