Bindbee
Bindbee is a unified API for HRIS, Payroll, ATS and LMS integrations. One integration against Bindbee reaches 67+ third-party HR systems — BambooHR, Workday, ADP, Greenhouse, Lever, Personio, Hibob and the rest — through normalized employee, candidate, job, payroll, time-off and course models, so a B2B software company never builds a one-to-one connector again. Each of its customers' end users authorizes their own system through an embedded link flow and is addressed by a connector token; reads are served from Bindbee's synced copy of the upstream system, refreshed every 24 hours by default, with webhooks for sync and data-change events and a passthrough endpoint for anything the unified model does not cover.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Bindbee the way a machine reads it — 65 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bindbee scores 67.0/100 (exemplar), with a separate agent-readiness read of 47/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Bindbee's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bindbee/"
title="Bindbee on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bindbee.svg"
alt="Bindbee Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/bindbee/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bindbee/"
title="Bindbee on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bindbee/card.svg"
alt="Bindbee Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Bindbee
Each block below is one kind of artifact we hold for Bindbee. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Bindbee Candidates API
Job candidates from connected ATS systems, normalized across Greenhouse, Lever, Workable, Ashby and every other connected ATS.
Bindbee Departments API
Organizational departments from connected HRIS and ATS systems.
Bindbee Employees API
Normalized employee records from connected HRIS systems, including employment, compensation, benefits, groups and reporting hierarchy.
Bindbee Jobs API
Job listings and requisitions from connected ATS systems.
Bindbee Time Off API
Employee time-off requests and accrued balances from connected HRIS systems.
Bindbee Unified API
The complete Bindbee contract as the provider publishes it — 119 paths and 144 operations across the HRIS, ATS, LMS, Custom Fields, Embedded and platform namespaces, fetched ver...
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBindbee Candidates API
OPEN COLLECTIONBindbee Candidates Departments API
OPEN COLLECTIONBindbee Candidates Employees API
OPEN COLLECTIONBindbee Candidates Jobs API
OPEN COLLECTIONBindbee Candidates Time Off API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Bindbee Docs
Bindbee serves a remote MCP server on its own documentation host. It was probed anonymously with a JSON-RPC tools/list call on 2026-09-04 and returned three tools with full inpu...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bindbee Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bindbee Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Unified HRIS API
Access employee data from BambooHR, Workday, ADP, and 50+ HRIS systems through one API.
Unified ATS API
Access job listings and candidates from Greenhouse, Lever, Workable, and other ATS systems.
Data Normalization
Consistent normalized schema across all connected HR systems.
Cursor Pagination
Efficient cursor-based pagination for large employee datasets.
Connector Tokens
Secure per-integration connector tokens for multi-tenant HR data access.
Real-Time Sync
Webhooks and polling for real-time HR data synchronization.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Bindbee Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Bindbee Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Bindbee API Rules
SPECTRALBindbee API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AtsCandidate
JSON SCHEMAPaginatedResponse[AtsCandidate]
JSON SCHEMAAtsDepartment
JSON SCHEMAPaginatedResponse[AtsDepartment]
JSON SCHEMAHrisEmployeeResponse
JSON SCHEMAPaginatedResponse[HrisEmployeeResponse]
JSON SCHEMAAtsJob
JSON SCHEMAPaginatedResponse[AtsJob]
JSON SCHEMAHrisTimeOff
JSON SCHEMAPaginatedResponse[HrisTimeOff]
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 10
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Bindbee Candidate Structure
JSON STRUCTUREBindbee Candidates Response Structure
JSON STRUCTUREBindbee Department Structure
JSON STRUCTUREBindbee Departments Response Structure
JSON STRUCTUREBindbee Employee Structure
JSON STRUCTUREBindbee Employees Response Structure
JSON STRUCTUREBindbee Job Structure
JSON STRUCTUREBindbee Jobs Response Structure
JSON STRUCTUREBindbee Time Off Request Structure
JSON STRUCTUREBindbee Time Off Response Structure
JSON STRUCTUREScroll within the panel for all 10 ·
Examples 10
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Bindbee Candidate Example
EXAMPLEBindbee Department Example
EXAMPLEBindbee Employee Example
EXAMPLEBindbee Job Example
EXAMPLEScroll within the panel for all 10 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Employee Directory Integration
Sync employee records from any HRIS into internal apps and directories.
Onboarding Automation
Trigger onboarding workflows when new employees are added in the HRIS.
Recruiting Pipeline Visibility
Track candidates across ATS stages in unified dashboards.
HRIS Migration
Move between HRIS providers without rewriting integrations.
HR Analytics
Aggregate people data from multiple HR systems for workforce analytics.
Resources
Every other property we hold for Bindbee — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bindbee · machine-readable index on apis.io
This is an independent, third-party profile of Bindbee, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.