Every accessible note changed after the cursor.
Pages carry snapshots when asked; without one a client that cannot bridge the gap fetches individually.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”A nextPageToken or nextSyncToken from an earlier call. Absent lists
every note: a full sync.
Notes per page: 100 when absent, at most 500. A page is also cut short at 4 MiB of ciphertext, though never below one note.
Include snapshots on this page. Defaults to true on a full sync. An initial
sync passes true on every page so later pages need no per-note fetch.
Responses
Section titled “Responses”Changed notes
Delta-sync page.
object
One note’s state within a delta-sync response.
object
Active members including the owner; 1 means unshared. Keeps the sidebar’s shared marker truthful without a members round trip.
Base64 encrypted metadata digest. Absent for tombstones.
The caller’s role on this note. revoked accompanies deleted.
Base64 encrypted Yjs snapshot. Absent for tombstones and on incremental
sync pages (fetch the note when version cannot reach snapshotVersion).
Last write time, for the tree’s date column and sort.
Base64 encrypted updates newer than the snapshot, in order.
Base64 content key wrapped to the caller. Absent for tombstones and for legacy notes still encrypted under the master key.
Pass as pageToken for the next page. Empty on the last page of this listing.
On the last page only. Pass it as pageToken later to list what changed
since. It is the account’s sync watermark and does not expire.
Example
{ "changes": [ { "role": "owner" } ]}The request is malformed
RFC 9457 problem details payload.
object
Explanation specific to this occurrence, written to help correct the request.
The invalid members of the request. Present on a validation problem.
One invalid member of a request, located by a JSON Pointer (RFC 6901).
object
What is wrong with it.
JSON Pointer to the member within the request body. Empty for the whole body.
HTTP status code.
Short summary of the problem type. For about:blank, the status phrase.
Problem type URI, which resolves to its documentation. Absent means about:blank.
Examplegenerated
{ "detail": "example", "errors": [ { "detail": "example", "pointer": "example" } ], "status": 1, "title": "example", "type": "example"}No valid session token
RFC 9457 problem details payload.
object
Explanation specific to this occurrence, written to help correct the request.
The invalid members of the request. Present on a validation problem.
One invalid member of a request, located by a JSON Pointer (RFC 6901).
object
What is wrong with it.
JSON Pointer to the member within the request body. Empty for the whole body.
HTTP status code.
Short summary of the problem type. For about:blank, the status phrase.
Problem type URI, which resolves to its documentation. Absent means about:blank.
Examplegenerated
{ "detail": "example", "errors": [ { "detail": "example", "pointer": "example" } ], "status": 1, "title": "example", "type": "example"}Headers
Section titled “Headers”The Bearer challenge (RFC 6750).
Too many requests
RFC 9457 problem details payload.
object
Explanation specific to this occurrence, written to help correct the request.
The invalid members of the request. Present on a validation problem.
One invalid member of a request, located by a JSON Pointer (RFC 6901).
object
What is wrong with it.
JSON Pointer to the member within the request body. Empty for the whole body.
HTTP status code.
Short summary of the problem type. For about:blank, the status phrase.
Problem type URI, which resolves to its documentation. Absent means about:blank.
Examplegenerated
{ "detail": "example", "errors": [ { "detail": "example", "pointer": "example" } ], "status": 1, "title": "example", "type": "example"}Headers
Section titled “Headers”Seconds to wait. Sent when the limit knows when it lifts.
The service failed
RFC 9457 problem details payload.
object
Explanation specific to this occurrence, written to help correct the request.
The invalid members of the request. Present on a validation problem.
One invalid member of a request, located by a JSON Pointer (RFC 6901).
object
What is wrong with it.
JSON Pointer to the member within the request body. Empty for the whole body.
HTTP status code.
Short summary of the problem type. For about:blank, the status phrase.
Problem type URI, which resolves to its documentation. Absent means about:blank.
Examplegenerated
{ "detail": "example", "errors": [ { "detail": "example", "pointer": "example" } ], "status": 1, "title": "example", "type": "example"}The service is at capacity
RFC 9457 problem details payload.
object
Explanation specific to this occurrence, written to help correct the request.
The invalid members of the request. Present on a validation problem.
One invalid member of a request, located by a JSON Pointer (RFC 6901).
object
What is wrong with it.
JSON Pointer to the member within the request body. Empty for the whole body.
HTTP status code.
Short summary of the problem type. For about:blank, the status phrase.
Problem type URI, which resolves to its documentation. Absent means about:blank.
Examplegenerated
{ "detail": "example", "errors": [ { "detail": "example", "pointer": "example" } ], "status": 1, "title": "example", "type": "example"}