Developers
Build on JobHunt. MCP server, REST API, CLI and webhooks.
Four ways into one job search account, with OAuth and scoped access. The MCP tools are built on the API's operations.
- OAuth with PKCE
- Read and write scopes
- One set of operations underneath
First request
Example$ curl "https:/ / jobhunt.app/ api/ v1/ journey/ get_connected_account" \
-H "Authorization: Bearer $JOB_HUNT_TOKEN"
200 · fictional account
{
"id": "example-account",
"name": "Morgan Ellis",
"email": "morgan@example.invalid",
"nickname": "Morgan"
}- Webhook event
- application.status_changed
- Sent to
- Your endpoint
- Delivery
- On record
Four surfaces
Pick the one that fits the job.
The HTTP API, the CLI and the website use the same registered operations. The MCP server offers fewer, larger tools built on them.
MCP server
Remote MCP with OAuth. Call tools/list for the tools enabled on your connection.
Server address
MCP setuphttps://jobhunt.app/mcpREST API
JSON over HTTPS. Your credential goes in the Authorization header, never in a URL.
A first read
API referenceGET /api/v1/journey/get_connected_accountCLI
A prerelease, built from source. There is no public npm package yet.
After building
CLI setupnode cli/dist/jobhunt.js account connected --jsonWebhooks
Workspace events, sent to a destination you reviewed, with delivery records.
An event name
Webhook eventsapplication.status_changed
Access
Scoped, and tied to one account.
The credential decides the account. An account ID in a request is an integrity check.
OAuth with discovery
Discovery starts at /.well-known/oauth-protected-resource. The authorization code flow uses PKCE.
Read and write are distinct
Each operation declares its scopes. Request only what a workflow needs, such as
read:applications write:tasksScoped API keys
A key carries its own scopes and belongs to one account.
Retries that do not duplicate
Keep a write’s request ID. After a lost reply, check the original before resending.
Addresses
Where to point it.
https://jobhunt.app/mcphttps://jobhunt.app/api/v1/openapi.json- Transport
- Streamable HTTP
- Sign-in
- OAuth 2.1 + PKCE
Where to start
One read, then the reference.
The contract lists supported operations. Your connection decides which are enabled.
First
Get scoped access
Use OAuth, or a scoped API key from your account.
Then
Read the account
Call get_connected_account and confirm it is the one you expect.
Next
Choose an operation
Read its input, output and scopes before making a write.
Every release is posted on X. Follow JobHunt on X (opens in a new tab)
7-day free trial
Start with one read.
Create an account, authorize a client and call get_connected_account.