Map the events you already have
File, REST, CSV, webhook, database and stream ingestion, with customer-defined event types and mapped fields.
For Technical owner
Your stack. Your schemas. A clear integration path.
Bring your events into SENTR without redesigning the business around a vendor’s data model. Map fields, backfill history and test the decision response with the people building the platform.
An API is the start of the integration conversation.
Integration risk lives in the details: stable identifiers, history, retries and what happens when a decision comes back. We work through those details with you before production access—not after the commercial decision.
Keep the architecture understandable.
Explore the capabilities behind the promise, then put them to work on your own questions.
Test without changing production
A provisioned sandbox supports integration testing. Optional Shadow Mode consumes agreed events without enforcing SENTR decisions in production.
Verify current availability
Request API documentation and scoped credentials for your integration. Automated provider mapping remains in development. SENTR 360 journey reconstruction is available with the JavaScript SDK.
Picture the work in practice.
One mapping, two deployment stages
In an illustrative PSP evaluation, payment and payout events carry stable merchant identifiers into SENTR. The first stage compares outcomes read-only.
- Map payment + payout
- Stable merchant IDs
- Read-only compare
- Reuse mapping later
The evaluation should reduce integration uncertainty, not postpone it.
Not your decision alone? Prepare a team brief.
Take the relevant links into your internal discussion. No signup, no email gate. These links use the public website address.
Bring a schema. Let’s work through the integration.
Bring the question that determines your next decision. Request a focused conversation—or take the evidence links into your team’s discussion first.