Organimi API
Agent-ready OpenAPI document · curated by JenticHR recruitingEmployee Managementbearer23 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage organizations, people, charts, and roles in Organimi, and export rendered org charts in multiple formats.
Use for: I need to add a new hire to our org chart, Export the current org chart as a PDF, List all charts under my organization, Find every role reporting into the engineering chart
Not supported: Does not handle payroll, time tracking, or performance reviews - use for org chart structure, people records, and role exports only.
Jentic publishes the only available OpenAPI specification for Organimi API, keeping it validated and agent-ready. Organimi is a cloud org-chart platform used by HR and people-ops teams to maintain visual organization charts, talent pools, and reporting hierarchies. The API spans 23 endpoints across organizations, people, custom fields, charts, roles, and exports, letting integrations sync HRIS data into a live chart and pull rendered charts in PDF, PNG, or CSV. It supports OAuth login plus bearer-token API access, and it is suitable for keeping org charts in lock-step with payroll or directory sources.
Install Jentic One Beta
Connect the Organimi API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Organimi 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%2Forganimi.com%2Forganimi" | 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%2Forganimi.com%2Forganimi" | 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 Organimi API.
List the organizations the authenticated user belongs to via GET /api/v7/me/organizations
Add a new person to the talent pool of an organization with POST /api/v7/organizations/{orgId}/people
Update or remove an employee record using PATCH or DELETE on /api/v7/organizations/{orgId}/people/{personId}
Define custom fields on people records through POST /api/v7/organizations/{orgId}/fields
Create a new org chart and populate roles via POST /api/v7/organizations/{orgId}/charts and /charts/{chartId}/roles
Export a chart to PDF, PNG, or CSV through GET /api/v7/organizations/{orgId}/charts/{chartId}/exports/{format}
Search across roles in the connected organizations using GET /api/v7/search/roles
Use Cases
Patterns agents use Organimi API for, with concrete tasks.
★ HRIS to Org Chart Sync
People-ops teams often hold the source of truth in BambooHR, Workday, or a directory service while leaders prefer a visual chart. The Organimi API lets a sync job push people, titles, and reporting lines into Organimi after each HRIS change so the chart never drifts. The 23 endpoints cover the full CRUD surface needed for daily reconciliation.
On each HRIS webhook, POST or PATCH /api/v7/organizations/{orgId}/people to mirror the change, then PATCH the matching role on the relevant chart.
Automated Org Chart Exports
Boards and leadership often request a current PDF org chart for monthly reviews. Instead of manually exporting, a scheduled job can call GET /api/v7/organizations/{orgId}/charts/{chartId}/exports/{format} to pull the latest chart as PDF, PNG, or CSV and attach it to the report pipeline.
Call GET /api/v7/organizations/{orgId}/charts/{chartId}/exports/pdf and upload the binary response to the shared drive used for the board pack.
Custom Field Driven Reporting
Finance often wants to slice headcount by cost center or location. Defining custom fields via POST /api/v7/organizations/{orgId}/fields lets people-ops add structured attributes that flow into chart filters and exports without modifying core people records.
POST a custom field cost_center to /api/v7/organizations/{orgId}/fields, then PATCH each person record to populate it.
Agent-Driven People Operations via Jentic
Agents that handle onboarding and directory updates can keep Organimi in sync without learning the API surface. Jentic exposes operations by intent and isolates the bearer token in the vault, letting an agent add a hire, assign a role, and export the updated chart in one workflow.
Use Jentic to search 'add a person to the org chart', load the schema for POST /api/v7/organizations/{orgId}/people, and execute with the new hire details.
Key Endpoints
23 endpoints — jentic publishes the only available openapi specification for organimi api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/v7/me/organizations
List organizations the user belongs to
POST
/api/v7/organizations/{orgId}/people
Add a person to the talent pool
PATCH
/api/v7/organizations/{orgId}/people/{personId}
Update a person record
POST
/api/v7/organizations/{orgId}/charts
Create a new org chart
POST
/api/v7/organizations/{orgId}/charts/{chartId}/roles
Add a role to a chart
GET
/api/v7/organizations/{orgId}/charts/{chartId}/exports/{format}
Export a chart as PDF, PNG, or CSV
GET
/api/v7/search/roles
Search across roles
GET
/api/v7/me/organizations
List organizations the user belongs to
POST
/api/v7/organizations/{orgId}/people
Add a person to the talent pool
PATCH
/api/v7/organizations/{orgId}/people/{personId}
Update a person record
POST
/api/v7/organizations/{orgId}/charts
Create a new org chart
POST
/api/v7/organizations/{orgId}/charts/{chartId}/roles
Add a role to a chart
GET
/api/v7/organizations/{orgId}/charts/{chartId}/exports/{format}
Export a chart as PDF, PNG, or CSV
GET
/api/v7/search/roles
Search across roles
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Organimi API by hand means setting up its bearer auth and threading the orgId and chartId through the people, chart, and role routes yourself. Through Jentic you install once, import Organimi from the API Directory, store the token once, and your agent calls it.
Permission scoping
Organimi puts the organization id in the URL path (/organizations/{orgId}/people, /organizations/{orgId}/charts), so a rule can pin your agent to one organization: it can work with that org's people and charts and nothing else. You choose the operations it may call, so editing a person or creating a chart is not included unless you add it.
Credential isolation
Your Organimi bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a person to the org chart' or 'export a chart', and Jentic returns the matching Organimi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Organimi API through Jentic.
Why is there no official OpenAPI spec for Organimi API?
Organimi publishes its API on SwaggerHub but does not host a maintained OpenAPI document on its own domain. Jentic generates and maintains this spec so that AI agents and developers can call Organimi 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 Organimi API use?
Organimi uses bearer-token authentication, with OAuth login and logout endpoints under /api/v7/auth. Through Jentic the bearer token is stored encrypted in the vault and injected at execution.
Can I export an org chart as a PDF through the Organimi API?
Yes. Call GET /api/v7/organizations/{orgId}/charts/{chartId}/exports/{format} with format set to pdf. PNG and CSV are also supported on the same endpoint.
What are the rate limits for the Organimi API?
The OpenAPI spec does not specify numeric rate limits. SwaggerHub publishes Organimi's terms but not throttle thresholds - confirm with Organimi support if you plan to push more than a few hundred people updates per minute.
How do I add a new hire to an Organimi chart through Jentic?
Search Jentic for 'add a person to an org chart', load the POST /api/v7/organizations/{orgId}/people schema, and execute with the new hire's name, title, and reporting manager. Then PATCH the relevant chart role to slot them into the structure.
Can I define custom fields on Organimi people records?
Yes. POST /api/v7/organizations/{orgId}/fields creates a new custom field definition. After creation, PATCH /api/v7/organizations/{orgId}/people/{personId} can populate that field for individual people.
Can I limit what my agent is allowed to do with the Organimi API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which operations and credentials your agent may use. Because Organimi carries the organization id in the URL path (/organizations/{orgId}/people, /organizations/{orgId}/charts), you can pin the agent to a single organization and let it touch only that org's people, charts, and role or export routes. You also choose the exact operations it may call, so read-only actions like listing charts or exporting a PDF can be enabled while editing a person or creating a chart stays off unless you add it.
GET STARTED