Skip to content
Database ⇄ Human resources

OCI Database (Oracle Cloud) to Smartrecruiters integration — real-time, two-way sync

Keep OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) and Smartrecruiters

Put your workforce data where your apps can reach it: OCI Database (Oracle Cloud) 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. OCI Database (Oracle Cloud) is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Job Postings, Interviews, Offers, Users in Smartrecruiters need to exist as queryable JSON collections, Partitions, Tables, Views in OCI Database (Oracle Cloud) 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 JSON collections, Partitions, Tables, Views in OCI Database (Oracle Cloud) with Job Postings, Interviews, Offers, Users 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 Write changes from SaaS applications back into OCI so PL/SQL-based processes operate on current data.
  • 02 Replicate operational tables from OCI to an analytics warehouse with log-based CDC instead of nightly batch dumps.
  • 03 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
  • 04 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.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in OCI Database (Oracle Cloud) 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 JSON collections, Partitions, Tables, Views in OCI Database (Oracle Cloud), 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.

What you can sync between OCI Database (Oracle Cloud) 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.

OCI Database (Oracle Cloud) objects Smartrecruiters objects How this pairing syncs
Tables The primary sync surface; rows are read and written directly over SQL Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Tables is specific to OCI Database (Oracle Cloud) and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Views Read-only projections used to expose curated subsets to downstream systems 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). Views is specific to OCI Database (Oracle Cloud) and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Materialized views Precomputed result sets sometimes used as stable read sources for replication Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Materialized views is specific to OCI Database (Oracle Cloud) and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Schemas Namespace boundaries that scope which objects a sync connection can access Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Schemas is specific to OCI Database (Oracle Cloud) and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Sequences Key generators that matter when writing new rows from external systems 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. Sequences is specific to OCI Database (Oracle Cloud) and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place 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. PL/SQL procedures and packages is specific to OCI Database (Oracle Cloud) and Applications to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between OCI Database (Oracle Cloud) 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.

OCI Database (Oracle Cloud) Smartrecruiters Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

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

Smartrecruiters OCI Database (Oracle Cloud) 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 applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing 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 OCI Database (Oracle Cloud) ⇄ Smartrecruiters

Connect OCI Database (Oracle Cloud) and Smartrecruiters for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–Smartrecruiters connection.

Real-time

Two-way sync

Changes in OCI Database (Oracle Cloud) or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) or Smartrecruiters record.

Observability

Monitoring

Track your OCI Database (Oracle Cloud) ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and Smartrecruiters.

How the OCI Database (Oracle Cloud) and Smartrecruiters connectors work

OCI Database (Oracle Cloud)

Integration surface
SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
Authentication
database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing 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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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
    OCI Database (Oracle Cloud) connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the OCI Database (Oracle Cloud) 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 · OCI Database (Oracle Cloud) ⇄ 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
    OCI Database (Oracle Cloud) Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

OCI Database (Oracle Cloud) 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:

Coworkers laughing in front of a laptop in a casual office setting

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