Astris HR API · v1

Build with Astris HR

The matching, parsing, retention, and skills-inference capabilities that power astrishr.com — available as a clean REST API so your ATS, caseworker system, or careers page can embed them. Eight endpoints, two webhook events, ATS-shaped payload adapters, self-serve keys.

Quick choice — what are you building?

Endpoints at a glance

POST/api/v1/parse/resume
POST/api/v1/parse/jd
POST/api/v1/match
POST/api/v1/retention-forecast
POST/api/v1/skills-infer
POST/api/v1/jobs/sync
POST/api/v1/jobs/bulk-sync
POST/api/v1/candidates/sync
GET/api/v1/jobs
GET/api/v1/candidates
GET/api/v1/matches

Full reference: per-endpoint docs.

Hello world

New here? Apply for an API key first — we review each request and approved applicants get an auto-issued live key emailed to them. Then:

# Parse a job description from text
curl -X POST https://www.astrishr.com/api/v1/parse/jd \
  -H "Authorization: Bearer ahr_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"text":"Apartment Maintenance Tech — EPA 608 required, $26-32/hr, Newark NJ. Spanish a plus."}'

Response:

{
  "parsed": {
    "title": "Apartment Maintenance Technician",
    "workMode": "onsite",
    "requiredCertifications": ["EPA Section 608"],
    "preferredSkills": ["Spanish language"],
    "payType": "hourly",
    "hourlyMinUsd": 26,
    "hourlyMaxUsd": 32,
    "city": "Newark",
    "state": "NJ",
    "detectedSourceLanguage": "en"
  },
  "usedVision": false,
  "parseError": null
}

Apply for an API key

Fill out the application at /auth/signup/developer: pick the employer or organization you're building for from the dropdown and tell us in a sentence what you're integrating. A super admin reviews each request — usually within a business day.

On approval we email you an auto-issued live API key scoped to the tenant you picked (employer → parse, match, retention, skills, jobs; organization → parse, match, retention, skills, candidates). The plaintext token is shown once — copy it into your secret manager immediately.

After approval, sign in at /auth/signin and the key is waiting at /developers/keys (you can also rotate or issue additional keys there).

Stability and changelog

v1 is stable as of June 2026. Breaking changes will go through a deprecation window with email notice to every key's createdBy contact. See /developers/changelog.