Get merge status for a draft revision
Runs the three-way merge between the draft and the current live version without applying it. Conflicts are granular: each conflicting field gets its own key, and rules conflict individually (rules.<ruleId>, plus rules.order for competing reorders). Pass the returned liveVersion as expectedLiveVersion when rebasing. Also reports rebaseRequired so callers can detect ahead of time whether the publish endpoint will block until the draft is rebased.
Authorizations
If using Bearer auth, pass the Secret Key as the token:
Response
Successful response
The current live version the merge was computed against. Echo this back as expectedLiveVersion when rebasing.
The draft's last-modified timestamp at merge time. Echo this back as expectedDraftDateUpdated when rebasing to guard against concurrent draft edits.
True when publishing this draft is blocked until it is rebased — either the merge has conflicts, or the draft is behind live (or its approval went stale) while the organization enforces rebase-before-publish. When true with no conflicts, callers with bypass-approval permission can still publish with mergeNow: true; others must rebase first.

