Two-way sync
Changes in IBM Db2 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep IBM Db2 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. IBM Db2 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 Sequences, Tablespaces, Databases, Schemas in IBM Db2 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 Sequences, Tablespaces, Databases, Schemas in IBM Db2 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.
Records maintained in Smartrecruiters land as queryable Sequences, Tablespaces, Databases, Schemas in IBM Db2, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Approvals, Candidates, Applications, Jobs replicate into IBM Db2 where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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.
| IBM Db2 objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces separating synced data from application and system objects. | 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. | Schemas is specific to IBM Db2 and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables Primary read/write target for syncing rows with SaaS systems or other databases. | 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. | Tables is specific to IBM Db2 and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Read-only projections often used to expose curated slices to a sync. | 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. | Views is specific to IBM Db2 and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Indexes Support fast key lookups on sync match columns. | 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). | Indexes is specific to IBM Db2 and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Stored Procedures Existing business logic sometimes invoked as part of write paths. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Stored Procedures is specific to IBM Db2 and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Sequences ID generation relevant when external systems insert rows. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Sequences is specific to IBM Db2 and Offers 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.
DetectionChanges in IBM Db2 are captured at the source via change data capture — no polling loop against its API. Log-based CDC through IBM's replication tooling where licensed.
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 applied to IBM Db2 as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM Db2–Smartrecruiters connection.
Changes in IBM Db2 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever IBM Db2 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 IBM Db2 or Smartrecruiters record.
Track your IBM Db2 ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between IBM Db2 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 IBM Db2 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 IBM Db2 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 IBM Db2 and Smartrecruiters: authenticate both systems, choose the objects to sync (such as IBM Db2's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on IBM Db2: Log-based CDC through IBM's replication tooling where licensed; otherwise polling on timestamp or audit columns. 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 IBM Db2 side: Sequences, Tablespaces, Databases, Schemas, plus custom fields where IBM Db2 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 IBM Db2 and Smartrecruiters: Mirror people records into the database; One directory of record; Reporting and analytics on current data. Records maintained in Smartrecruiters land as queryable Sequences, Tablespaces, Databases, Schemas in IBM Db2, so internal apps and dashboards read live data instead of a periodic export.
IBM Db2: SQL via JDBC/ODBC/CLI drivers; optional REST endpoints in some editions. Authentication: Database credentials, typically backed by OS or LDAP authentication. 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 452 integrations available for IBM Db2 and Smartrecruiters.