Two-way sync
Changes in Smartrecruiters or StarRocks instantly reflect in both systems. No stale data, no manual imports.
Keep Smartrecruiters and StarRocks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Smartrecruiters is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in StarRocks next to everything else the company measures.
Stacksync syncs Job Postings, Interviews, Offers, Users from Smartrecruiters into tables in StarRocks continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in StarRocks, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Smartrecruiters where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
People and organization records from Smartrecruiters arrive in StarRocks as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine Smartrecruiters's workforce records with finance, product, or operational data already in StarRocks for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
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.
| Smartrecruiters objects | StarRocks objects | How this pairing syncs | |
|---|---|---|---|
| Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Materialized views Automatically maintained rollups used to accelerate queries on synced data. | Interviews is specific to Smartrecruiters and Materialized views to StarRocks — each maps to any object or custom field on the other side. | |
| 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 Logical views for shaping analytical reads. | Offers is specific to Smartrecruiters and Views to StarRocks — each maps to any object or custom field on the other side. | |
| Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Partitions Time or range partitions that scope loads and retention. | Users is specific to Smartrecruiters and Partitions to StarRocks — each maps to any object or custom field on the other side. | |
| Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Columns Columnar storage with types mapped from source systems during sync. | Approvals is specific to Smartrecruiters and Columns to StarRocks — each maps to any object or custom field on the other side. | |
| 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. | Databases Top-level namespaces addressed exactly as in MySQL clients. | Candidates is specific to Smartrecruiters and Databases to StarRocks — each maps to any object or custom field on the other side. | |
| 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. | Tables Defined with a table model (Primary Key, Unique Key, Aggregate, Duplicate Key) that determines update behavior. | Applications is specific to Smartrecruiters and Tables to StarRocks — 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.
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 StarRocks as a row-level write, with types converted between the two schemas.
DetectionStacksync polls StarRocks for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling when reading.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartrecruiters–StarRocks connection.
Changes in Smartrecruiters or StarRocks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Smartrecruiters or StarRocks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Smartrecruiters or StarRocks record.
Track your Smartrecruiters ⇄ StarRocks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Smartrecruiters and StarRocks.
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 Smartrecruiters and StarRocks 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 Smartrecruiters and StarRocks 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 Smartrecruiters and StarRocks: authenticate both systems, choose the objects to sync (such as Smartrecruiters's Interviews and Offers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Smartrecruiters and StarRocks: HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else; Fresh data instead of last night's load. People and organization records from Smartrecruiters arrive in StarRocks as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Smartrecruiters: 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. StarRocks: MySQL wire protocol for SQL; HTTP-based Stream Load API for ingestion. Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
StarRocks: The Primary Key table model supports real-time upserts and deletes, which suits applying change streams from operational systems. Smartrecruiters: Rate limits apply per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), with a separate concurrency limiter of up to 8 simultaneous requests and GET /candidates capped at 1; breaches return 429. Stacksync's field mapping accounts for these differences between Smartrecruiters and StarRocks 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 Smartrecruiters and StarRocks records are not retained after a sync operation.
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 434 integrations available for Smartrecruiters and StarRocks.