jobhunt.app/mcp

Record an application you submitted

Save what you actually sent, then keep the next step separate.

Updated

Step by step

  1. Report what happened

    Ask your agent: “I applied yesterday using the earlier resume PDF. Record it and remind me to follow up next Friday.” Identify the saved application and actual calendar date. Clarify the date or time zone if needed. A plan to apply, downloaded file or opened employer link is not a submission.

  2. Choose the files you used

    Select the exact saved package or application attachments, including older choices. If you do not know which files or destination you used, keep them unknown. You do not need to recreate historical documents, and current answer drafts are not evidence of submitted answers.

  3. Review the saved report

    JobHunt records your report, not an employer receipt or delivery confirmation. Recording can move an earlier-stage application to Applied; ask to keep the current stage if that is your intent. Later stages are preserved.

  4. Correct an existing report

    Identify the report to correct and supply the corrected facts. A correction adds a replacement linked to the earlier report; the original evidence stays in history. It does not delete the past report or send another application.

  5. Recover only unfinished work

    If the reply was interrupted, check the original request before retrying. Keep the same request identity for that retry. Closing a retry does not undo a recorded application. A requested follow-up task is saved separately: if the report succeeds but the task fails, recover the task without recording the submission again. A missing task permission does not erase a saved submission; restore that permission before resuming the unfinished task.

What happens next

Your application history records the date and evidence you supplied, with corrections preserved.

Troubleshooting

Unknown files and destinations stay unknown. JobHunt does not submit employer forms or send a follow-up message. See “Tailor documents for a role” for final material review and “Keep track of your next steps” for saved reminders.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget submission options

Read this application’s current stage, public employer link, saved PDF packages and owned attachments for an explicit submission review. These are choices, never inferred evidence. An employer-link click has no submission effect. Use prepared_before_id or external_before_id with the returned next cursor to read older choices.

GET /api/v1/journey/get_submission_options

DECLARED PERMISSIONS

  • read:applications
  • read:documents
View input, output and access requirements →
READget application submissions

Read up to 50 reported submissions and appended corrections for one owned application. Files require read:documents. before_id pages older history. Unknown documents and destinations remain explicitly unknown. These are user reports, not delivery receipts from an employer.

GET /api/v1/journey/get_application_submissions

DECLARED PERMISSIONS

  • read:applications
View input, output and access requirements →
WRITErecord submission

Record an application only after the user explicitly says they submitted it. user_confirmed must be true. This is a user_report, never employer-verified evidence. Record the actual date and optional public HTTPS destination. Select the exact prepared package or owned application attachments they used; if unknown, document_knowledge=unknown with no file references. Never infer the newest file. The report and optional move to Applied are atomic; later stages stay in place. Set move_to_applied=false to keep the current stage. Corrections append a new report using supersedes_id. Reuse request_id after interruption. No employer send or billing action occurs.

POST /api/v1/journey/record_submission

DECLARED PERMISSIONS

  • write:applications
View input, output and access requirements →
READget job hunt operation

Read a saved JobHunt operation after a retry or lost response. Use the original operation ID or request ID and operation name; optionally bind the expected payload hash. Full profile-photo receipts expose original non-secret photo artifact IDs in data.related_ids. Payload-hash-bound application-document customization checks also expose the exact created role-document ID. Payload-hash-bound submission-report checks expose the exact reported submission ID. Other receipt namespaces do not expose related IDs. Never repeat an uncertain create with a new key.

GET /api/v1/journey/get_job_hunt_operation

DECLARED PERMISSIONS

  • read:profile
  • read:applications
  • read:documents
  • read:campaigns
  • read:tasks
  • read:contacts
  • read:interviews
  • read:companies
  • read:calendar
View input, output and access requirements →
WRITEclose submission original

Explicitly close retry of one complete user-reported submission original. Supply the captured account, full original input and confirm_close=true. Uses the same owner and receipt lock as record_submission. An unused request is fenced; recorded or expired evidence is historical, never an undo. No application, report, document or pipeline stage is read, created or changed. Read/write application grants suffice because closure does not inspect document contents. Keep the original until exact closure is verified. No employer send or publication occurs.

POST /api/v1/journey/close_submission_original_v1

DECLARED PERMISSIONS

  • read:applications
  • write:applications
View input, output and access requirements →
WRITEcreate task

Create one requested follow-up, standalone or linked to an owned application/search. Reuse request_id after a lost response and check get_job_hunt_operation. Calendar dates stay on their supplied day; timed due_at values require a timezone. Use recurrence for explicit repeating requests; weekly/custom_days use Monday=0 through Sunday=6, and optional due_time uses the account timezone. Do not invent a time or turn a recurring request into a one-off. Linking a job/search also requires its read grant. Records a task only: no email, invitation, calendar sync or scheduled outreach.

POST /api/v1/journey/create_task_v2

DECLARED PERMISSIONS

  • write:tasks
View input, output and access requirements →
READget task

Read one owned task and its current revision before editing. Application-linked tasks also require read:applications. Recurring tasks include their schedule and date-specific completion fingerprint; stage templates use application records.

GET /api/v1/journey/get_task_v2

DECLARED PERMISSIONS

  • read:tasks
View input, output and access requirements →