Skip to main content
This workflow updates the same pages an employer sees in the selected job’s Instructions tab. Requirements: an employer API token with instructions:read for reads and instructions:write for preview or mutations. The token owner must have access to the target job.

​
1. Inspect the job

The response identifies canonicalSource: "JOB_INSTRUCTION_SET", the page tree, folder inheritance, and the exact employer URL. Use only page IDs from this response.

​
2. Preview rich content

Save a TipTap doc node in page.json, then validate and render it without writing:
The response includes writesApplied: false. Review the rendered HTML before confirming a live mutation.

​
3. Create a page

The idempotency key makes a retry safe. Omit --confirm-live to preview the content and command summary without writing. Use --parent <root-page-id> to create one subpage beneath a root. A subpage cannot have children.

​
Import a DOCX file

The first run previews the converted structure. Embedded images appear as placeholders and no bytes are uploaded. After review, rerun with --confirm-live. The CLI uploads the images, inserts them in the TipTap page, creates the canonical job page, and reads it back.

​
4. Edit without overwriting another writer

Read the current page and retain its checksum:
Apply node patches with that checksum:
For a complete replacement, preview the new document first and then use both --confirm-replace and --confirm-live. A stale checksum returns a conflict; read the page again and reconcile the human’s changes. Rename, move, or archive pages with the corresponding page command. These operations also require --confirm-live; archive additionally requires --confirm-archive.

​
5. Verify worker-visible state

Open the returned employer URL when human visual verification is needed. CLI success already includes canonical readback, but only this job URL represents the worker instruction source—there is no separate publish command.