GraphQL Changelog – June 29
June 30th, 2026 by ReadMe API
Pipes and Databases now expose their structure snapshots through the API, so callers can fetch the latest snapshot or a specific version.
Added:
- The field
snapshotis available onPipeandTable(both implement theRepointerface). It returns a point-in-timeRepoSnapshotof the Repo versioned structure.versionId: ID(optional) — the snapshot version to fetch. When omitted, the latest snapshot is returned.- Returns a
RepoSnapshotwithid,versionId,signedUrl(temporary download URL, null while pending),uploadedAt, andcreatedAt. Null when the Repo has no matching snapshot.
- The field
snapshotsis available onPipeandTable. It returns the list of allRepoSnapshots of the Repo, most recent first (empty list when there are none).
Notes:
- Both fields are gated by the
enable_repo_snapshot_createfeature flag (the same flag that controls thecreateRepoSnapshotmutation). While the flag is off for an organization, the fields are not present in the schema for that caller. - The field requires Repo admin permission (
manage). A caller without it receives aPERMISSION_DENIEDerror and anullsnapshot. - A
versionIdthat does not belong to the queried Pipe/Database resolves tonull; it does not leak snapshots across Repos.

