API Documentation

Use exact product_name, release_type, or release_status values from Filter Options. limit accepts 1–25 items, default 25.

• Five most recently modified items
• Up to ten shipped items

Illustrative data, not a live record. Dates are quarters or null; description HTML is sanitized at read time. The original description is unchanged.

{
  "data": [{
    "release_item_id": "11111111-1111-1111-1111-111111111111",
    "feature_name": "Example feature",
    "release_date": "Q4 2026",
    "release_type": "General availability",
    "release_status": "Shipped",
    "product_id": null,
    "product_name": "Power BI",
    "feature_description": "Example description.",
    "feature_description_html": "<p>Example description.</p>",
    "blog_title": null,
    "blog_url": null,
    "last_modified": "2026-10-19",
    "active": true
  }],
  "pagination": {
    "page": 1, "page_size": 1, "total_items": 1, "total_pages": 1,
    "has_next": false, "has_prev": false, "next_page": null, "prev_page": null
  },
  "links": {
    "self": "/api/releases?page=1&page_size=1",
    "first": "/api/releases?page=1&page_size=1",
    "last": "/api/releases?page=1&page_size=1",
    "next": null, "prev": null
  }
}

A single-item request returns the object inside data, without the collection envelope.

activity

Product/kind rows with event and distinct-feature counts.

transitions, target_changes

Daily status/type counts and the number of release-date change events.

upcoming, products

Current quarter counts and product choices.

filters, coverage

Resolved UTC window/query and retained-history coverage, always complete: false.

details

items, total, previous_url, next_url, and capped. Links target dashboard evidence.

visuals

Derived dashboard chart values and links.

Counts describe observed events, not delivery guarantees. Repeated transitions count separately; pipeline-only writes do not. Additions are first retained observations. Retention/import coverage is unverified. Planned quarters are a current snapshot, independent of the historical window.

[
  {
    "changed_columns": ["Release Status Planned -> Shipped"],
    "last_modified": "2026-10-19"
  },
  {
    "changed_columns": ["Roadmap Item Added"],
    "last_modified": "2026-09-01"
  }
]

{
  "total_items": 1,
  "days": [{
    "date": "2026-10-19", "count": 1,
    "items": [{
      "release_item_id": "11111111-1111-1111-1111-111111111111",
      "feature_name": "Example feature",
      "product_name": "Power BI",
      "release_type": "General availability",
      "release_status": "Shipped",
      "release_date": "Q4 2026",
      "last_modified": "2026-10-19",
      "active": true,
      "changed_columns": ["Release Status Planned -> Shipped"]
    }]
  }]
}

since=YYYY-MM-DD is a legacy inclusive UTC range, today through 90 days ago. It overrides days and cannot be combined with date. Historical filters include removals/restorations by default. Repeated same-day tracked-field events count separately; pipeline/blog-only writes are excluded.

The response adds since, through, total_events, total_features, and complete: true. In this mode, last_modified is the observed UTC temporal-event day. Recorded history began August 27, 2025.

visit=1 returns the full unfiltered 90-day event snapshot for browser-local highlights, not a server visitor record. It adds mode, complete, exact UTC cutoff, and window_start; items carry stable content-event identities. Filters are display-only. It cannot combine with date, since, or event_date. Above 10,000 events, it returns 503 with complete: false rather than a partial acknowledgement.

Daily permalinks use event_date=YYYY-MM-DD for all tracked UTC events on one day, including repeated edits and removals. This ignores days, cannot combine with another temporal mode, and adds mode: "events", event_date, total_events, and total_features without reading or advancing visit state. Legacy date selection remains unchanged. All three event modes are private/no-store.

POST /api/subscribe requires email. Filter arrays are optional; cadence is daily or weekly (default weekly). Requests are limited to five per hour.

{
  "email": "user@example.com",
  "products": ["Power BI"],
  "types": ["General availability"],
  "statuses": ["Shipped"],
  "cadence": "weekly"
}

A successful request returns a generic confirmation to protect subscription privacy; it does not confirm delivery or reveal whether an address is subscribed.

• GET /api/verify-email?token=TOKEN returns JSON; GET /verify-email?token=TOKEN opens the verification page.
• GET /unsubscribe?token=TOKEN opens the unsubscribe page.
• POST /api/send-preferences-link accepts an email address; GET/POST /api/preferences?token=TOKEN manages preferences.
• POST/DELETE /api/watch manages feature watches; /watch/RELEASE_ID opens the watch page.

Use the verification/preferences links sent by email; never share their tokens.