Chameleon-i API

Name: Chameleon-i API API
Brand: Chameleon-i API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting AtsapiKey36 EndpointsREST

For Agents

Manage candidates, clients, companies, job requirements, activities, and baskets in the Chameleon-i recruitment CRM, including shortlist, search, and combined-note creation.

Quickstart

Get started with Chameleon-i API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search chameleon-i candidates by skill"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chameleon-i API API.

Create, read, update, and delete candidate records and pull a basic or full profile

Manage company and client records and look up enumeration values for each entity

Create and update job requirements and shortlist candidates against them

Search any supported entity type with structured filters

GET STARTED

Start building with Chameleon-i API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Chameleon-i API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Chameleon-i API, keeping it validated and agent-ready. Chameleon-i is a recruitment CRM and applicant-tracking system, and its REST API exposes the core entities — companies, clients, candidates, requirements, contracts, activities, baskets, and user records — with full CRUD plus entity search, phone-number lookup, and combined note creation. Recruiters use it to keep external sourcing tools, job boards, and reporting systems in sync with Chameleon-i without re-keying data.

Use Cases

Patterns agents use Chameleon-i API API for, with concrete tasks.

★ Job Board Inbound Sync

Keep Chameleon-i in step with applications submitted from job boards or career sites by creating or updating candidate records as each application arrives. POST /candidate/add creates the record, POST /candidate/update/{candidateID} keeps later submissions in sync, and POST /requirement/shortlist links the candidate to the role they applied for. Recruiters then work the candidate inside Chameleon-i without re-keying data from the careers site.

Call POST /candidate/add for each new application, then POST /requirement/shortlist with the candidate id and the requirement id

Inbound Call Resolution

When a candidate or client calls in, resolve the caller's record before the recruiter answers. POST /miscellaneous/query_entity_by_phone returns the matching candidate, client, or company so the screen pop can show name, requirement context, and recent activity. Used by recruitment teams running softphone integrations on top of Chameleon-i.

Call POST /miscellaneous/query_entity_by_phone with the caller's E.164 number and surface the matching candidate or client record

Outreach Basket Management

Build, edit, and reuse baskets of candidates for targeted outreach. GET /basket/list shows existing baskets, POST /basket/new creates a new one, and POST /basket/alter adjusts membership. Combined with POST /{entity_type}/search to source candidates by criteria, this turns ad hoc list-building into a repeatable, auditable workflow.

Call POST /candidate/search with skill and location filters, then POST /basket/new with the resulting candidate ids

AI Agent Recruiter Assistant via Jentic

A recruiter agent receives a request like 'find Python contractors in Manchester available next month and add them to the new fintech requirement'. Through Jentic, the agent searches for a candidate-search operation, loads the input schema, and calls /candidate/search and /requirement/shortlist with credentials drawn from the Jentic vault. The agent updates Chameleon-i directly, no manual data entry required.

Use Jentic to search 'search candidates by skill', execute it for 'python' in Manchester, then search 'shortlist candidates against a requirement' and call it for the resulting ids

Key Endpoints

36 endpoints — jentic publishes the only available openapi specification for chameleon-i api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/candidate/add

Create a candidate record

GET

/candidate/read/{candidateID}

Read a full candidate profile

POST

/requirement/add

Create a job requirement

POST

/requirement/shortlist

Shortlist candidates against a requirement

POST

/{entity_type}/search

Search any supported entity type

POST

/miscellaneous/query_entity_by_phone

Resolve a caller phone number to a record

POST

/basket/new

Create a basket for outreach

POST

/miscellaneous/create_combined_note

Create a combined activity and note

POST

/candidate/add

Create a candidate record

GET

/candidate/read/{candidateID}

Read a full candidate profile

POST

/requirement/add

Create a job requirement

POST

/requirement/shortlist

Shortlist candidates against a requirement

POST

/{entity_type}/search

Search any supported entity type

Why though Jentic?

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

Credential isolation

Chameleon-i API keys are stored encrypted in the Jentic vault and added to the API-KEY request header at execution time. Agents receive scoped access only — the raw key never enters the agent's context window or prompt history.

Intent-based discovery

Agents search Jentic by intent (e.g., 'add a candidate' or 'search candidates by skill') and Jentic returns the matching Chameleon-i operation with its input schema, so the agent calls the right endpoint without scraping the readme.io docs.

Time to first call

Direct Chameleon-i integration: 1-2 days to wire 36 endpoints, the entity_type path parameter pattern, and lookup-value resolution. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Bullhorn API

Recruitment CRM and ATS with similar candidate, client, and requirement entities

Choose Bullhorn when the agency standardises on Bullhorn's data model and middle-office integrations; choose Chameleon-i for its lighter-weight tenant model

Alternative

Lever API

Modern ATS focused on internal corporate hiring rather than agency recruiting

Choose Lever when the workload is in-house corporate hiring; choose Chameleon-i for agency workflows that need client and contract records alongside candidates

Complementary

Greenhouse Harvest API

Corporate ATS often used by Chameleon-i agency clients on the in-house side

Use Greenhouse Harvest alongside Chameleon-i to mirror agency-submitted candidates into the client's internal ATS

FAQs

Specific to using Chameleon-i API API through Jentic.

Why is there no official OpenAPI spec for Chameleon-i API?

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

The API uses an API key passed in the API-KEY request header, issued from inside the Chameleon-i workspace. Through Jentic, the key lives in the Jentic vault and is added to outgoing requests at execution time so it never enters the agent's prompt or context window.

Can I shortlist candidates against a requirement with the Chameleon-i API?

Yes. POST /requirement/shortlist accepts a requirement id and a list of candidate ids and links them as a shortlist inside the requirement. Pair with POST /candidate/search to source candidates by structured filters before shortlisting.

What are the rate limits for the Chameleon-i API?

Limits are tied to the Chameleon-i tenant and plan rather than published as a fixed number in the spec. Watch for 429 responses with Retry-After headers, especially when running bulk imports through POST /candidate/add or large POST /{entity_type}/search calls.

How do I find a candidate by phone number through Jentic?

Search Jentic for 'find a chameleon-i record by phone number', load the operation backed by POST /miscellaneous/query_entity_by_phone, and execute it with the caller's E.164 number. Jentic injects the API-KEY header so the agent receives the matching record back as typed JSON.

Does the Chameleon-i API support combined activity and note creation?

Yes. POST /miscellaneous/create_combined_note records an activity (call, meeting, email, etc.) and a free-text note in a single request, attached to the relevant candidate, client, or requirement. This avoids the two-call pattern of creating an activity and a note separately.