Skip to content
Database ⇄ Human resources

RavenDB to Smartrecruiters integration — real-time, two-way sync

Keep RavenDB 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect RavenDB and Smartrecruiters

Put your workforce data where your apps can reach it: RavenDB and Smartrecruiters share the same people, positions, and org structure in real time.

Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. RavenDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Interviews, Offers, Users, Approvals in Smartrecruiters need to exist as queryable Attachments, Revisions, Counters, Time series in RavenDB 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 Attachments, Revisions, Counters, Time series in RavenDB with Interviews, Offers, Users, Approvals 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.

Common use cases

  • 01 Sync operational documents such as orders and profiles between RavenDB and a CRM so business teams see application data.
  • 02 Mirror reference data from relational systems into RavenDB collections that serve application reads.
  • 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
  • 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.

Common sync patterns

Mirror people records into the database

Records maintained in Smartrecruiters land as queryable Attachments, Revisions, Counters, Time series in RavenDB, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Interviews, Offers, Users, Approvals replicate into RavenDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between RavenDB and Smartrecruiters

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.

RavenDB objects Smartrecruiters objects How this pairing syncs
Counters Numeric values attached to documents that change independently of the document body Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Counters is specific to RavenDB and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Time series Timestamped measurements stored per document, synced for metrics analysis Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Time series is specific to RavenDB and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Data subscriptions Server-side change feeds that push matching documents to consumers 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. Data subscriptions is specific to RavenDB and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
Documents JSON records, the primary unit read and written during sync 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. Documents is specific to RavenDB and Applications to Smartrecruiters — each maps to any object or custom field on the other side.
Collections Groupings of documents by type, mapped to tables in relational targets 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. Collections is specific to RavenDB and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Indexes Static and auto indexes used to query documents for filtered reads 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 RavenDB and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between RavenDB and Smartrecruiters

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.

RavenDB Smartrecruiters Sub-second propagation

DetectionChanges in RavenDB are captured at the source via change data capture — no polling loop against its API. Data subscriptions and the Changes API provide server-pushed change feeds.

DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.

Smartrecruiters RavenDB Sub-second propagation

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 RavenDB through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • RavenDB: Throughput bounded by cluster resources rather than API quotas.
  • Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with RavenDB ⇄ Smartrecruiters

Connect RavenDB and Smartrecruiters for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every RavenDB–Smartrecruiters connection.

Real-time

Two-way sync

Changes in RavenDB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever RavenDB or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single RavenDB or Smartrecruiters record.

Observability

Monitoring

Track your RavenDB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between RavenDB and Smartrecruiters.

How the RavenDB and Smartrecruiters connectors work

RavenDB

Integration surface
HTTP REST API with official clients (.NET, Java, Node.js, Python, and others)
Authentication
X.509 client certificates on secured servers, instead of username and password
Change detection
data subscriptions and the Changes API provide server-pushed change feeds
Capabilities
read · write · CDC
Rate limits
throughput bounded by cluster resources rather than API quotas

Smartrecruiters

Integration surface
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
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
Smartrecruiters setup guide
How it works

How to connect RavenDB to Smartrecruiters — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate RavenDB 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    RavenDB connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the RavenDB 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · RavenDB ⇄ Smartrecruiters
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    RavenDB Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

RavenDB and Smartrecruiters integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 430 integrations available for RavenDB and Smartrecruiters.

Popular · 7 of 430
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.