API reference
Edits API
Sessions, snapshots, staged changesets, apply and undo: the contract behind the MCP server.
A small, stable contract for making reviewed changes to a business's information. A caller opens a session on a business it may edit, reads a snapshot, stages a changeset, and applies or reverts it. Every applied change lands in the console's Change History with Undo. The Keystone MCP server calls this surface and nothing else.
14 endpoints in 6 groups.
Business claims
Businesses
Businesses change log
Businesses changesets
Changesets
- GET
/api/v1/edits/changesets/{changeset_id}A changeset and its items - POST
/api/v1/edits/changesets/{changeset_id}/applyApply a staged changeset's ticked items, each only if its value has not moved - POST
/api/v1/edits/changesets/{changeset_id}/discardDrop a staged changeset - PATCH
/api/v1/edits/changesets/{changeset_id}/items/{item_id}Tick or untick one staged item - POST
/api/v1/edits/changesets/{changeset_id}/revertUndo an applied changeset where nothing changed since
Sessions
- POST
/api/v1/edits/sessionsOpen an edit session for one business the caller holds - GET
/api/v1/edits/sessions/{session_id}An edit session, and whether it is still open - POST
/api/v1/edits/sessions/{session_id}/changesetsCheck proposed changes and stage them as one changeset - GET
/api/v1/edits/sessions/{session_id}/records/{entity}/{record_id}One record in full, with its version (the profile is record_id 'profile') - GET
/api/v1/edits/sessions/{session_id}/snapshotEverything the session's business has: the profile in full, other records trimmed