Real-time
Two-way sync
Changes in Azure Cosmos DB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
Azure Cosmos DB to Smartrecruiters integration — real-time, two-way sync
Keep Azure Cosmos DB 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 Azure Cosmos DB and Smartrecruiters
Put your workforce data where your apps can reach it: Azure Cosmos DB 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. Azure Cosmos DB 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 Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB 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 Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB 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 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
- 02 Consolidate documents from multiple containers into a single reporting store.
- 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 Azure Cosmos DB 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 Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB, 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 Azure Cosmos DB 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.
| Azure Cosmos DB objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Databases Top-level namespaces that scope containers and throughput provisioning. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Databases is specific to Azure Cosmos DB and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | 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). | Containers is specific to Azure Cosmos DB and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Items (JSON documents) is specific to Azure Cosmos DB and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Partition keys is specific to Azure Cosmos DB and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | 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. | Change feed entries is specific to Azure Cosmos DB and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | 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. | Stored procedures and triggers is specific to Azure Cosmos DB and Applications to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Azure Cosmos DB 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.
Azure Cosmos DB Smartrecruiters Sub-second propagation
DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Azure Cosmos DB 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 Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- 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 Azure Cosmos DB ⇄ Smartrecruiters
Connect Azure Cosmos DB and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Cosmos DB 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 Azure Cosmos DB or Smartrecruiters record.
Observability
Monitoring
Track your Azure Cosmos DB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Smartrecruiters.
How the Azure Cosmos DB and Smartrecruiters connectors work
Azure Cosmos DB
- Integration surface
- REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
- Authentication
- Account keys, resource tokens, or Microsoft Entra ID role-based access
- Change detection
- Built-in change feed exposing inserts and updates in order within each partition key range
- Capabilities
- read · write · CDC
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.
How it works
How to connect Azure Cosmos DB 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.
- 01
Connect your apps
Authenticate Azure Cosmos DB 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.
Azure Cosmos DB
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Cosmos DB 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.
objects · Azure Cosmos DB ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Azure Cosmos DB SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Cosmos DB and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Databases and Containers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Azure Cosmos DB: Throughput is provisioned in request units per container or database, which means sync read and write volume has a direct cost and throttling dimension. 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 Azure Cosmos DB 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 Azure Cosmos DB and Smartrecruiters records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Cosmos DB and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Cosmos DB–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Cosmos DB and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. 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.
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 438 integrations available for Azure Cosmos DB and Smartrecruiters.
Popular · 8 of 438
-
Azure Cosmos DB ⇄ Ukg Ready -
Azure Cosmos DB ⇄ BambooHR -
Azure Cosmos DB ⇄ Success Factors -
Azure Cosmos DB ⇄ Hibob -
Smartrecruiters ⇄ TimescaleDB -
Smartrecruiters ⇄ VoltDB -
Smartrecruiters ⇄ YugabyteDB -
Smartrecruiters ⇄ Amazon DynamoDB
No integrations match .
