This article describes the available options for sending data from physical or virtual sensors to Gundi, along with the requirements and timelines associated with each integration path.
Gundi supports two integration models:
Push Model (your system sends data to Gundi)
Pull Model (Gundi retrieves data from your system)
Each model requires different information from you and follows a different onboarding process.
1. Integration Models
A. Push to Gundi (API-Based)
Your system sends data directly to Gundi using our API.
A complete API documentation article is available, covering authentication, payload formats, and implementation details.
You can begin testing immediately—no engineering coordination is required to get started.
Your system manages delivery timing, batching, retries, and error handling.
Recommended when:
You want to start quickly and control how and when your data is delivered.
B. Gundi Fetches Your Data (Pull-Based)
Gundi retrieves your sensor data using the endpoints or API your system already exposes.
Gundi does not provide a public API for configuring pull-based integrations.
These integrations require engineering work on our side, which must be scheduled in advance.
Depending on workload and prioritization, work may begin several weeks after your request.
Recommended when:
Your system already exposes data through a stable API and you prefer Gundi to retrieve it on a schedule.
2. Information Requirements by Integration Path
The information below is required before Gundi can evaluate or begin an integration.
Requirements are grouped into Must-Haves (required to proceed) and Nice-to-Haves (helpful but optional).
If You Are Pushing Data to Gundi (API-Based)
Must-Haves
Subtitle 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Subtitle 2
Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Nice-to-Haves
Subtitle 3
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.
Subtitle 4
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum.
Subtitle 5
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia.
If Gundi Is Fetching Data from Your System (Pull-Based)
Must-Haves
API Documentation
Authentication requirements, rate limits, supported filters, and schema definitions.
Credentials
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Nice-to-Haves
Endpoint Information
Base URL(s), available endpoints, required parameters, and expected response patterns.
Sample Responses
Real or representative JSON/XML responses for each type of data.
Authentication Requirements
Token, OAuth, IP allowlisting, or other access constraints.
Data Availability Timing
How often new data becomes available and any constraints on polling frequency.
Filtering Options
Supported filters such as ID filters, date ranges, or pagination.
Historical Data Access
Whether older records are available and relevant limitations.
Change Detection Mechanisms
Whether your system distinguishes new/updated records from full lists.
Load Guidelines
Recommended or required polling limits to avoid overloading your systems.
Subtitle 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Subtitle 2
Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Subtitle 3
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.
3. Timelines and Next Steps
API-Based (Push Model)
You may begin immediately using the API documentation article.
We can assist with payload validation, ingestion mapping, and provide direction on Event Types and related needs.
Pull-Based (Gundi Fetches Data)
Engineering work is required and must be scheduled.
Depending on current workload, the onboarding process may begin within several weeks.
Once the required information is received, Gundi performs an initial compatibility review and adds the integration to the engineering pipeline.