Two-way sync
Changes in Elasticsearch or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Elasticsearch and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Elasticsearch is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Approvals, Candidates, Applications, Jobs in Smartrecruiters need to exist as queryable Index mappings, Aliases, Data streams, Ingest pipelines in Elasticsearch before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Index mappings, Aliases, Data streams, Ingest pipelines in Elasticsearch with Approvals, Candidates, Applications, Jobs in Smartrecruiters field by field, in real time. You decide which system owns which fields — Smartrecruiters typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Elasticsearch, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in Elasticsearch write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
Records maintained in Smartrecruiters land as queryable Index mappings, Aliases, Data streams, Ingest pipelines in Elasticsearch, so internal apps and dashboards read live data instead of a periodic export.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Elasticsearch objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Data streams Append-only targets for time-series or event data pushed from source systems. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Data streams is specific to Elasticsearch and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Ingest pipelines is specific to Elasticsearch and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Index templates is specific to Elasticsearch and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Indices is specific to Elasticsearch and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Documents The unit of sync; JSON records created, updated, and deleted by _id. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Documents is specific to Elasticsearch and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Index mappings Field type definitions that determine how synced fields are indexed and queried. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Index mappings is specific to Elasticsearch and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is written to Elasticsearch through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Smartrecruiters connection.
Changes in Elasticsearch or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Elasticsearch or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Elasticsearch or Smartrecruiters record.
Track your Elasticsearch ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Elasticsearch and Smartrecruiters.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Elasticsearch and Smartrecruiters with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Elasticsearch and Smartrecruiters objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Elasticsearch and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Elasticsearch's Data streams and Ingest pipelines), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Elasticsearch: Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Elasticsearch side: Index mappings, Aliases, Data streams, Ingest pipelines, plus custom fields where Elasticsearch exposes them. On the Smartrecruiters side: Approvals, Candidates, Applications, Jobs. 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 Elasticsearch and Smartrecruiters: Org and structure stay aligned; Computed and operational fields flow back; Mirror people records into the database. Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Elasticsearch, so hierarchy-driven logic and permissions don't drift.
Elasticsearch: REST API (JSON over HTTP). Authentication: API keys or basic authentication; Elastic Cloud also issues service account tokens. Smartrecruiters: SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions. Authentication: X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions. Stacksync manages authentication, retries, and rate limits on both sides.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 520 integrations available for Elasticsearch and Smartrecruiters.