Gatekeeper to Hibob integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Gatekeeper and Hibob: authenticate both systems, choose the objects to sync (such as Gatekeeper's Contracts and Vendors (Suppliers)), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Gatekeeper: No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream. On Hibob: Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Gatekeeper side: Users, Categories, Contracts, Vendors (Suppliers), plus custom fields where Gatekeeper exposes them. On the Hibob side: Documents, Named lists, People (Employees), Employment. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Gatekeeper and Hibob: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Hibob creates the matching user in Gatekeeper with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. Hibob: REST API (the Bob API). Authentication: Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin. Stacksync manages authentication, retries, and rate limits on both sides.