Skip to main content
Empuls is built on a service-oriented architecture (SOA) and provides full access to its core functions through a public API SDK, enabling IT teams to execute recognition, rewards, and engagement capabilities as services within external applications and portals.
Xoxoday Empuls is architected on a service-oriented architecture (SOA), meaning its core capabilities — recognition, rewards, surveys, and analytics — are built as discrete, independently operable services. Each function communicates over standardised interfaces rather than being locked inside a single monolithic application. This design gives IT and engineering teams significant flexibility when planning integrations. Because Empuls is delivered as a SaaS product, customers access these services through a well-documented public API, available via the Empuls SDK. This provides a controlled, secure entry point to embed Empuls capabilities inside other enterprise applications and portals without rebuilding the user experience from scratch. Embedding Empuls functions in your existing tools A practical example: an organisation using Microsoft Teams as its primary collaboration environment can surface Empuls recognition flows — peer nominations, milestone alerts, and reward redemptions — directly inside Teams channels and personal apps. Employees participate in recognition programmes without leaving their existing workflow. The same pattern applies to Slack, where Empuls bot interactions trigger and display recognition events in real time. For HR technology stacks, the SDK enables deeper connectivity with systems like SAP SuccessFactors, Workday, and Darwinbox. Employee lifecycle events — onboarding completions, work anniversaries, or performance review outcomes — can be passed from the HRIS to Empuls via API, automatically triggering rewards or recognition without manual administrator input. What “highly modular” means in practice Because Empuls is highly modular at the service layer, IT teams are not restricted to a single integration point. Organisations can expose only the functions relevant to their use case — for instance, connecting only the rewards catalogue and redemption service to an internal intranet portal, while keeping survey and analytics modules accessible exclusively through the Empuls web application. This selective exposure gives IT administrators fine-grained control over scope and integration surface area. All API access is governed by standard authentication and authorisation controls. Empuls maintains SOC 2 Type II and ISO 27001 certifications, ensuring the service infrastructure powering these APIs meets the compliance benchmarks IT and InfoSec teams require before extending any SaaS product into internal systems. Getting started with the Empuls SDK The Empuls SDK documentation covers authentication flows, available endpoints, rate limits, and webhook configuration. Teams building custom integrations — whether embedding a recognition widget in a company portal or syncing reward data with a data warehouse — work against the same public API Empuls uses internally, ensuring consistency and long-term reliability as the product evolves. Learn more: Empuls Help Centre — IT

HRIS integrations supported by Empuls

Learn how Empuls connects with Workday, SAP SuccessFactors, Darwinbox, and other HRIS platforms to automate recognition triggers from employee lifecycle events.

Slack and MS Teams integration with Empuls

Understand how to surface Empuls recognition and rewards workflows directly inside Slack channels and Microsoft Teams without leaving the collaboration tool.

SSO and SAML support in Empuls

Find out how Empuls supports single sign-on via SAML 2.0, enabling IT teams to manage access through existing identity providers.

Empuls security certifications and compliance

Review the security standards Empuls meets, including SOC 2 Type II and ISO 27001, and what they mean for enterprise data handling.