jobhunt.app/mcp

Make your first API request

Start with a read, confirm the account, then choose a workflow.

Updated

Step by step

  1. Connect with scoped access

    Use OAuth or a scoped API key. To create a key, open Account settings and find the API keys section; the guide "Authentication and permissions" explains how to choose its permissions. Send the credential in the Authorization header, never in a URL or client-side bundle.

  2. Read the connected account

    Call get_connected_account. Use the returned account ID when an operation asks for account binding; an ID is not permission to act as another owner.

  3. Inspect the operation contract

    Choose an operation in the API reference. Read its input, output, scopes and availability before making a write.

Read the connected account · HTTP
curl "https://jobhunt.app/api/v1/journey/get_connected_account" \
  -H "Authorization: Bearer $JOB_HUNT_TOKEN"

What happens next

HTTP, MCP and CLI operate on the same saved workspace through the shared backend.

These guides are also published as structured data at https://jobhunt.app/support/catalog.json, and the operation contracts at https://jobhunt.app/support/contracts.json. After each website release, the published guide catalog and API reference are compared byte for byte with the released source, and the release check fails if either differs. A release is not complete until that check passes. JobHunt publishes its Terms, Privacy Policy, sitemap and llms.txt only at https://jobhunt.app. The API host, api.jobhunt.app, serves the API, OAuth and sign-in links; the old page addresses on it now redirect to the website, its robots.txt asks crawlers to stay out, and the pages it still shows ask search engines not to index them. API, OAuth and MCP responses are unchanged. If a bookmark or integration still points at a page on the API host, follow the redirect or use the jobhunt.app address. An agent that needs the product in one read can fetch https://jobhunt.app/llms.txt: what JobHunt is, what it costs, how to connect and where each guide is. Every guide page is also available as Markdown, either by adding .md to its address or by requesting the same address with the header Accept: text/markdown. Each guide shows the date its text last changed, and the same date is in the catalog as updated. The OpenAPI document at https://jobhunt.app/api/v1/openapi.json can be cached and loaded from a browser on any origin. Example request to an agent: "Read jobhunt.app/llms.txt and tell me what JobHunt costs and how I would connect you to it."

Troubleshooting

The published contract describes supported operations. Your deployment and connection determine which capabilities are enabled.

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_account

DECLARED PERMISSIONS

  • read:profile
View input, output and access requirements →
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_view

DECLARED PERMISSIONS

  • read:profile
  • read:campaigns
  • read:documents
  • read:applications
View input, output and access requirements →