How do I mock the Google Tasks API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:gtasks-style), and run stunt up. You get a local, stateful stand-in for Google Tasks API v1 — 11 routes over rest — with no remote account, no network, and no bills.

Is the Google Tasks API mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of Google Tasks API (routes, status codes, pagination, webhooks), never real records.

← all adapters

gtasks-style

simulates Google Tasks API v1

restadapter v0.1.011 routes

verification

SDKverified with google-api-go-client v0.293.0· surface 11 · not implemented 3 · differs 2

use it

# add to stunt.yaml
services:
  gtasks:
    adapter: embedded:gtasks-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the Google Tasks API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of Google Tasks API. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real Google Tasks API v1 surface — the data is fake, the behavior is real.

backing stores

taskliststasks

api surface (11)

generated from the adapter manifest — exactly what boots, nothing more · covers 64% of the real API's 14 routes (derived from sdk google-api-go-client @ v0.293.0)

11 routes

GET/tasks/v1/users/@me/lists

POST/tasks/v1/users/@me/lists

GET/tasks/v1/lists

POST/tasks/v1/lists

POST/tasks/v1/lists/{tasklistId}/tasks/{taskId}/move

GET/tasks/v1/lists/{tasklistId}/tasks

POST/tasks/v1/lists/{tasklistId}/tasks

GET/tasks/v1/lists/{tasklistId}/tasks/{taskId}

PUT/tasks/v1/lists/{tasklistId}/tasks/{taskId}

PATCH/tasks/v1/lists/{tasklistId}/tasks/{taskId}

DELETE/tasks/v1/lists/{tasklistId}/tasks/{taskId}

SDK-verified behaviors (8)

✓Tasklists.List returns the seeded default list
✓Tasklists.Insert + Tasklists.List round-trip
✓Tasks.Insert + Tasks.Get round-trip fields
✓Tasks.Patch status=completed derives the completed stamp
✓Tasks.List ShowCompleted=false hides completed tasks
✓Tasks.Move Parent/Previous re-parents and repositions
✓Tasks.List MaxResults + PageToken walk pages
✓Tasks.Delete then Tasks.Get -> googleapi 404

Not implemented (3)

No task-list get, patch, or delete endpoints
No tasks.clear endpoint
showDeleted/showHidden/showAssigned list params unmodeled

Differs from the real API (2)

Responses omit the kind field (tasks#task, tasks#taskList); SDKs decode fine without it
tasks.insert ignores a client-sent status/completed (always needsAction); due is stored verbatim

full scorecard →

want more of the Google Tasks API surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.