Pulse integrations connect operational data from source systems to a Pulse tenant using an industry-specific domain model.
A model defines the resources, relationships, and integration flow used to represent the source data in Pulse.
Integration principle
Pulse does not generate operational data. It produces analysis from the data provided by connected source systems.
A successful integration therefore depends on supplying Pulse with complete, correctly mapped, and meaningful business data.
The integration should be simple and robust to implement, but technical correctness alone is not enough. The integrator must also understand the business meaning of the source data and how it maps to the Pulse domain model.
Integration process
A typical integration follows this sequence:
1. Configure the Pulse tenant
Before starting the data integration, the required Pulse tenant must be provisioned and made available for the selected model.
See Configure a production tenant.
2. Configure authentication
Authenticated API requests use a Bearer token.
See Authentication.
3. Follow the domain model-specific integration guide
Choose the domain model configured for the Pulse tenant:
The model documentation explains the available resources, relationships, integration options, submission order, and examples.
Integration options
Pulse supports several ways to integrate operational data:
- REST API for direct programmatic integration over HTTP.
- .NET client for automated integrations from .NET applications and services.
- Excel template for file-based data preparation and import. Download the Excel template specific to your domain model here.
The available resources and data structures are defined by the domain model configured for the Pulse tenant.
Refer to the selected domain model documentation for model-specific guidance and examples.
API reference
Use the OpenAPI specification for the exact API contract, including endpoints, request fields, parameters, schemas, responses, and supported operations.
Where available, the Scalar interface can be used to browse and test the API interactively.