Crelate Recruiting CRM API

Name: Crelate Recruiting CRM API API
Brand: Crelate Recruiting CRM API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting AtsapiKey42 EndpointsREST

For Agents

Read and write Crelate's recruiting data — contacts, companies, jobs, pipelines, placements, tasks, notes, and activities — to keep an applicant tracking system in sync with another tool or to drive recruiter workflows from an agent.

Connect the Crelate Recruiting CRM API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crelate Recruiting CRM 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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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.

Capabilities

What an agent can do with Crelate Recruiting CRM API API.

Search and filter the contacts list and create or update individual contact records by ID

Create company records, fetch them by ID, and update or remove them as account data changes

Open new jobs, update their state, and pull a job's detail by ID for downstream syncing

Move candidates through hiring pipelines by reading and writing pipeline records on jobs

GET STARTED

Start building with Crelate Recruiting CRM API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Crelate Recruiting CRM API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Crelate Recruiting CRM API, keeping it validated and agent-ready. Crelate is a recruiting CRM and applicant tracking system used by staffing agencies and corporate recruiters to manage the full hiring lifecycle, from sourcing through placement. The API exposes the core recruiting objects — contacts, companies, jobs, candidates, pipelines, placements, tasks, notes, activities — through a consistent REST surface backed by an X-API-Key header, so an integration can keep an external system synchronised with the Crelate workspace.

Use Cases

Patterns agents use Crelate Recruiting CRM API API for, with concrete tasks.

★ Sync a sourcing tool with Crelate

Push candidates surfaced by an external sourcing or LinkedIn-extraction tool into Crelate as contacts, attaching them to the right company and job. POST /contacts creates the record, POST /companies (or a search-then-link flow) keeps the account graph clean, and POST /activities lets the integration record where the candidate came from for later reporting.

For each new sourced profile, call POST /contacts with the candidate fields, then POST /activities tying the activity to the new contactId with type 'Sourced'.

Pipeline progression from a chat assistant

Let recruiters update Crelate from a chat or voice assistant rather than the desktop UI by mapping commands like 'move Jane to Onsite' to a PUT against the relevant pipeline record. The agent looks up the contact and the job, finds the pipeline entry, and patches its stage in place without leaving the conversation.

Look up the candidate via GET /contacts with a name filter, fetch the matching pipeline via GET /pipelines/{pipelineId}, then PUT /pipelines/{pipelineId} with the new stage.

Placement and reporting export

Pull placements, jobs, and contacts into a data warehouse for billing or commission reporting by paging through GET /placements, GET /jobs, and GET /contacts on a schedule. The integration maps Crelate IDs to the warehouse keys and writes back placement events as they close.

Run a daily job that pages GET /placements, GET /jobs, and GET /contacts since the last sync timestamp and writes the records into a Snowflake staging table.

Agent-driven recruiter copilot via Jentic

A Jentic-orchestrated agent can act as a recruiter copilot: a recruiter says 'log a screening with Sam and book a follow-up task' and the agent calls POST /notes and POST /tasks against the right contactId. Jentic handles the X-API-Key injection, so the recruiter does not paste credentials into the chat tool.

Through Jentic, run search('log a recruiter activity in Crelate'), load POST /notes, then POST /tasks, and execute both against the contactId returned from a prior GET /contacts query.

Key Endpoints

42 endpoints — jentic publishes the only available openapi specification for crelate recruiting crm api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/contacts

List contacts

POST

/contacts

Create a contact

POST

/jobs

Create a job

GET

/pipelines

List pipelines

PUT

/pipelines/{pipelineId}

Update a pipeline record

POST

/placements

Create a placement

POST

/notes

Create a note

POST

/activities

Create an activity

GET

/contacts

List contacts

POST

/contacts

Create a contact

POST

/jobs

Create a job

GET

/pipelines

List pipelines

PUT

/pipelines/{pipelineId}

Update a pipeline record

POST

/placements

Create a placement

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Crelate X-API-Key tokens are stored encrypted in the Jentic vault. Jentic adds the X-API-Key header on every outbound call to https://app.crelate.com/api/pub/v1, so the raw key never appears in the agent context, prompt, or logs.

Intent-based discovery

Agents search Jentic with intents like 'create a candidate in Crelate' or 'move a candidate to the next stage' and Jentic returns the matching POST /contacts or PUT /pipelines/{pipelineId} operation with its input schema.

Time to first call

Direct integration: 2 to 5 days to wire up the contact, company, job, and pipeline objects with consistent paging and error handling. Through Jentic: under an hour to discover and call the right operations across the 42-endpoint surface.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Greenhouse Harvest

Greenhouse's well-documented ATS API targeting in-house corporate recruiting teams.

Choose Greenhouse Harvest for corporate ATS integrations where the customer already runs Greenhouse; pick Crelate when the customer is a staffing or recruiting agency.

Alternative

Lever

Recruiting platform API covering candidates, opportunities, and stages.

Pick Lever when the customer is on Lever's platform; Crelate is the right fit for staffing agencies running Crelate as their CRM and ATS.

Complementary

BambooHR

Core HRIS API used to push hires from an ATS into employee records.

Use BambooHR alongside Crelate to convert a placement into an employee record once a hire is finalised.

FAQs

Specific to using Crelate Recruiting CRM API API through Jentic.

Why is there no official OpenAPI spec for Crelate Recruiting CRM API?

Crelate documents its API in its developer guide but does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crelate Recruiting CRM API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Crelate Recruiting CRM API use?

The API uses an X-API-Key header on every request. The key is created in the Crelate application settings and is per workspace. Through Jentic the key is stored encrypted in the vault and applied at execution time so it never enters the agent's prompt or logs.

Can I create candidates in Crelate through the API?

Yes. POST /contacts creates a contact record that represents a candidate. You can then attach them to jobs via the pipeline endpoints and log activity with POST /activities, POST /notes, or POST /tasks.

How do I move a candidate to the next pipeline stage with the Crelate API?

Pipeline membership is exposed as records under /pipelines. Fetch the relevant pipeline record with GET /pipelines/{pipelineId}, change the stage value, and PUT /pipelines/{pipelineId} to persist the move.

What are the rate limits for the Crelate Recruiting CRM API?

The published OpenAPI spec does not declare rate limits. Limits are configured per Crelate tenant, so confirm them with your Crelate admin and build retry-with-backoff around HTTP 429 responses, especially on bulk GET /contacts and GET /placements pulls.

How do I keep Crelate in sync with my data warehouse via Jentic?

Install Jentic with pip install jentic, then async-search for 'list crelate contacts' or 'list crelate placements'. Load the matching list operations and execute them on a schedule with paging parameters; Jentic injects the X-API-Key automatically and returns paged contacts, jobs, and placements ready for warehouse load.