Empuls supports JSON over REST APIs and CSV over SFTP for data exchange, using HTTPS and SFTP as the underlying communication protocols, with field-level metadata covering HRIS records, reward transactions, and redemption activity.
Supported Integration Protocols
Empuls uses two primary communication protocols for back-end data exchange: HTTPS for real-time REST API calls and SFTP for scheduled or bulk file transfers. HTTPS is the standard for event-driven and on-demand integrations where low latency matters, while SFTP suits batch processes such as nightly employee roster syncs. Both protocols are secured in line with Empuls’s ISO 27001 and SOC 2 Type II compliance posture.Data Formats
Empuls exchanges data in JSON over REST APIs and CSV over SFTP. JSON is the preferred format for real-time integrations because it is lightweight, self-describing, and natively supported by virtually every HRIS and HCM platform. CSV transfers are typically used for bulk employee imports, historical reward exports, or scheduled report delivery where a tabular structure is more practical.HRIS Integration Metadata
When Empuls connects to an HRIS such as Workday, SAP SuccessFactors, or Darwinbox, the sync payload includes core employee attributes: Employee ID, full name, work email, department, designation, reporting manager details, and employment status. These fields drive automated onboarding flows — for example, when a new hire is added in Darwinbox, Empuls automatically provisions their account and assigns them to the correct peer group without any manual intervention.Rewards and Recognition Metadata
For reward and recognition activity, Empuls exposes transaction-level metadata that enables granular reporting. Each record includes an Award ID, Transaction ID, timestamp, points allocated, and redemption details such as channel and catalog item redeemed. Finance and People Analytics teams typically consume this data to reconcile reward spend, measure program ROI, and track recognition frequency across business units.Field-Level Specs and Custom Attributes
The exact set of fields exchanged depends on the specific integration use case. Empuls shares detailed interface specifications and field mapping documentation during the integration scoping phase. Custom metadata — such as cost-center codes or business-unit tags — can be added to align with an organisation’s internal reporting taxonomy. Learn more: Empuls Help Centre — Back-end integrationHRIS Integrations
Connect Empuls with Workday, SAP SuccessFactors, Darwinbox, and other HRIS platforms to automate employee data sync and provisioning.
SSO and Authentication
Set up single sign-on for Empuls using SAML 2.0 or OAuth 2.0 with your existing identity provider.
Webhooks and Event Triggers
Configure real-time webhooks to push Empuls recognition events to external systems like Slack or MS Teams.
Data Security and Compliance
Learn how Empuls protects integration data under ISO 27001 and SOC 2 Type II certifications.