100Hires API

What authentication does the 100Hires API use?

The 100Hires API uses an API key passed in the Authorization header. When you call it through Jentic, the key is stored encrypted in the Jentic credential vault and injected at execution time, so the secret never enters the agent's prompt or logs.

Can I assign a candidate to a specific pipeline stage with the 100Hires API?

Yes. Call GET /jobs/stages to retrieve the configured workflow stages and their integer stage_id values, then pass the chosen stage_id in the body of POST /candidates/assign-job alongside candidate_alias and job_alias. If stage_id is omitted the candidate lands in the default stage for that job.

How many endpoints does the 100Hires API expose?

Four: POST /candidates/create, POST /candidates/assign-job, GET /jobs, and GET /jobs/stages. They cover candidate creation, candidate-to-job assignment, listing open jobs, and listing pipeline stages - the minimum surface needed to wire 100Hires into an external sourcing or intake flow.

How do I create a candidate and place them in a job opening through Jentic?

Run pip install jentic, then search for 'create a candidate in 100Hires' to load createCandidate, execute it with first_name, last_name, email, and phone, capture the returned alias, and then call assignCandidateToJob with that candidate_alias and the target job_alias from GET /jobs.

Are there rate limits on the 100Hires API?

The OpenAPI specification does not declare explicit rate limits. The endpoints live under the /zapier base path, which is intended for integration traffic, so design your agent to back off on 429 responses and to batch candidate creation rather than firing per-row requests from a sourcing list.

Can the 100Hires API list candidates that already exist in the workspace?

No. The current spec only exposes candidate creation and job assignment - there is no GET endpoint for candidates. If your agent needs to deduplicate, store the alias returned by POST /candidates/create at write time and key off that, or maintain an external index of candidates the agent has already pushed.

Can I limit what my agent is allowed to do with the 100Hires API?

Yes. Because you run Jentic One yourself, your own rules decide which 100Hires operations and credentials the agent can use. You can allow read-only calls like GET /jobs and GET /jobs/stages so the agent only lists openings and inspects pipeline stages, while leaving out POST /candidates/create and POST /candidates/assign-job unless you explicitly permit them. Since 100Hires names its targets in the request body rather than the URL path, only the operations you pick are exposed to the agent.