Peerdom API

Name: Peerdom API API
Brand: Peerdom API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee ManagementapiKey24 EndpointsREST

For Agents

Manage organizational structures by creating and updating peers, roles, groups, and projects. Assign roles to people and retrieve org chart maps for a tenant.

Connect the Peerdom API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Peerdom API API.

Assign and revoke roles for team members within organizational hierarchies

Construct and retrieve visual org chart maps reflecting current team structure

Synchronize peer records with external HR systems through bulk read operations

Create project entities and link them to relevant groups and roles

GET STARTED

Start building with Peerdom API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Peerdom API, keeping it validated and agent-ready. Peerdom API provides programmatic access to organizational structure management, including peers (people), roles, groups, projects, and org chart maps. It supports full CRUD operations on all organizational entities and enables role assignment workflows, making it suitable for building dynamic org charts, automating onboarding role assignments, and synchronizing organizational data across HR systems.

Use Cases

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

★ Dynamic Org Chart Synchronization

Keep organizational charts up to date by syncing peer and role data from Peerdom into internal tools or dashboards. The API exposes 24 endpoints for managing peers, roles, groups, projects, and maps. Agents can poll for changes and propagate updates to Slack channels, wiki pages, or HR platforms in near real-time.

Retrieve all roles via GET /roles, then for each role fetch assigned peers via GET /roles/{roleId}/peers to build a complete org chart data structure

Automated Role Assignment During Onboarding

Automate the process of assigning roles to new hires during onboarding. When a new peer record is created, the agent can assign appropriate roles based on department and seniority. Peerdom handles role-to-peer mappings with dedicated endpoints for assignment and unassignment, reducing manual HR overhead.

Create a new peer with POST /peers using name and department data, then assign the appropriate role via POST /roles/{roleId}/peers with the new peer ID

Cross-System Organizational Data Export

Export organizational structures from Peerdom to feed into BI tools, compliance reports, or workforce planning systems. The API provides read access to all entity types including groups, projects, and tenant-level details, enabling periodic bulk exports for analytics or auditing purposes.

Retrieve all groups via GET /groups, all peers via GET /peers, and tenant details via GET /tenant, then compile into a structured workforce report

AI Agent Org Structure Management via Jentic

AI agents discover and call Peerdom API operations through Jentic to manage organizational structures without manual integration work. Agents search for org management capabilities by intent, receive typed schemas for each operation, and execute role assignments or peer lookups through a unified interface. Integration takes under an hour compared to days of direct API work.

Search Jentic for 'assign a role to a team member', load the POST /roles/{roleId}/peers operation schema, and execute with roleId and peerId parameters

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/peers

List all peers in the organization

POST

/peers

Create a new peer

GET

/roles

List all defined roles

POST

/roles/{roleId}/peers

Assign a role to a peer

DELETE

/roles/{roleId}/peers/{peerId}

Unassign a role from a peer

GET

/maps

Retrieve org chart maps

GET

/tenant

Get tenant details

GET

/peers

List all peers in the organization

POST

/peers

Create a new peer

GET

/roles

List all defined roles

POST

/roles/{roleId}/peers

Assign a role to a peer

DELETE

/roles/{roleId}/peers/{peerId}

Unassign a role from a peer

GET

Why though Jentic?

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

Credential isolation

Peerdom API keys (X-Api-Key header) are stored encrypted in the Jentic vault. Agents receive scoped access tokens, so the raw API key never enters the agent's working context.

Intent-based discovery

Agents search by intent (e.g., 'assign a role to a team member') and Jentic returns matching Peerdom operations with input schemas, so the agent calls the correct endpoint without reading documentation.

Time to first call

Direct Peerdom integration: 1-2 days for auth setup, schema mapping, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ChartHop API

ChartHop offers broader org planning with compensation and headcount analytics alongside structure management.

Choose ChartHop when you need compensation planning, headcount budgeting, or scenario modeling in addition to org structure. Choose Peerdom when you need a lightweight role-and-peer model focused purely on organizational hierarchy.

Complementary

BambooHR API

BambooHR handles employee records, time-off, and payroll data that feed into Peerdom's org structure.

Use BambooHR for full employee lifecycle data (personal details, time off, benefits) and Peerdom for the organizational hierarchy and role assignment layer.

Complementary

HiBob API

HiBob provides full HRIS capabilities including payroll, onboarding, and performance that complement Peerdom's org chart focus.

Use HiBob when you need a complete HR platform with payroll and performance reviews. Use Peerdom specifically for dynamic org chart modeling and role-based hierarchy management.

FAQs

Specific to using Peerdom API API through Jentic.

Why is there no official OpenAPI spec for Peerdom API?

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

The Peerdom API uses an API key passed in the X-Api-Key request header. Through Jentic, your API key is stored encrypted in the credential vault and agents receive scoped access without the raw key entering their context.

Can I assign roles to multiple peers in bulk with the Peerdom API?

The API handles role assignments one at a time via POST /roles/{roleId}/peers with a specific peer ID. For bulk assignments, agents iterate over a list of peer IDs and call the assignment endpoint for each. There is no single bulk-assign endpoint.

How do I retrieve the full org chart through the Peerdom API via Jentic?

Search Jentic for 'get org chart map' to discover the GET /maps endpoint. Load the operation schema, execute the call, and receive the current org chart structure. You can also combine GET /roles with GET /roles/{roleId}/peers to construct a role-based hierarchy programmatically.

What are the rate limits for the Peerdom API?

The OpenAPI spec does not document specific rate limits. In practice, standard API key-authenticated services typically enforce per-minute request caps. Monitor HTTP 429 responses and implement exponential backoff in your agent logic.

Can I create and manage org chart maps programmatically?

Yes. POST /maps creates a new draft map, and GET /maps returns all existing maps for the tenant. Maps represent visual org chart layouts. Combine map retrieval with peer and role data to render complete organizational visualizations.