Skip to content
Database ⇄ Human resources

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

Keep Reltio 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 Reltio and Smartrecruiters

Put your workforce data where your apps can reach it: Reltio 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. Reltio 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 Entities, Relations, Crosswalks, Interactions in Reltio 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 Entities, Relations, Crosswalks, Interactions in Reltio 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.

Common use cases

  • 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 03 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
  • 04 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.

Common sync patterns

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Reltio, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Reltio write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Smartrecruiters land as queryable Entities, Relations, Crosswalks, Interactions in Reltio, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Reltio 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.

Reltio objects Smartrecruiters objects How this pairing syncs
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. 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. Matches (Potential Matches) is specific to Reltio and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. 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). Activity Log is specific to Reltio and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Data Change Requests (DCR) is specific to Reltio and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. 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). Reference Data (RDM) is specific to Reltio and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Entities is specific to Reltio and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Relations is specific to Reltio and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between Reltio 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.

Reltio Smartrecruiters Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

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

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • 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 Reltio ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio 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 Reltio or Smartrecruiters record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Reltio and Smartrecruiters connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

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 Reltio 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 Reltio 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
    Reltio connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio 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 · Reltio ⇄ 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
    Reltio Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Reltio 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 431 integrations available for Reltio and Smartrecruiters.

Popular · 8 of 431
Coworkers laughing in front of a laptop in a casual office setting

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