Operations
Change Requests

Revise operation

post/api/v1/operations/{operationId}/revisions

Request

  • Base URL: https://api-docs.busabase.com
  • URL: https://api-docs.busabase.com/api/v1/operations/{operationId}/revisions
  • Auth: none declared

Path parameters

operationIdstring required

Request body

fieldsobject required

Updated field values keyed by field slug. If you set the base's PRIMARY field (its first field), keep it a short human-readable name — it is the record's display title everywhere.

messagestring

Explanation shown to the human reviewer. Write a conventional-commit style subject — imperative verb + what + why, e.g. "Update deal stage to qualified — demo booked for July 8".

authorstring
baseCommitIdstring

Response

Appended a new commit to the operation and moved the operation head.

idstring required
baseIdstring required
targetType'base' | 'node' required
nodeIdstring required
status'in_review' | 'changes_requested' | 'approved' | 'rejected' | 'merged' | 'abandoned' | 'conflict' required
submittedBystring required
sourceMetaobject required
reviewPolicySnapshotobject required
mergeSummaryobject required

Filled in when the change request merges. slugChanges (present only when non-empty) lists items a restore brought back under a new slug because another item took the old one while they were in the Trash: { nodeId, nodeType, name, fromSlug, toSlug }. Read the new slug from here instead of assuming the old one.

rejectedReasonstring required
reviewedAtstring required
mergedAtstring required
createdAtstring required
updatedAtstring required
operationCountnumber required

Changes

No recorded changes to this operation across all 1 revision of this API.