ComboSync v2 Overview

ComboSync v2 Overview

ComboCurve

ComboSync v2 Overview

A software service to hide the REST API integration — standalone, no-code-on-the-customer solution for integrating client and public subscription data in and out of ComboCurve

ComboSync v2 is a standalone, no-code-on-the-customer solution which integrates client and public subscription data in and out of ComboCurve.

Why ComboSync?

Challenge

  • Customers have limited time & resources to support integration
  • Changing data landscape — what happens when a new data source is added?
  • New business needs require constant adaptation

Solution

  • An automated utility to sync client in-house data and publicly sourced data into ComboCurve
  • Customers only need to provide a view to their database — we handle all data ingestions

Benefits

  • ComboCurve knows its data and integration points
  • Guaranteed data flow between ComboCurve and the client's database
  • Low implementation cost with no in-house development time required
  • Faster data changes

Sustainability

  • Support for future data requirements
  • Continuous improvements with data agent updates
Solution Components
Agent

ComboSync Agent

A service that processes data pipelines and ensures the flow of data from source to target. The service is managed by the ComboSync Backend.

Backend

ComboSync Backend

The cloud service manages the definition and scheduling of the data pipelines. The service doesn't process data — it only controls the ComboSync Agents and their work.

Networking Diagram
Architecture

Component Networking Overview

How ComboCurve IET, the ComboSync Backend, the Agent Service, and external data sources interact across the network.

Data services ComboCurve IET Managing pipelines ComboSync Backend API Managing agents (NO Data) ComboSync Agent Service Data SQL Local database Data ComboCurve API Enverus IHS SQL ... mongoDB ComboCurve DB ComboCurve App
Implementation Overview
Architecture


Data Flow Diagram

End-to-end flow of data between client sources, the ComboSync platform, and ComboCurve — including ingestion views, sync utility, and output tables.

Client
Data Source(s):
  • Enverus
  • IHS (SPGCI)
  • CSV
  • MySQL
  • Excel
  • PostgreSQL
  • Snowflake
  • Databricks
  • MongoDB
  • Oracle DB
  • SFTP
  • SQL Server
  • API
  • SOTAOG
  • Google Storage
  • ZdScada
  • Local / Network Storage
»
ComboSync
01Data
ComboCurve Ingested Views:
  • Well Header
  • Production Data (Daily/Monthly)
  • Directional Surveys
  • Ownership
  • Project Level Econ Models
02Sync Utility
Data Push »
04Output
ComboCurve Destination Tables
«
Data Pull
« Data Pull
»
ComboCurve
03
REST API's
  • Scenarios
  • Forecasts
  • Economics
01

Client builds SQL views to align with ComboSync ingestion views, then deploys the resulting output tables

02

Client installs the ComboSync Agent — ComboCurve then configures and sets ingestion schedules

03

Run Forecasts and Economics

04

Process data in existing workflows

End User Analyses
«
Data Pull return
Connectors

Supported Connectors

All data sources and targets supported by the ComboSync integration platform.

ComboCurve

  • ComboCurve API Resources

Public Sources

  • SPGCI (formerly IHS Energy)
  • Enverus
  • ARIES Petroleum Economics
  • Scout
  • TGS
  • Well Database API
  • ZdScada

SQL

  • MS SQL Server
  • Oracle
  • PostgreSQL
  • MySQL
  • OLE DB
  • Snowflake
  • AWS Redshift

No SQL

  • MongoDB

File Storages

  • AWS S3
  • Azure Blob Storage
  • Google Cloud Storage
  • SFTP
  • Shared Folders
  • Local Files

File Types

  • CSV
  • Excel
  • JSON
Security

Networking — Required Outbound Traffic

The ComboSync Agent requires outbound access to the following addresses. Ensure these are allowlisted in your network configuration.

Data SourceAddress
ComboSync Backend (required)syncapi.combocurve.com:443
ComboCurve APIapi.combocurve.com:443
Enverus / Drilling Info V3api.enverus.com/v3
Enverus / Drilling Info V2di-api.drillinginfo.com/v2
Enverus: BI Connectbiconnect.enverus.com:443
SPGCI RestApienergydataservices.ihsenergy.com:443
Scoutstaging.fdc.io:443
Well Database APIapp.welldatabase.com:443
ZdScadazdscada.com:443
Other Data Sources
Security

Customer Credentials

How credentials are handled depends on the customer's authentication setup:

Standard Authentication — If the customer is not using Integrated Security, database credentials (username and password) are stored in the ComboSync Backend. These credentials are encrypted and stored securely, with the ComboSync Backend using strict permissions to access them.

Integrated Security — If the customer uses a domain Windows service account and a domain security group, Integrated Security can be enabled. In this case, no database username or password is stored — authentication is handled entirely through the domain security group, eliminating the need to manage or store database credentials in the ComboSync Backend.

For any additional questions or concerns, please reach out to support@combocurve.com


    • Related Articles

    • ComboCurve: Carbon Network Overview

      Modeling Basics Carbon networks are composed of nodes and edges. Each node represents a point where a calculation occurs in the network, while edges indicate which nodes are related and what time series data is passed from node to node. Some nodes ...
    • ComboSync SPGCI Connector

      ComboCurve™ S&P Global Commodity Insights (SPGCI) Connector ComboSync connector mapping and dataflow documentation for SPGCI data sources Recommended Mapping Overview Connector Mapping SPGCI → ComboCurve Entity Mapping The following table describes ...
    • ComboSync Connector

      ComboCurve™ Available ComboSync API Endpoints Supported ingestion and extraction endpoints available through the ComboSync integration platform Ingestions Push Data Into ComboCurve These are the items we can ingest into ComboCurve from client source ...
    • ComboSync Auto-Update Feature

      ComboSync Agent Auto Update Introduction An automatic update feature is preferred. There is no action needed on the customer side. The update will be performed automatically. If the ComboCurve support team detects any auto-update issue, they will ...
    • ComboSync Enverus Connector

      ComboCurve™ Enverus Connector ComboSync connector mapping and dataflow documentation for Enverus data sources Supported Enverus APIs Connector Enverus Data Sets The Enverus connector supports two data set families, each accessed through a different ...