Bindbee unified API profile
Unified API for HRIS, payroll, ATS, benefits, and LMS integrations.
Research note: This neutral profile summarizes first-party material published by Bindbee. It was last checked . Capabilities can differ by connector, so verify the exact model, field, action, and refresh behavior required by your product.
Bindbee at a glance
- Focus
- Employment-focused unified APIs with benefits and payroll depth.
- Good fit for
- Products that need normalized workforce, payroll, benefits, recruiting, or learning data through one employment-focused integration layer.
- Categories
- HRIS, Payroll, ATS, Benefits, LMS
- Data delivery
- Scheduled synchronization with connector and data-change webhooks; the documented default sync frequency is once every 24 hours and can be customized.
- Extension path
- Custom fields, optional raw data, and authenticated passthrough requests supplement the unified models.
What is Bindbee?
Bindbee is an employment-focused unified API platform for connecting a product to HRIS, payroll, ATS, benefits, and LMS systems. Its public product material emphasizes normalized workforce models, read-and-write operations, and embedded customer connection flows.
- The HRIS surface includes employees, employments, companies, groups, locations, compensation, time off, payroll runs, benefits, dependents, documents, and related workforce objects.
- The ATS documentation includes jobs, candidates, applications, offers, interviews, scorecards, attachments, tags, and other recruiting objects, with documented create operations for several models.
- The LMS documentation covers users, courses, content, skills, categories, completions, and enrollments.
How do customers connect and authenticate?
A product can use Bindbee’s embedded Magic Link flow to let an end user authorize a system. Server-to-server requests use an organization API key, while end-user data requests also carry the connection-specific connector token.
- The API key is sent as an Authorization Bearer token and identifies the calling organization.
- The connector token is sent through X-Connector-Token and scopes the request to one end-user connection.
- Keeping the durable credentials on the backend lets the product maintain its own tenant-to-connection mapping.
How are data and updates delivered?
Bindbee imports and normalizes connected-system data on a scheduled cadence, then exposes sync lifecycle and data-change events through webhooks. The documented default is one sync every 24 hours, with customization available.
- Webhook events cover connector sync started, completed, and error states as well as employee and connector data changes.
- Webhook requests are documented with HMAC-SHA256 verification through the X-Bindbee-Webhook-Signature header.
- Applications should still verify connector-level freshness and use idempotent ingestion because authorization success and completed data synchronization are separate states.
How does Bindbee handle fields outside the common model?
Bindbee supports custom fields that map values from an upstream payload into a unified response. Mappings can be defined at organization or connector scope, and the documentation also exposes raw-data inspection, preview tooling, and a passthrough request endpoint.
- Custom-field mappings use JMESPath expressions and can be tested before they are saved.
- Connector-scoped mappings can override organization-level mappings for a particular customer connection.
- Passthrough is the provider-specific escape hatch when a required endpoint or action is not represented by a normalized model.
What developer tooling is documented?
Bindbee publishes interactive API documentation, development and production environments, dashboard logs, connector management, and SDK support for Python, Node, and Go.
- The product page describes an embeddable connection experience that can be branded for the product’s users.
- The API index exposes read and write endpoints across HRIS and ATS models, plus meta endpoints that describe connector-specific write requirements.
- The integration catalog labels different connection methods, including API and SFTP, so setup and behavior should be checked per connector.
What should buyers verify?
- Connector coverage is not the same as model, field, filter, or write coverage; validate the exact provider and operation before committing a workflow.
- The public integration catalog includes both API and SFTP connection methods, so onboarding and freshness can differ by connector.
- Some documented surfaces are explicitly marked beta, including the HRIS Documents API at the time of review.
For a cross-vendor evaluation framework, read the verified unified API buyer’s guide.
Frequently asked questions about Bindbee
What is Bindbee best suited for?
Bindbee is most directly aligned with HR technology, benefits, payroll, and adjacent employment products that need normalized workforce data and employment-specific write workflows.
Does Bindbee support both reads and writes?
Yes, Bindbee documents read and write endpoints, but support must be confirmed for the exact connector, model, fields, and action required by the product.
How fresh is Bindbee data?
Bindbee documents a default synchronization frequency of once every 24 hours that can be customized, together with webhooks for sync status and data-change notifications.
Can Bindbee expose provider-specific fields?
Yes. Bindbee documents custom-field mappings, raw-data inspection, and passthrough requests for requirements outside its standard unified models.
Sources checked
- Bindbee official website — official website, checked
- Bindbee product overview — official website, checked
- Bindbee integration catalog — official website, checked
- Bindbee documentation index for agents — documentation, checked
- Bindbee API authentication — documentation, checked
- Bindbee sync frequency — documentation, checked
- Bindbee webhook overview — documentation, checked
- Bindbee custom fields — documentation, checked
- Bindbee passthrough requests — documentation, checked
- Bindbee guide to unified APIs — blog, checked