Clockwork Recruiting API
Agent-ready OpenAPI document · curated by JenticHR recruitingRecruiting AtsapiKey14 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage candidate records, companies, positions, and webhooks inside an executive search firm's Clockwork Recruiting instance.
Use for: I want to add a new candidate to our executive search pipeline, Attach a LinkedIn URL to an existing candidate profile, Retrieve all tags configured for our firm, Register a webhook to receive candidate updates
Not supported: Does not handle background checks, offer letter generation, or payroll - use for executive search candidate management and pipeline events only.
Jentic publishes the only available OpenAPI specification for Clockwork Recruiting API, keeping it validated and agent-ready. Clockwork Recruiting is an executive search platform used by retained search firms to manage candidate pipelines, client engagements, and outreach. The API exposes people, companies, positions, tags, regions, and webhooks, with the firm name embedded in the base URL so each call is scoped to a specific search firm. Authentication combines a token with a firm-specific API key.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclockworkrecruiting.com%2Fclockwork-recruiting" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclockworkrecruiting.com%2Fclockwork-recruiting" | 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.
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
Retrieve the firm's tag and region taxonomies for consistent classification
Register webhooks to receive candidate or position update events
Look up an individual candidate by id for profile review or update flows
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.
Register a webhook pointing to https://ops.example.com/clockwork-events to receive person and position updates.
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 your Jentic One instance - 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
Register a webhook subscription
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
Register a webhook subscription
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Clockwork Recruiting by hand means carrying its Base64 token and X-API-Key header pair, substituting your firm name into the base path, and handling retries yourself against api.clockworkrecruiting.com/v3.0/{firmName}. Through Jentic you install once, import the Clockwork Recruiting API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Clockwork puts the person id in the URL path (/people/{personId}/...), so a rule can pin your agent to one candidate: it can add tags or positions to that person and nothing else. You choose the operations it may call, so creating people or webhooks are not included unless you add them.
Credential isolation
Your Clockwork token and X-API-Key, scoped to your firm name, are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a candidate to Clockwork', and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without browsing the partner-specific docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Clockwork Recruiting API?
Yes. Because your Jentic One instance is self-hosted, you write the rules that decide which Clockwork Recruiting operations and credentials your agent may use. Since the person id sits in the URL path, you can pin the agent to a single candidate so it only adds tags via POST /people/{personId}/tags or positions via POST /people/{personId}/positions and nothing else. Operations like creating a candidate with POST /people or registering a POST /webhooks subscription stay out of reach unless you explicitly grant them.
GET STARTED