Clockwork Recruiting API

Name: Clockwork Recruiting API
Brand: Clockwork Recruiting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting AtsapiKey14 EndpointsREST

For Agents

Manage candidate records, companies, positions, and webhooks inside an executive search firm's Clockwork Recruiting instance.

Install Jentic One Beta

Connect the Clockwork Recruiting API to your agent

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

Step 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 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 Clockwork Recruiting API.

Add new candidate records and enrich them with addresses, emails, phone numbers, and LinkedIn URLs

Attach work positions and tags to candidate profiles for pipeline segmentation

List companies tracked by the search firm for sourcing and target lists

GET STARTED

Start building with Clockwork Recruiting API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Clockwork Recruiting API for, with concrete tasks.

★ Sourcing Pipeline Sync

Search firms maintain target lists across LinkedIn, referrals, and research vendors. With POST /people, an agent can push a sourced candidate into Clockwork with their core attributes, then enrich the record via the addresses, email_addresses, phone_numbers, and linkedin_urls subresources. This replaces manual data entry from research spreadsheets and keeps the pipeline current without partner intervention.

Create a person in Clockwork for 'Jane Doe' with email jane@example.com, phone +14155551234, and linkedin URL linkedin.com/in/janedoe.

Candidate Tagging and Segmentation

Retained searches require precise pipeline segmentation by industry, function, or stage. POST /people/{personId}/tags applies firm-defined tags from GET /tags to a candidate, enabling longlist filtering and shortlist exports. Agents can tag in bulk based on enrichment signals — e.g., tagging every candidate from a specific company.

Tag person 12345 with 'CFO Track' and 'Healthcare' tags from the firm's tag library.

Webhook-Driven Candidate Updates

Search firm dashboards need real-time updates when partners move candidates through stages. POST /webhooks subscribes an external endpoint to candidate events, while DELETE /webhooks/{webhookId} cleans up after migrations. This eliminates polling and keeps downstream BI tools in sync with the search pipeline.

AI Agent for Executive Search Operations

Pair an AI assistant with a research analyst's workflow so newly identified candidates land in Clockwork without copy-paste. Through Jentic, the agent searches by intent, loads the create-person schema, and posts the record on the analyst's behalf. The firm's API key and token stay in the Jentic vault — never visible to the model.

Search Jentic for 'add candidate to clockwork', load the schema, and execute it for a sourced lead from a LinkedIn export.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/people

Create a candidate record

GET

/people/{personId}

Retrieve a candidate by id

POST

/people/{personId}/tags

Apply tags to a candidate

POST

/people/{personId}/positions

Add a work position to a candidate

GET

/companies

List companies tracked by the firm

POST

/webhooks

POST

/people

Create a candidate record

GET

/people/{personId}

Retrieve a candidate by id

POST

/people/{personId}/tags

Apply tags to a candidate

POST

/people/{personId}/positions

Add a work position to a candidate

GET

/companies

List companies tracked by the firm

Why Jentic?

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

Credential isolation

Clockwork's token + apiKey header pair, scoped to a firm name, is stored encrypted in the Jentic vault (MAXsystem). Agents call the API without ever seeing the secret material.

Intent-based discovery

Agents search Jentic by intent (e.g., 'add a candidate to clockwork') and Jentic returns the matching operations with their schemas, so the agent skips reading partner-specific docs.

Time to first call

Direct Clockwork integration: 1-2 days to handle the firm-scoped base URL and dual auth headers. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Clockwork Recruiting API through Jentic.

Why is there no official OpenAPI spec for Clockwork Recruiting API?

Clockwork Recruiting does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clockwork Recruiting 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 Clockwork Recruiting API use?

Clockwork uses two header-based credentials in tandem: a token (Authorization-style) and an API key for the firm. Both are scoped to a firm name embedded in the base URL. Jentic stores both encrypted in the MAXsystem vault and injects them at call time so agents never see the raw values.

Can I add a candidate's contact details with the Clockwork Recruiting API?

Yes. After creating the candidate via POST /people, attach contact details via the dedicated subresources: POST /people/{personId}/email_addresses, /phone_numbers, /addresses, and /linkedin_urls. Each call returns the attached object with its id.

What are the rate limits for the Clockwork Recruiting API?

Clockwork enforces per-firm rate limits in the low hundreds of requests per minute. The spec does not encode exact thresholds, so handle 429 responses with backoff. Jentic surfaces rate limit responses to the agent so it can pace bulk imports correctly.

How do I subscribe to candidate update events through Jentic?

Run pip install jentic, search for 'register clockwork webhook', load the POST /webhooks schema, and execute with your event types and target URL. Jentic returns the created webhook id which you can later delete via the DELETE /webhooks/{webhookId} operation.

Clockwork Recruiting API

Connect the Clockwork Recruiting API to your agent

Capabilities

Start building with Clockwork Recruiting API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs