Two-way sync
Changes in DEAR Inventory or Splunk instantly reflect in both systems. No stale data, no manual imports.
Keep DEAR Inventory and Splunk in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether DEAR Inventory carries financials, operations, workforce data, or all three, those numbers belong in Splunk, next to the product, behavioral, and web data the team already measures.
Stacksync syncs Purchase orders, Customers, Suppliers, Stock adjustments and transfers from DEAR Inventory into Splunk continuously, handling API limits and schema drift as it goes, so each record type arrives as Users and Roles, Dashboards, Search Results, Saved Searches ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Splunk can be written back to fields in DEAR Inventory where that is useful.
Operational records from DEAR Inventory become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.
Worker and organization data from DEAR Inventory syncs into Splunk for headcount, cost, and utilization reporting alongside other company data.
Segments, scores, or metrics computed in Splunk sync onto the matching records in DEAR Inventory, so operations act on what the analysis found.
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.
| DEAR Inventory objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Purchase orders is specific to DEAR Inventory and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Customers Buyer records aligned with CRM and accounting counterparts. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Customers is specific to DEAR Inventory and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Suppliers Vendor records referenced on purchase orders. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Suppliers is specific to DEAR Inventory and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Stock adjustments and transfers Inventory movement transactions that explain changes in availability. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Stock adjustments and transfers is specific to DEAR Inventory and KV Store Collections to Splunk — each maps to any object or custom field on the other side. | |
| Assemblies / Production Bill-of-material and production records for light manufacturing workflows. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Assemblies / Production is specific to DEAR Inventory and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Locations Warehouses and bins that scope stock levels and fulfillment. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Locations is specific to DEAR Inventory and HTTP Event Collector to Splunk — 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.
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
DeliveryEach detected change is written to DEAR Inventory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DEAR Inventory–Splunk connection.
Changes in DEAR Inventory or Splunk instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DEAR Inventory or Splunk data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DEAR Inventory or Splunk record.
Track your DEAR Inventory ⇄ Splunk sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DEAR Inventory and Splunk.
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 DEAR Inventory and Splunk 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 DEAR Inventory and Splunk 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 DEAR Inventory and Splunk: authenticate both systems, choose the objects to sync (such as DEAR Inventory's Purchase orders and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Splunk side: Users and Roles, Dashboards, Search Results, Saved Searches, plus custom fields where Splunk exposes them. On the DEAR Inventory side: Purchase orders, Customers, Suppliers, Stock adjustments and transfers. Stacksync auto-detects both schemas and converts types between the two systems.
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 DEAR Inventory and Splunk: Where DEAR Inventory runs operations: inventory and fulfillment metrics; Where DEAR Inventory is the HR system of record: workforce and cost analysis; Write-back where DEAR Inventory exposes writable fields: segments and scores return. Operational records from DEAR Inventory become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.
DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.
Splunk: Splunk exposes two API surfaces: the management REST API (default port 8089) for search jobs, saved searches, KV Store, indexes, users, and roles, and the HTTP Event Collector (default port 8088, port 443 on Splunk Cloud) for pushing events and metrics in — so the connector both reads from and writes into Splunk. DEAR Inventory: DEAR Systems was acquired by Cin7 and the product now operates as Cin7 Core; the API and data model carried over from DEAR. Stacksync's field mapping accounts for these differences between DEAR Inventory and Splunk without custom code.
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 380 integrations available for DEAR Inventory and Splunk.