An ingress endpoint is a receiving location where an external system can push data into IMSURGE. The sending system may be a sensor, device, gateway, or third-party cloud service.

Ingress endpoints are used when the external system sends data to IMSURGE directly, instead of IMSURGE polling that system on a schedule.

Ingress endpoints are commonly used by data push integrations.

How Ingress Endpoints Change Pipeline Execution

Different types of source integrations have different execution requirements. For API pull methods, pipelines have a polling frequency and reach out on a schedule to collect new data.

For integrations that use an ingress endpoint, data flow works the other way around. The source sensor or service pushes data directly to IMSURGE as it becomes available. Executions occur when that sensor or service pushes data to the ingress endpoint.

Some integrations with ingress endpoints can still be manually executed. Manual execution is usually used to collect historical data because direct push methods often only send current or future data.

Integration Endpoints and Credential Endpoints

An ingress endpoint can be attached directly to an integration, or it can be attached to credentials used by one or more integrations.

Integration Ingress Endpoints

An integration ingress endpoint belongs to one specific integration.

This is used when each source device or sensor needs its own receiving configuration. For example, each sensor may be configured to send data to its own endpoint so IMSURGE can sort incoming data by the endpoint that received it.

Data pushed to an integration ingress endpoint only triggers pipelines that use that integration.

Credential Ingress Endpoints

A credential ingress endpoint belongs to a set of credentials.

Any integration that uses those credentials inherits the credential’s ingress endpoint. When data is pushed to that endpoint, pipelines using integrations that inherit the endpoint can execute at the same time.

This is common when a third-party service platform sends all data to one endpoint and includes the sensor or device identifier inside the message body. IMSURGE receives the message first, then sorts the data after receipt.

Supported Endpoint Methods

IMSURGE supports these ingress endpoint methods:

Method Status Use case
HTTP Available Webhooks, device uploads, vendor exports, or any source that can send an HTTP POST request.