Two-way sync
Changes in MarkLogic or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep MarkLogic 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. MarkLogic 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 Document Metadata & Properties, Databases & Forests, Users & Roles, Documents in MarkLogic 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 Document Metadata & Properties, Databases & Forests, Users & Roles, Documents in MarkLogic 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 MarkLogic, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in MarkLogic write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
Records maintained in Smartrecruiters land as queryable Document Metadata & Properties, Databases & Forests, Users & Roles, Documents in MarkLogic, 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.
| MarkLogic objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Databases & Forests Storage units that define the scope and placement of synced content. | 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). | Databases & Forests is specific to MarkLogic and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Users & Roles Security principals that govern what an integration credential can read or write. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Users & Roles is specific to MarkLogic and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Documents JSON and XML documents, the primary records read from and written to the database. | 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). | Documents is specific to MarkLogic and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Collections Named groupings used to scope which documents a sync reads or updates. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Collections is specific to MarkLogic and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Semantic Triples is specific to MarkLogic and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| TDE Views Relational projections of documents that let syncs read document data as SQL rows. | 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. | TDE Views is specific to MarkLogic and Candidates 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 MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.
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 MarkLogic as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MarkLogic–Smartrecruiters connection.
Changes in MarkLogic or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MarkLogic 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 MarkLogic or Smartrecruiters record.
Track your MarkLogic ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MarkLogic 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 MarkLogic 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 MarkLogic 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 MarkLogic and Smartrecruiters: authenticate both systems, choose the objects to sync (such as MarkLogic's Databases & Forests and Users & Roles), map fields visually, and changes propagate both ways in milliseconds — no code required.
MarkLogic: Template Driven Extraction (TDE) projects document content into rows that can be queried over SQL/ODBC, which simplifies warehouse-style reads. 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 MarkLogic and Smartrecruiters 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 MarkLogic and Smartrecruiters records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MarkLogic and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MarkLogic–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both MarkLogic and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on MarkLogic: No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup. 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.
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 438 integrations available for MarkLogic and Smartrecruiters.