canonical: https://jentic.com/apis/hireinc.com/hireinc

# Hire.Inc Zapier API

Hire.Inc is an applicant tracking system designed for high-performing recruiting teams that lean on AI for sourcing and screening. The Zapier integration API exposes a small surface for workspace lookup, listing published job posts, creating new jobs, and upserting candidates. It is intended as the connector layer that drops Hire.Inc events and records into broader recruiting workflows.

## For AI agents

Create job posts, upsert candidates, and list public job listings from a Hire.Inc workspace via the Zapier integration endpoints.

## Scope

Does not handle interview scheduling, offers, or background checks - use for job post and candidate upsert via the Zapier integration only.

## Capabilities

- Look up the authenticated workspace and the user's role inside Hire.Inc
- List public job posts with their associated form IDs for embedding or syndication
- Create new job posts inside a Hire.Inc workspace via a single POST
- Upsert candidate records with contact details and source metadata

## Use cases

### Sync Job Posts From an HRIS

Recruiting ops teams keep job listings in sync between their HRIS and Hire.Inc by calling the create-job endpoint each time a requisition is approved. The Zapier API returns the form ID so downstream systems can embed the application form. This avoids double-entry and keeps the careers page in lockstep with internal job openings.

Example prompt: Create a job post titled 'Senior Backend Engineer' in the Hire.Inc workspace and return the published form ID.

### Inbound Candidate Capture

Sourcing tools and chrome extensions push candidate records into Hire.Inc via the create-candidate endpoint, which upserts based on email or external id. Recruiters see new candidates appear in their Hire.Inc pipeline automatically. Time from sourcing tool to ATS drops from manual minutes to API seconds.

Example prompt: Upsert a candidate with email jane@example.com and source 'LinkedIn' for the requisition created earlier.

### Embedded Careers Page

Marketing or careers-page maintainers use the published-jobs endpoint to render a live list of open roles with the correct form IDs. The job list and form IDs come from one GET so there is no risk of stale links. Pages refresh automatically when recruiters open or close roles in Hire.Inc.

Example prompt: Fetch all published Hire.Inc jobs and return a list of {title, form_id} pairs ordered by post date.

### Agent-Driven Recruiting Workflow

An AI sourcing agent connected via Jentic identifies a strong candidate, checks the Hire.Inc workspace for an open requisition, and upserts the candidate against the matching job. The agent never sees the API key directly because Jentic injects it at execution time. Setup takes minutes once the workspace credential is stored in your Jentic One instance.

Example prompt: Look up the authenticated workspace, find the matching published job by title, and upsert a candidate against it.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get authenticated user workspace data |
| GET | `/published-jobs` | List public job posts with form IDs |
| POST | `/create-job` | Create a new job post |
| POST | `/create-candidate` | Upsert a candidate |

## Key resources

- **Workspace** — Authenticated workspace context and user metadata
- **Jobs** — Public job posts and create-job operation
- **Candidates** — Upsert candidate records into the pipeline

## Why Jentic

- **Setup:** Wiring the Hire.Inc Zapier API by hand means sending an x-api-key header and posting job and candidate bodies to its AWS App Runner host. Through Jentic you install once, import the Hire.Inc Zapier API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Hire.Inc Zapier API carries the job and candidate data in the request body rather than the URL path, so scoping stays at the operation level: limit the agent to the operations it needs, such as reading published jobs or upserting a candidate. You choose that set, so creating a job is only available if you include it.
- **Credential handling:** Your Hire.Inc x-api-key is stored once, encrypted, by your own Jentic One instance and injected into the x-api-key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upsert a candidate into the ATS', and Jentic returns the matching Hire.Inc operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Ashby API** — Ashby is a deeper ATS with broader API surface for hiring teams
- **Workable API** — Workable provides a broader public ATS API for jobs and candidates
- **Lever API** — Lever offers full ATS coverage including stages, feedback, and offers

## FAQ

### What authentication does the Hire.Inc Zapier API use?

The Hire.Inc Zapier API uses an API key passed in the x-api-key header on every request. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at call time, so agents never handle the secret directly.

### Can I create candidates with the Hire.Inc Zapier API?

Yes. POST /create-candidate upserts a candidate record using email or external id as the dedupe key. Existing candidates are updated in place; new candidates are inserted into the workspace pipeline.

### What are the rate limits for the Hire.Inc Zapier API?

Hire.Inc does not publish public rate limits for the Zapier integration surface. Treat it as a low-volume connector - keep request volume to a few per second per workspace and back off on 429 responses.

### How do I publish a new job through Jentic?

Search Jentic for 'create hire.inc job post', load the POST /create-job operation, and execute with the job title, description, and workspace fields. Run pip install jentic and use the async SearchRequest, LoadRequest, ExecutionRequest pattern to wire the call.

### Does the Hire.Inc API support pulling published jobs for a careers page?

Yes. GET /published-jobs returns the public job posts along with their Hire.Inc form IDs, which can be embedded on an external careers page. Refresh on a schedule to pick up role open or close events.

### Can I limit what my agent is allowed to do with the Hire.Inc Zapier API?

Yes. Because you run Jentic One yourself, you decide which of the Hire.Inc operations your agent can call, so you can allow it to list published jobs (GET /published-jobs) or upsert candidates (POST /create-candidate) while withholding job creation (POST /create-job) or workspace lookup (GET /me). Since the job and candidate data travels in the request body rather than the URL, scoping happens at the operation level: an operation you leave out is simply unavailable to the agent. Your own rules also govern the stored x-api-key, which is injected at call time so the agent never handles it directly.