Two-way sync
Changes in Smartrecruiters or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Keep Smartrecruiters and YugabyteDB 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. YugabyteDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Jobs, Job Postings, Interviews, Offers in Smartrecruiters need to exist as queryable Materialized Views, Schemas, Sequences, CDC Streams in YugabyteDB 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 Materialized Views, Schemas, Sequences, CDC Streams in YugabyteDB with Jobs, Job Postings, Interviews, Offers 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.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Jobs, Job Postings, Interviews, Offers replicate into YugabyteDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in YugabyteDB, so hierarchy-driven logic and permissions don't drift.
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.
| Smartrecruiters objects | YugabyteDB objects | How this pairing syncs | |
|---|---|---|---|
| Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Databases and Keyspaces Top-level containers for the YSQL (Postgres-style) and YCQL (Cassandra-style) APIs respectively. | Users is specific to Smartrecruiters and Databases and Keyspaces to YugabyteDB — each maps to any object or custom field on the other side. | |
| Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Tables Distributed SQL tables split into tablets; the primary read and write targets. | Approvals is specific to Smartrecruiters and Tables to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Indexes Global secondary indexes maintained transactionally alongside table writes. | Candidates is specific to Smartrecruiters and Indexes to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Materialized Views Precomputed query results available in YSQL for read-side shaping. | Applications is specific to Smartrecruiters and Materialized Views to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Schemas Postgres-style namespaces in YSQL used to organize synced data. | Jobs is specific to Smartrecruiters and Schemas to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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). | Sequences ID generation objects relevant when syncing writes into YSQL tables. | Job Postings is specific to Smartrecruiters and Sequences to YugabyteDB — 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.
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 applied to YugabyteDB as a row-level write, with types converted between the two schemas.
DetectionChanges in YugabyteDB are captured at the source via change data capture — no polling loop against its API. Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartrecruiters–YugabyteDB connection.
Changes in Smartrecruiters or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Smartrecruiters or YugabyteDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Smartrecruiters or YugabyteDB record.
Track your Smartrecruiters ⇄ YugabyteDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Smartrecruiters and YugabyteDB.
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 Smartrecruiters and YugabyteDB 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 Smartrecruiters and YugabyteDB 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 Smartrecruiters and YugabyteDB: authenticate both systems, choose the objects to sync (such as Smartrecruiters's Users and Approvals), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. YugabyteDB: SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
YugabyteDB: A second, Cassandra-compatible API (YCQL) is available alongside YSQL on the same cluster. Smartrecruiters: Change tracking uses the Webhooks API (event subscriptions with a signing secret and callback logs) plus updated-after-style polling; there is no log-based change data capture. Stacksync's field mapping accounts for these differences between Smartrecruiters and YugabyteDB without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Smartrecruiters and YugabyteDB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Smartrecruiters and YugabyteDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Smartrecruiters–YugabyteDB integration in-house.
Yes — Stacksync ships production-grade connectors for both Smartrecruiters and YugabyteDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 429 integrations available for Smartrecruiters and YugabyteDB.