What's new across the GetItDone API, SDK, webhooks, and MCP server — and what is planned.
POST /v1/webhook-endpoints/{endpoint_id}/replay-failed takes a required `since` instant. It now rejects timestamps written without seconds — `2026-07-24T00:00Z` returns a validation problem where it used to be accepted. Send `2026-07-24T00:00:00Z` (or the fractional-second form, `2026-07-24T00:00:00.000Z`) instead.
Read more →The TypeScript SDK is now published: npm install @nowgetitdone/sdk. The package ships compiled ESM + CJS bundles with type declarations; the open-source mirror on GitHub tracks every release.
Read more →The official GetItDone TypeScript SDK is now developed in the open. It is a thin, typed wrapper over the /v1 REST surface with retries, automatic idempotency keys on consequential POSTs, cursor pagination helpers, and typed problem errors.
Read more →Register HTTPS endpoints and receive signed events when tasks change. Payloads are signed with the Standard Webhooks scheme so you can verify authenticity from the raw request bytes.
Read more →The public GetItDone REST API is live at /v1. Authenticate with a gid_ API key over Bearer auth and manage organizations, projects, tasks, the daily plan, and attachments.
Read more →Things we have said we would build, and where each one actually stands. Status describes the code, not the intention — nothing here says “shipped” until it is in production.
Not started. The integrations grid lists Google Calendar as planned, and that is all it is today — there is no calendar code in the product, one-way or two-way. It is not in the current build cycle.
The capture pipeline ships today for screenshots. Voice is built but gated on a transcription provider being configured, so it is off in production: the API answers "unavailable" and the UI offers typing instead of pretending to transcribe.