Changelog

Markdown

The API version is the date of the newest entry, now 2026-09-30.2. Every change so far only added to the surface, so the REST paths stay /v1. How versioning works.

  1. 2026-09-30.2

    A documented contract

    • added

      Every operation documents its response: a JSON schema for the 200 or 201 body, with a description on every field, in the OpenAPI document and the reference.

    • added

      Request and response examples for every operation, and the error codes each one can return.

    • added

      since and stability (stable or beta) on every operation; the nine operations of 2026-09-30 start as beta.

    • added

      The OpenAPI document lists upload_media_batch (POST /v1/media/upload-batch) and names the shared shapes (Fee, Schedule, Arrival and the rest) as components.

      upload_media_batch

    • fixed

      stale_editor (the expectedUpdatedAt guard) answers 409, like the other conflicts, instead of 400.

      update_chapterset_chapter_introsave_sales_page_draft

  2. 2026-09-30

    Structured facts, link health, readiness checks

  3. 2026-09-29

    Publishing a live guide's changes, planning places worldwide

    • added

      The opt-in publish scope: a key with it may publish a live guide's changes when the creator asks.

      get_publish_statuspublish_changes

    • added

      Place types for stays and transport, food and parking places, and places linked straight to spots (spotKeys).

      create_facilityupdate_facilitylist_facilities

    • added

      Routes worldwide: activity, grade scales and the route line from GPX or KML.

      create_routeupdate_route

    • changed

      Publishing is decided at the function for every credential, so a key sent straight to the backend meets the same checks.

  4. 2026-09-23

    Chapter front matter

    • changed

      set_chapter_intro takes cover overrides, bullet lists and dressed chapter rows and collection cards.

      set_chapter_intro

  5. 2026-09-17

    First release

    • added

      46 operations, each a REST endpoint under /v1 and an MCP tool: account, guides, properties, spots, chapters, routes, places, photos, the sales page draft and the profile. Photo uploads over REST, the OpenAPI document, and the authoring guide as a SKILL.md.