Stop building OneLogin integrations from scratch. Bindbee gives you one API to pull the user directory from OneLogin (names, emails, usernames, departments, managers, job titles, account status, and custom attributes), normalized to the same models you use for Okta, Microsoft Entra ID, and 73+ HR systems.
Bindbee normalizes OneLogin's data into our unified models. One integration, consistent data structure across 73+ HR systems.
Authenticate via Magic Link—our drop-in auth component. Your customer logs in to OneLogin and grants access in minutes.
We normalize OneLogin data to unified models with automatic incremental syncs. Employee, compensation, benefits, and dependent data stays fresh.
One REST API for OneLogin and 73+ other HR systems. Same endpoints, same data structure, regardless of your customer's payroll provider.
Customers authenticate effortlessly via Magic Link, with an embeddable SDK that enables seamless, in-app connections.
Bindbee syncs OneLogin users into its Employee and Employment models. That includes names, username, work email, mobile phone, job title, department, manager, account status, and custom attributes.
Their OneLogin subdomain, plus a Client ID and Client Secret from an API credential pair with the Read Users scope. Your customer enters these in Bindbee Link; credentials are never stored on your servers.
Read Users. It gives read-only access to users, roles, and groups, which is all Bindbee needs. There's no need to grant Manage Users or Manage All.
Yes. Custom user fields defined in OneLogin come through in the custom_fields object on each Employee.
Yes. The manager field on each Employee holds the manager's Bindbee ID, and department is available on both Employee and Employment.
Yes. The employment_status field reflects the user's account status, so you can filter for inactive users and act on them, for example to revoke access in your product.
Many customers treat their IdP as the source of truth for who has access. Syncing OneLogin gives you an up-to-date user list for provisioning, access reviews, and seat management, even when the customer's HRIS isn't connected.
You don't. Bindbee generates and refreshes OneLogin access tokens, manages rate limits, and retries failed requests.
Bindbee syncs OneLogin on a schedule, not in real time. After the first sync, incremental syncs keep data current, and webhooks tell you when new data is ready. You can also trigger a sync through the API.
We use cookies to improve your experience on our site. By using our site, you are agreeing to the collection and use of data as described in our privacy policy.
