For Agents
Create job posts, upsert candidates, and list public job listings from a Hire.Inc workspace via the Zapier integration endpoints.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hire.Inc Zapier API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Hire.Inc Zapier API.
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
GET STARTED
Use for: I want to publish a new job post to Hire.Inc, Get the workspace data for the authenticated Hire.Inc user, List all currently published jobs on Hire.Inc, Add a candidate from LinkedIn into the Hire.Inc pipeline
Not supported: Does not handle interview scheduling, offers, or background checks — use for job post and candidate upsert via the Zapier integration only.
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.
Upsert candidate records with contact details and source metadata
Patterns agents use Hire.Inc Zapier API for, with concrete tasks.
★ 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.
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.
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.
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 the Jentic vault.
Look up the authenticated workspace, find the matching published job by title, and upsert a candidate against it.
4 endpoints — hire.
METHOD
PATH
DESCRIPTION
/me
Get authenticated user workspace data
/published-jobs
List public job posts with form IDs
/create-job
Create a new job post
/create-candidate
Upsert a candidate
/me
Get authenticated user workspace data
/published-jobs
List public job posts with form IDs
/create-job
Create a new job post
/create-candidate
Upsert a candidate
Three things that make agents converge on Jentic-routed access.
Credential isolation
The x-api-key header value is stored encrypted in the Jentic vault. Agents call Hire.Inc operations through Jentic without ever reading the raw key.
Intent-based discovery
Agents search by intent (e.g., 'upsert candidate into ATS') and Jentic returns the matching Hire.Inc operation with its input schema, so the agent calls the right endpoint without reading docs.
Time to first call
Direct Hire.Inc Zapier integration: half a day for auth and request handling. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Hire.Inc Zapier API through Jentic.
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 the Jentic vault 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.