[markdennis22]

Why?

The 2.17 spec for the tag, note, segment, subscription type and job status endpoints didn't match the API. The lists were missing query parameters, note ids were typed as integers, the note list described cursor paging where the API pages by number, and several error responses were missing. The Preview spec had the same problems, and the next version is cut from Preview, so it needs the same fixes.

How?

Corrects these endpoints and their schemas to match the API's current behaviour, and adds the OAuth scopes each endpoint accepts to its description. The same changes go into the Preview spec, keeping content that only applies to Preview, such as the {id} path parameter name.

Risks

The Preview SDKs are generated from this spec, so these changes affect generated Preview types:

Change	Could SDK code stop compiling?	Did that code work before?
listTags returns a new ListTagsResponse union of a tag list or a tag, instead of TagList	Yes, because the return type becomes a union	No. GET /tags?id= already returned a single tag
The id path parameter on createNote, retrieveNote and deleteNote becomes a string	Yes, where an integer was passed	No. Both ids are strings
NoteList.pages becomes PagesLink instead of CursorPages	Yes, if it reads pages.next as an object	No. The API sends a URL
SegmentList.pages goes	Yes, if it reads pages	No. The API never sends it
CreateNoteRequest.contact_id goes	Yes, where code sets it	No. The API ignores it and uses the contact id in the path
UntagCompanyRequestCompaniesItem.untag becomes a required boolean	Only for a payload without untag, which tags instead of untagging	—
New optional request fields on the tag requests, new query parameters on listTags, the two note lists, listSegments and retrieveSegment, and new 400 and 404 errors	No	—

Notes for reviewers

• fern check shows 0 errors. There are no new dangling refs and no operationId changes, and none of the changed Preview types is unknown.

_{Generated with Claude Code}