Bindbee
Bindbee provides a unified HRIS and ATS integration API that allows companies to connect with multiple HR systems through a single integration, simplifying workforce data access and HR automation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bindbee the way a machine reads it — 55 machine-readable artifacts across 5 APIs, 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 52.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
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 5
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
Bindbee Departments API
Organizational departments
Bindbee Employees API
Employee records from connected HRIS systems
Bindbee Jobs API
Job listings from connected ATS systems
Bindbee Time Off API
Employee time-off requests and balances
Pricing 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 six things the Kin Score reads for commercial clarity.
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.
Semantic 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.
Candidate
JSON SCHEMACandidatesResponse
JSON SCHEMADepartment
JSON SCHEMADepartmentsResponse
JSON SCHEMAEmployee
JSON SCHEMAEmployeesResponse
JSON SCHEMAJob
JSON SCHEMAJobsResponse
JSON SCHEMATimeOffRequest
JSON SCHEMATimeOffResponse
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 2
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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bindbee · machine-readable index on apis.io