ChartHop API

Name: ChartHop API API
Brand: ChartHop API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer10 EndpointsREST

For Agents

Read and update people, jobs, groups, and scenarios in a ChartHop org. Bearer-authenticated REST API with 10 endpoints under /v1/org.

Quickstart

Get started with ChartHop 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:
"list people in a charthop org"

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

Capabilities

What an agent can do with ChartHop API API.

List the organizations the authenticated token has access to via GET /v1/org

Retrieve an org's full record including reporting structure via GET /v1/org/{orgId}

List and look up people in an organization through /v1/org/{orgId}/person endpoints

Create a new person record under an org and PATCH that record to update fields

GET STARTED

Start building with ChartHop API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for ChartHop API, keeping it validated and agent-ready. ChartHop is a people-analytics and org-management platform that exposes organizations, employees, jobs, groups, and scenarios over a bearer-authenticated REST API. The 10 documented endpoints let an agent retrieve org structure, list and update people, look up jobs, and read what-if compensation scenarios. It is read-heavy: most endpoints are GET, with create-person and update-person available on the people resource.

Use Cases

Patterns agents use ChartHop API API for, with concrete tasks.

★ Sync new hires from an ATS into ChartHop

When a candidate is moved to 'hired' in an applicant tracking system, an agent can call POST /v1/org/{orgId}/person to register the new employee in ChartHop with their job, start date, and reporting line. This keeps the org chart and headcount metrics in sync without a manual import. The single-endpoint create flow makes this a low-effort integration.

Create a person in ChartHop org acme with name 'Jane Doe', title 'Senior Engineer', and start date 2026-07-01

Pull org structure for an internal directory

Combine GET /v1/org/{orgId}/person and GET /v1/org/{orgId}/group to build an internal employee directory with names, titles, and group membership. Because the endpoints return structured JSON, an agent can produce the directory in one pass without scraping HTML or parsing exports.

List all persons in ChartHop org acme, then list all groups, and emit a CSV mapping each person to their primary group

Reconcile job definitions with a compensation review

Call GET /v1/org/{orgId}/job to enumerate jobs and GET /v1/org/{orgId}/scenario to fetch active what-if scenarios. An agent can compare the two and highlight roles whose target compensation has drifted from the latest scenario, which is useful as a check before a comp cycle is finalised.

List all jobs in ChartHop org acme, list all scenarios, and return any job whose current title appears in a scenario but with a different compensation band

Surface ChartHop people data inside an AI agent

An AI agent uses Jentic to discover the ChartHop person endpoints, loads their schema, and answers natural-language questions like 'who reports to the head of engineering?' by combining list-person and get-person calls. The bearer-auth setup is handled by Jentic so the agent never sees the raw token.

Search Jentic for 'find people in charthop', load the list-persons schema, and return the names and titles of all people reporting to the person with title 'VP Engineering' in org acme

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/org

List organizations

GET

/v1/org/{orgId}

Get an organization

GET

/v1/org/{orgId}/person

List persons in an organization

POST

/v1/org/{orgId}/person

Create a person

PATCH

/v1/org/{orgId}/person/{personId}

Update a person

GET

/v1/org/{orgId}/job

List jobs

GET

/v1/org/{orgId}/scenario

List scenarios

GET

/v1/org/{orgId}/group

List groups

GET

/v1/org

List organizations

GET

/v1/org/{orgId}

Get an organization

GET

/v1/org/{orgId}/person

List persons in an organization

POST

/v1/org/{orgId}/person

Create a person

PATCH

/v1/org/{orgId}/person/{personId}

Update a person

GET

Why though Jentic?

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

Credential isolation

ChartHop bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access — the raw token never enters the agent's prompt context.

Intent-based discovery

Agents search by intent (e.g., 'list charthop people' or 'create a charthop person') and Jentic returns the matching ChartHop operations with their input schemas.

Time to first call

Direct ChartHop integration: half a day to wire up bearer auth, parse the org/person/job model, and handle pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HiBob API

HiBob is a full HRIS — choose it over ChartHop when you need payroll, time off, and onboarding rather than org-chart analytics.

Use HiBob when the task involves payroll-related employee data; use ChartHop when the task is org-chart, headcount, or compensation-scenario analytics.

Complementary

Chartbrew API

Chartbrew is an open-source BI tool — pull people data from ChartHop and chart it in Chartbrew.

Use Chartbrew alongside ChartHop when the user wants to visualise headcount, compensation, or attrition on a self-hosted dashboard.

Complementary

ChartMogul API

ChartMogul tracks SaaS revenue — combine with ChartHop for revenue-per-employee reporting.

Use ChartMogul for the revenue side and ChartHop for the headcount side when computing efficiency metrics.

FAQs

Specific to using ChartHop API API through Jentic.

Why is there no official OpenAPI spec for ChartHop API?

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

ChartHop uses HTTP bearer-token authentication. Every request must send 'Authorization: Bearer <token>' against api.charthop.com. Through Jentic, the token sits in the encrypted MAXsystem vault and is injected at execution time so the agent never sees it.

Can I create new employees with the ChartHop API?

Yes. POST /v1/org/{orgId}/person creates a person record in the specified org. You can update existing people with PATCH /v1/org/{orgId}/person/{personId}. There is no DELETE-person endpoint in this spec — terminations are handled by editing the person record.

How do I list all people in a ChartHop org through Jentic?

Run pip install jentic, set JENTIC_AGENT_API_KEY, then search 'list charthop people'. Jentic returns GET /v1/org/{orgId}/person with its query schema. Load the schema, supply your orgId, and execute — the agent gets the full person list without parsing docs.

Are there documented rate limits for the ChartHop API?

The OpenAPI spec does not declare rate-limit headers or per-token quotas. ChartHop's HR data is typically read in batch, so design your agent to handle a 429 response by backing off and retrying, and read any RateLimit headers the live service returns to learn the active limits.

Can the ChartHop API return what-if compensation scenarios?

Yes — GET /v1/org/{orgId}/scenario lists scenarios attached to an org. The endpoint returns each scenario's identifier and metadata, which an agent can join with GET /v1/org/{orgId}/job to compare current jobs against scenario-defined target bands.