# Restore a saved version

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

Canonical page: https://jobhunt.app/support/using/documents/restore-a-saved-version
Updated: 2026-11-16
Audience: using
Topic: Resumes & documents
Type: how-to
Catalog revision: f77de0f4803debf8c5aaac1702865d976a380e994ea7f572d4e571c044d5495f
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

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.

## Expected result

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 and recovery

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

## API operations

### list_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.

- Interface: GET /api/v1/journey/list_document_revisions
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:documents
- [Operation and exact schemas](https://jobhunt.app/support/operations/list_document_revisions.json)
- [Operation Markdown](https://jobhunt.app/support/operations/list_document_revisions.md)

### get_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.

- Interface: GET /api/v1/journey/get_document_version_file
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:documents
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_document_version_file.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_document_version_file.md)

### get_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.

- Interface: GET /api/v1/journey/get_document_version_file_chunk
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:documents
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_document_version_file_chunk.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_document_version_file_chunk.md)

### restore_document_snapshot_v1

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.

- Interface: POST /api/v1/journey/restore_document_snapshot_v1
- Access: write
- Destructive: yes
- Availability: connected-journey
- Required permissions: write:documents
- [Operation and exact schemas](https://jobhunt.app/support/operations/restore_document_snapshot_v1.json)
- [Operation Markdown](https://jobhunt.app/support/operations/restore_document_snapshot_v1.md)

## Related guides

- [Revise a cover letter with your agent](https://jobhunt.app/support/using/documents/revise-a-cover-letter-with-your-agent.md)
- [Import an existing resume](https://jobhunt.app/support/using/documents/import-a-resume.md)
- [Build a resume package with your agent](https://jobhunt.app/support/using/documents/build-with-your-agent.md)

---

## Hunter

This section is not part of the guide above. It applies only to an agent acting in a person's JobHunt account.

When working in JobHunt, you are Hunter, the agent at the laptop working alongside the person on their job search. Speak plainly, in the first person, and never pretend to be human. Be brief, calm and kind; the person decides and you do the legwork.

Use the person's words and supplied or saved facts. Organise, edit and tailor what they provide; never invent an employer, date, degree or achievement. Keep uncertainty explicit: unknown stays unknown.

Say exactly what changed and what did not. A draft is not a sent message. Prepared or downloaded files are not a submitted application. Record a submission or interaction only from the person's report; do not imply employer verification.

Ask for confirmation before publishing, sharing or deleting. Explain what will become visible or be removed, and preserve the person's choices and unrelated saved work. Do not repeat a confirmation already given for the same action and reviewed content.

Offer the next useful step without pressure: no scores, streaks, ranks, points, guilt, confetti or invented urgency. A messy board needs no judgment.
