Release NotesOpen Release Notes
Guide

API changelog

What each version of the API added, newest first, with a feed to follow it.

Follow the feed in any reader to hear of a new version. Every answer says the version it comes from in API-Version, and the API’s description says it as info.version, with this same list as x-changes.

/v1 only ever gains things: new requests, new optional fields, new error codes. A deprecation is announced here with its date, and a breaking change would be /v2. The exceptions so far are 1.8.0, which withdrew something no released app had sent, and 1.22.0, which closed the tag row to tokens that neither add nor read notes.

1.22.2

November 9, 2026

POST /v1/check-ins/places, on a name already remembered, and PATCH /v1/check-ins/places/{id}/check-ins refuse tags that would take the place, or any stay there, past 20, with invalid_request on tags and nothing written, as a tags field refuses a 21st tag. Before, the tags past 20 were silently left off. No other request changed.

1.22.1

November 9, 2026

Signing in: POST /oauth/register counts every new client against the one 200 an hour for everyone again, the Changelog app’s too, since 1.21.5’s separate count went by redirect URIs any client can claim. Each network’s own limits, an IPv6 /48’s among them, are unchanged. No request changed.

1.22.0

November 8, 2026

GET /v1/tags, the tag row, needs a token that adds or reads notes: notes:write or notes:read (notes:all comes with notes:write). A token for Upcoming or the activity log alone now gets scope_required, where before any token could read the recent tag names. Changelog and every app that adds notes are unchanged. This is the second exception to /v1 only gaining things, after 1.8.0.

1.21.7

November 8, 2026

POST /v1/check-ins keeps no spot or time in its 7-day Idempotency-Key receipt that the answer shows as the request sent (lat, lon, accuracy_m, arrived, left, at): a replay, which has the same request, fills them back in. So a stop at an ignored place, or one deleted since, leaves no spot or time behind. A replay answers exactly as before, and no request changed.

1.21.6

November 8, 2026

POST /v1/check-ins and PATCH /v1/check-ins/{id} answer a token with neither activity nor notes:all with empty tags and tag_names when a stop took them from a remembered place, as they already hid the place’s name. Tags the token sends in the PATCH show as sent. The stop keeps its tags, and a token that reads the log sees them. No request changed.

1.21.5

November 8, 2026

Signing in: an authorization code that comes back to POST /oauth/token after it was spent ends the connection it made, refresh token and all (RFC 6749, 4.1.2), as an app’s code already did. The OAuth requests count an IPv6 /48 as well as each /64, at three times the /64’s limit, and the Changelog app’s registrations count apart from the 200 new clients an hour for everyone. No request changed.

1.21.4

November 8, 2026

GET /v1/mail-log keeps an email’s subject only when its sender was proven to be the owner, as they already did its words: from another sender, or with failed authentication, spam or a virus, or to a replaced or stopped address, subject is empty, and another sender’s sender is its From line’s addresses alone. Anyone can write either. No request changed; the activity log never carried either.

1.21.3

November 8, 2026

POST /v1/uploads’s 200 files and 2 GB a UTC day are the account’s across the web, its tokens and, now, files attached to notes sent by email, since each photo is described and may be placed. No request or answer changed otherwise.

1.21.2

November 8, 2026

Signing in: POST /oauth/register answers invalid_client_metadata for a client_name that reads as Changelog, Claude or ChatGPT unless every redirect is that client’s own (Changelog’s com.yourversionnumber.changelog scheme, claude.ai or claude.com, chatgpt.com or chat.openai.com) or loopback, since the approval page leads with the name. The approval page also says where Allow sends the answer, and for a website’s redirect Cancel links back with access_denied instead of going there. An app’s own scheme gets access_denied straight back, as before.

1.21.1

November 8, 2026

POST /v1/places/here’s 100 spots a UTC day are the account’s across its tokens and the web’s Here together, since each is a paid lookup, and its rate_limited message says so. No request or answer changed otherwise.

1.21.0

November 8, 2026

Tags are first-class. A tag has a name, as written, with spaces or emoji (“Road Trip”, “🚗 Lake”), and a key (“road-trip”) that matches every spelling; tags still lists keys and the new tag_names lists the names beside them. POST /v1/notes and PUT /v1/notes/{date}/{id} take tags, by name, besides the hashtags in the text. Upcoming dates take tags, several of them; the single tag keeps working and is deprecated, and its removal will be announced here with a date. Check-ins and remembered places carry tags: a new stop at a place gets the place’s, PATCH /v1/check-ins/{id} and the places routes take tags, a place that gains a tag answers how many check_ins it has, and PATCH /v1/check-ins/places/{id}/check-ins tags them for that count. GET /v1/check-ins takes tag. Every tag filter takes any spelling. GET /v1/tags/all says each tag’s name and counts its Upcoming dates and check-ins, and GET /v1/tags adds pinned_names and a name on each recent tag. The activity log adds checkin.tagged.

1.20.0

November 8, 2026

A remembered place can be ignored: PATCH or POST /v1/check-ins/places takes ignored, and each place says it. No new stop at an ignored place is kept: POST /v1/check-ins answers 200 with kept false. The stops already there are hidden, not deleted, from GET /v1/check-ins, each read of one and the activity log, and come back when it is unignored. GET /v1/check-ins/places/{id} counts the check-ins at a place, hidden or not, and DELETE /v1/check-ins/places/{id}/check-ins?count= deletes them for that count. The activity log adds checkin.ignored and checkin.unignored, with the place’s id, and a checkin.deleted with a place.

1.19.0

November 8, 2026

GET /v1/map/pins takes q and tag as GET /v1/search does, and keeps only the pins of the notes with every word and the tag, so an app can show what a search finds on its own map. Left out, every pin comes, as before. Each pin says its note’s written_at, so the notes of a day can be put in the order they were written.

1.18.2

November 6, 2026

The description links two new pages: the guide in one file for agents, at /guide/api/llms.txt, and this list as a changelog with a feed, at /guide/api/changelog/. No request or answer changed.

1.18.1

November 6, 2026

The API description groups its requests with tags, links the guide, and can be fetched from a page in a browser, so tools that show it can load it. No request or answer changes.

1.18.0

November 6, 2026

Check-ins, the places you stop. POST /v1/check-ins sends a stop as a phone is told of it, and a later report of the same stay fills it in. GET /v1/check-ins lists them newest first with their spots and the names they show, and back-to-back stops at one place read as one. PATCH and DELETE /v1/check-ins/{id} name or delete a whole stay, and DELETE /v1/check-ins?confirm=all deletes them all. GET, POST, PATCH and DELETE /v1/check-ins/places keep the names you remember. GET /v1/activity has a new kind, checkin, whose label is the one place a row holds your own words, and never a spot. It takes no new scope.

1.17.2

November 5, 2026

A file’s address takes a number of up to six digits. Since numbers no longer come round (1.17.1), a note that has had many files added and removed can pass the old limit of three, which would have read as not_found.

1.17.1

November 5, 2026

A file’s number never comes round again. 1.17.0 let a later file take the number a removed last file left, so a transcript still being made for the old one could land on the new one. Two writers racing a removal could also give two files one number; now the later write reads the note again.

1.17.0

November 5, 2026

Taking one file off a note. DELETE /v1/notes/{date}/{id}/media/{n} removes it with its small copy, transcript and description, with media:write on a note this token wrote, and notes:all as well on any other. The other files keep their numbers. A note with no words can’t lose its last file (text_required). A note’s activity row of kind note.files can now say removed rather than added.

1.16.0

November 5, 2026

Writing as the web does. POST /v1/notes takes markup: "rich", for a note whose words hold rich-text marks. PUT and DELETE /v1/notes/{date}/{id}/place set, change or remove where a note was, on a note this token wrote, or any note with notes:all. PUT and DELETE /v1/days/{date}/place set or remove a day’s own place, with notes:all. The day’s weather follows each of these, and a new note with a place on an earlier day, and never fails the write.

1.15.0

November 5, 2026

Reading the archive. A new scope, notes:read, stands alone: it reads every note and what is made from them, and writes nothing. GET /v1/notes, GET /v1/notes/{date}/{id} and its media open to it, reaching every note. New with notes:read or notes:all: GET /v1/days (the timeline), GET /v1/days/{date}, GET /v1/search, GET /v1/on-this-day, GET /v1/releases, GET /v1/releases/{v}, GET /v1/tags/all, GET /v1/map/pins, GET /v1/badges and GET /v1/mail-log. notes:write alone still reads only what its token wrote.

1.14.0

November 5, 2026

The complete note. A note now says its tags, markup, parts (its words cut into strings, links and tags), place, no_place, edited_at, tz, late, author, client, from and attachments. Each of its media says its transcript, description and whether a transcript is writing. include=urls on GET /v1/notes and GET /v1/notes/{date}/{id} puts each file’s ten-minute address in the answer. A page of GET /v1/notes stops at about a megabyte, so it may hold fewer than limit notes: follow next until it is null.

1.13.0

November 1, 2026

GET /v1/me says lived, the weeks and days lived (both from 1), as Release Notes’ Today page and morning email set them (“Week 2,826 — Day 19,779”), for today and for each of its days. Changelog’s widget shows it.

1.12.0

November 1, 2026

