jobhunt.app/mcp

Restore a saved version

Return to saved content while keeping a history of the change.

Updated

Step by step

  1. Open the version history

    In the document editor, open Versions. Choose Show older checkpoints to reach earlier history, then select a version.

  2. Compare exact versions

    Ask your connected agent to compare two saved versions by their version IDs. It reads the exact immutable content, follows every chunk and verifies the complete checksums. Comparing does not restore anything. If several checkpoints match a date, choose the intended checkpoint. A null legacy revision means its old provenance is unknown.

  3. See a version's pages

    Ask "Show me my resume at the checkpoint Before the rewrite." Where your assistant shows JobHunt cards, it shows that version's pages without changing anything. A version keeps its words and contact details, not the design it was printed in, so it is shown in your current design. Page previews in the chat are rolling out with JobHunt's new assistant tools; until your assistant offers them, open the document on jobhunt.app.

  4. Confirm the restore

    Ask the agent to restore the exact version you selected. JobHunt checks the current document revision so a delayed action cannot silently replace newer work. The saved profile link and prepared PDFs are preserved separately.

What happens next

Restoring creates a new current revision. Saved history and prepared application files remain separate.

A saved version may contain captured profile details. Restoring document content does not change the profile currently linked to the document.

Troubleshooting

If the document changed, reload and compare before restoring. If the reply was lost, check the original request; do not assume nothing happened.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist document revisions

Read up to 30 saved versions from the shared website and chat history. Follow next_before_id while has_more to find older versions, including timestamp ties. Optional include_metadata returns account/document-bound names, dates, triggers and total without document bodies. expected_account_id fences a changed account. Pages are live history, not an immutable collection snapshot. A null revision means a legacy website checkpoint, not missing content. Select the user's exact version before restoring.

GET /api/v1/journey/list_document_revisions

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
READget document version file

Read the complete saved version manifest, including its captured account, document, version and content hash. This does not read today's content or linked profile. A null revision means legacy provenance is unknown. Use bound chunks for the full private JSON.

GET /api/v1/journey/get_document_version_file

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
READget document version file chunk

Read one bounded chunk of the selected immutable version file. Use the exact manifest hash and size for every chunk, verify chunk and whole-file hashes, and never substitute latest content after source removal, revocation or conflict. Saved metadata is historical evidence, not permission to infer a human or agent actor.

GET /api/v1/journey/get_document_version_file_chunk

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITErestore document snapshot

Restore the exact owned native snapshot without a bounded career-fact response projection. Returns a content-minimal recorded revision; read saved content with get_document_version_file. Uses the same restore_document_revision original, receipt namespace, current-revision check and explicit retry/closure. Preserves unknown provenance and current linked-profile choices; never restores or infers a profile link.

POST /api/v1/journey/restore_document_snapshot_v1

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →