Step by step
Start with the onboarding widget
Open Onboarding in the sidebar to see your saved setup progress and choose a useful next step. Start with the work you need, such as bringing in a resume or saving a role. A loading or unavailable progress indicator does not mean your saved work has disappeared.
Continue from saved work in chat
Ask: What have I already set up, and what could I do next? Your agent should read the connected account, saved resume and saved roles before describing progress. Continue those records instead of importing or saving them again. The current context tools do not expose the full onboarding-widget checklist, so an agent should leave that completion state unknown and direct you to Onboarding in the sidebar when needed.
Start with your pipeline
Hunt Pipeline holds the roles and companies you are considering. A saved role opens its own activity, documents, notes, tasks, interviews and people.
Choose one useful starting point
Open Onboarding in the sidebar for existing setup choices. Start with a resume, a specific opening or a target company; you can use JobHunt before completing the whole checklist. The Choose your first useful step and Continue unfinished setup guides explain how to begin and return.
Keep reusable work in Hunt Docs
A document package groups a resume with related documents. Keep a reusable master here; create a separate role draft when you want to tailor it.
Set up your identity
Hunt Profiles holds names, contact details and public links. Hunt Page is the separate page you can choose to publish. Creating a profile does not publish it.
Check your reusable resume
The setup checklist counts a reusable resume marked Ready to distribute. A tailored application copy does not complete that step, even if its application link was cleared. Keep and review a reusable master in Hunt Docs; making one Ready does not publish it or apply for a job.
What happens next
The browser and connected tools work with the same account and saved records.
The website has an overview page for each part of JobHunt: working from your assistant at https://jobhunt.app/product/agent, the web app at https://jobhunt.app/product/browser, Hunt Page at https://jobhunt.app/product/hunt-page, connecting an assistant at https://jobhunt.app/agents and building on JobHunt at https://jobhunt.app/developers. Those pages describe what JobHunt does; the guides here remain the step-by-step instructions. If an overview and a guide disagree, follow the guide and tell us through Contact support. Every page of the website carries the same menu at the top and the same list of pages at the foot, under Product, Agents, Developers, Resources and Legal; on a phone, open Menu. If you cannot find a page, the sitemap at https://jobhunt.app/sitemap lists them all, and the light or dark theme switch is at the foot of every page. To see what has changed, open the changelog at https://jobhunt.app/changelog, linked under Resources at the foot of every page: it lists each release that changed something you or your assistant can see, newest first, dated in US Pacific time. Open an entry for its own page: the summary, then what changed, who it is for, how to use it and where to find it when the entry has them, with the date, type and area beside it. Its footer has links to share it, to its place in the timeline, to related entries and to the earlier and later releases. An assistant or feed reader can follow the same list at https://jobhunt.app/changelog/feed.xml.
Troubleshooting
Missing work? Check which account is signed in and which Hunt is selected before creating another record.
Technical detailsAPI operations and permissions
These operation details and permissions come from the API contract.
READget connected account
Identify the JobHunt account connected by these credentials. The opaque account ID stays unchanged across renaming, reconnection and token refresh. This does not select or change a resume contact profile.
GET /api/v1/journey/get_connected_accountread:profile
READget job hunt context
Resume the job hunt using saved, confirmed preferences. Reads never create defaults. Ask the user to choose when choices are returned; setup can be skipped.
GET /api/v1/journey/get_job_hunt_contextread:profileread:campaignsread:documentsread:applications
READget job hunt view
Read the current owned hunt or an explicitly selected application, its role documents, screening drafts, PDF preparation state and user-reported submissions. Filters and pagination never change saved defaults. Supplied IDs are selection hints, not permissions. Document content is included only when document_id selects an owned master or a member of the selected application package. No read creates a job, document, submission or task. Unavailable tasks are not an empty list.
GET /api/v1/journey/get_job_hunt_viewread:profileread:campaignsread:documentsread:applications
READlist document packages
Read owned master document packages and their real version, sharing and usage counts. Follow has_more for packages and documents_have_more for members; package_id selects one exact package. Role copies remain in their application. No resume bodies are returned.
GET /api/v1/journey/list_document_packages_v2read:documents