GET /v1/me says supporting_member: whether the account gets what Supporting Members of the Weekly Thing get, as Release Notes last looked (every nine days, and at a web sign-in). Changelog reads it to offer its other app icons.

1.11.0

October 30, 2026

notes:all reaches the rest: a token with it deletes any note in the account (with its files, and an emailed note’s email, as the web’s delete does) and adds files to any note (with media:write). Without notes:all, nothing changes.

1.10.0

October 30, 2026

Every note: a token with the new notes:all scope (only beside notes:write, chosen by the owner) reads any note in the account, whatever channel wrote it, lists them all by day, fetches their files, and changes their words with PUT and append, from the revision it read. Delete and adding files stay on the notes it wrote. A note now says where it came from as source (email, web, api, an agent or an import) and whether this token wrote it as mine, and GET /v1/notes takes mine=true for this token’s alone. Without notes:all, nothing changes. Fixed: an activity cursor outside the from/to days answers an empty page, not 503.

1.9.0

October 30, 2026

Reading back by day: GET /v1/notes?from=&to= lists the notes this token wrote on those days, oldest first, a page at a time, up to 31 days a request (wider is range_too_wide). A note now lists its files as media (number, kind, type, name, size and its small copy), and GET /v1/notes/{date}/{id}/media/{n} gives a ten-minute address for one, or its small copy with ?size=thumb. GET /v1/activity takes the same from and to, days in the account’s time zone.

1.8.0

October 30, 2026

Moments withdrawn: POST /v1/notes no longer takes the moment that 1.6.0 added, and refuses it as a field it doesn’t have (invalid_request, with field moment). No released app sent one, and no note kept one. A note’s read and its note.added row no longer carry it. An app that starts a note from something picked, a workout, a song or who was there, writes it into the words, with its photos as uploads and its spot as place.

1.7.1

October 30, 2026

Tags in any script: a hashtag whose letters are not Latin is a tag of its own letters, lowercased (#東京 is 東京, #Москва is москва), on a note sent through /v1 as anywhere, and PUT /v1/tags/pinned takes them. Every tag that worked before is spelled as it was.

1.7.0

October 30, 2026

Odd bodies: POST /v1/notes reads a form (application/x-www-form-urlencoded, as a Shortcut’s Form body sends it) as its text, date and written_at, when those are its only fields and text is one; any other form is still the words, and a multipart or media body is refused. A body may be 256 KB, room for the longest note with every character escaped. A note’s words lose control characters other than tab and newline, as from every channel, and a JSON body holding a lone surrogate escape is refused. A note’s place is kept as sent, its shape checked.

1.6.0

October 30, 2026

Moments: a new note can carry a moment, what an app picked for it (a workout, a song or podcast, steps, a feeling, an event, people, a reflection prompt) as typed values beside its words. GET /v1/notes/{date}/{id} returns it as kept, and the note.added activity row names its kinds, never its words.

1.5.0

October 30, 2026

The contract says what answers do: POST /v1/uploads and POST /v1/places/here take no Idempotency-Key, since neither keeps a receipt (a retry asks again); RateLimit headers come on a write that counts, not on a replay; and Accept: text/plain gives text, a line for each thing a list holds. Accept is read in full, so text/plain wins only where it outranks application/json. A token’s 404 and 405 answers say today’s version too, and a body naming another date or id than the path is invalid_request.

1.4.0

October 30, 2026

Which account and which token: GET /v1/me gives the account’s id, the same for every token of the account and never changing, and the token’s own id; each activity row a token writes from now names it by token_id. An Idempotency-Key now holds for the account: the same key sent through another of its tokens gets the first answer, and a different request under it is idempotency_mismatch.

1.3.0

October 29, 2026

Signing in: an app can get its token with OAuth (the authorization code with PKCE, for the resource /v1, with its own https or reverse-DNS callback), choosing among notes:write, media:write, upcoming and activity; the owner names the token, ticks its scopes and picks its expiry, and the answer is that token, with no refresh. The app can sign out at /oauth/revoke as well as DELETE /v1/token.

1.2.0

October 29, 2026

Files and places: with the media:write scope, a signed form for each photo, recording or PDF, and files on a new note or added to one this token wrote; and a new note’s place, from the city search or from Here, which names a device’s spot and the businesses near it.

1.1.0

October 29, 2026

Upcoming, with the upcoming scope: list the dates ahead, add, change and remove up to 50 at once (all or nothing, with a dry run), remove one, and read the reminders each morning carries for up to 31 days ahead, with when the email is due.

1.0.0

October 29, 2026

The first version: who the token is and the days ahead, text notes, tags and pinned tags, and the activity log.

A hobby by Jamie Thingelstad, free with the Weekly Thing. From Your Version Number.