Small examples. Clearer ideas.

Static learning files. These JSON files contain synthetic data. Opening them does not call a live service, create records, or connect to an account. The field names illustrate design choices rather than any provider’s production contract.

A note with its context

Keep the source reference and review state separate from the original body.

{
  "example": true,
  "kind": "note",
  "note_id": "note_001",
  "title": "Ideas for the next field guide",
  "body": "Keep source material separate from personal commentary.",
  "source_ref": "manual-capture",
  "tags": [
    "writing",
    "ideas"
  ],
  "review_status": "reviewed"
}

Download the JSON file · Read the complete guide

A list of tasks

Use task identity, explicit status, date-only deadlines, and a version marker.

{
  "example": true,
  "list_id": "list_001",
  "title": "A thoughtful launch",
  "items": [
    {
      "task_id": "task_001",
      "title": "Review the guide structure",
      "status": "completed",
      "due_date": "2026-09-01",
      "version": 1
    },
    {
      "task_id": "task_002",
      "title": "Check the sample data",
      "status": "open",
      "due_date": "2026-09-04",
      "version": 1
    }
  ],
  "next_cursor": null
}

Download the JSON file · Read the complete guide

Timed and all-day events

Keep timed boundaries and date-only ranges visibly different. The all-day example uses an exclusive ending date.

{
  "example": true,
  "calendar_id": "calendar_001",
  "events": [
    {
      "event_id": "event_001",
      "title": "Editorial planning",
      "start": "2026-09-08T09:00:00-07:00",
      "end": "2026-09-08T09:30:00-07:00",
      "time_zone": "America/Los_Angeles"
    },
    {
      "event_id": "event_002",
      "title": "Research day",
      "start_date": "2026-09-09",
      "end_date_exclusive": "2026-09-10"
    }
  ]
}

Download the JSON file · Read the complete guide

A contact, not a subscription

The synthetic address identifies a sample contact field. It does not express newsletter permission.

{
  "example": true,
  "contact_id": "contact_001",
  "display_name": "Sample Contact",
  "email_addresses": [
    {
      "label": "work",
      "value": "[email protected]"
    }
  ],
  "source": "synthetic-example",
  "updated_at": "2026-09-01T12:00:00Z"
}

Download the JSON file · Read the complete guide

An email-to-note starting template

Use a small set of properties to record the source, capture date, and review state. Keep quoted material, your commentary, and proposed actions in separate sections. Validate any automated destination path and review sensitive correspondence before moving it into a shared vault.

Download the Markdown note template · Read the Obsidian list email guide

How to use these examples

Read the object structure first, then adapt the model to a small synthetic test collection. Do not replace the sample values with private account data in a public website. Before connecting a real provider, map every field to its documented meaning and decide which values your application actually needs.

The files are also directly readable resources on this website. They remain static files: there are no write methods, credentials, server-side validation, or synchronization services behind them.