HitApply Job Alerts API
The Job Alerts API from HitApply — 3 operation(s) for job alerts.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/hitapply-app:hitapply-app-job-alerts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Fast Job Alerts API
version: 0.1.0
tags:
- name: Job Alerts
paths:
/api/job-alerts:
get:
summary: List Job Alerts
description: 'The one live alert, plus anything archived.
`archived` is normally empty. It is non-empty only for users who held several alerts before
migration 012, and it exists so that collapsing them to one was not a silent discard — the UI
lists them read-only with a Restore button.'
operationId: list_job_alerts_api_job_alerts_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Job Alerts
post:
summary: Create Job Alert
operationId: create_job_alert_api_job_alerts_post
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/JobAlertBody'
required: true
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Job Alerts
/api/job-alerts/{alert_id}:
post:
summary: Update Job Alert
operationId: update_job_alert_api_job_alerts__alert_id__post
parameters:
- name: alert_id
in: path
required: true
schema:
type: string
title: Alert Id
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/JobAlertBody'
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Job Alerts
delete:
summary: Delete Job Alert
operationId: delete_job_alert_api_job_alerts__alert_id__delete
parameters:
- name: alert_id
in: path
required: true
schema:
type: string
title: Alert Id
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Job Alerts
/api/job-alerts/{alert_id}/restore:
post:
summary: Restore Job Alert
description: 'Swap an archived alert in for the live one.
Only reachable for users who had several alerts before migration 012. Archive-then-restore in
one transaction, in that order: the partial unique index allows exactly one live row, so
restoring first would abort.'
operationId: restore_job_alert_api_job_alerts__alert_id__restore_post
parameters:
- name: alert_id
in: path
required: true
schema:
type: string
title: Alert Id
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Job Alerts
components:
schemas:
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
JobAlertBody:
properties:
name:
type: string
title: Name
query_text:
anyOf:
- type: string
- type: 'null'
title: Query Text
locations:
anyOf:
- items:
type: string
type: array
- type: 'null'
title: Locations
levels:
anyOf:
- items:
type: string
type: array
- type: 'null'
title: Levels
areas:
anyOf:
- items:
type: string
type: array
- type: 'null'
title: Areas
active:
type: boolean
title: Active
default: true
type: object
required:
- name
title: JobAlertBody
description: 'An alert is a name, keywords, locations and an on/off switch. Nothing else.
Work type, sources, job types, minimum salary and posted-within were removed in the Discover
redesign. Pydantic ignores keys it does not declare, so a browser still running the old editor
keeps working and its retired values are simply not written — which is the point: the columns
survive in the table but nothing can set them again.'