The API-First and Event-Driven Platform
Webhooks, event streams, and notifications let connected systems react while teams and customers stay informed without constant polling.
Scelto dai leader del settore. Progettato per operazioni complesse.
Come funziona?
Explore product API references, OpenAPI-compatible documentation, and release notes before writing integration code.
See your integration flow in action.
Bring the systems, API operations, and business events you need to connect.
Build faster with OpenAPI and SDKs
Generate API clients directly from OpenAPI-compatible documentation and integrate using the languages, tools, and workflows your development team already uses.
Use official SDKs for TypeScript and JavaScript on Node.js, Python, Java, and C#/.NET to reduce boilerplate and make integrations easier to build and maintain.
React to changes with business events
Tridens generates business events when the status of a payment, invoice, subscription, charging session, or charger changes.
Connected systems can use these events to trigger workflows automatically without repeatedly polling the API for updates.
Configure event-driven notifications
Choose which business events trigger notifications, apply filters, select receivers, and define delivery and retry rules.
When a matching event occurs, Tridens routes it to the right system, team, or customer through webhooks, email, SMS, push notifications, or logs.
Use APIs and events across Tridens products
Choose the product that matches your operation, then explore its capabilities.
Tridens Monetization
Connect customer, product, subscription, billing, payment, and revenue workflows with your existing stack. Use business events and notifications to keep downstream systems informed when states change.
Tridens Monetization docs
Carica EV Tridens
Connect charging infrastructure, charging sessions, customer applications, and external systems through APIs. Use configurable notifications to respond to charger, session, and customer events.
Tridens EV Charge docs
Domande frequenti
Still have questions?
What does API-first mean at Tridens?
API-first means that core platform operations are available through documented APIs, rather than being limited to the user interface. Development teams can integrate Tridens with existing systems, automate workflows, and build custom applications around the platform.
Tridens currently presents Monetization as an API-first platform with REST APIs and OpenAPI support.
Which operations are available through Tridens APIs?
Tridens APIs provide programmatic access to core operations supported by Tridens Monetization and Tridens EV Charge. Applications can use the product APIs to create, retrieve, update, and automate supported resources and workflows.
Can Tridens connect to our existing technology stack?
Yes. Tridens can connect with CRM, ERP, payment, tax, provisioning, analytics, accounting, customer-facing applications, and custom business systems through APIs and integrations.
This allows companies to keep the systems they already use instead of rebuilding their entire technology stack around Tridens.
Can we generate our own API client or use an official SDK?
Yes. Development teams can generate API clients from the OpenAPI-compatible documentation or use an official Tridens SDK.
Official SDKs are available for TypeScript and JavaScript on Node.js, Python, Java, and C#/.NET.
How are event-driven notifications configured?
First, select the event scope and action that should trigger the notification. Then apply filters, configure one or more publishers, select the receivers, and define how many delivery retries should be attempted if a notification fails.
When a matching event occurs, Tridens sends the configured notification to the selected destination. Monetization currently supports notification scopes around subscriptions, billing, rating, and exporting, while EV Charge supports events around charging infrastructure and charging sessions.
Which notification channels does Tridens support?
Tridens supports URL-based API requests, email, SMS, push notifications, and log notifications.
URL delivery can be used for machine-to-machine integration, while email, SMS, and push notifications can inform customers or operational teams. Log notifications can record when configured events are triggered.
What happens when notification delivery fails?
The number of retries can be configured for each notification publisher. If the first delivery attempt fails, Tridens retries the notification according to the configured rule.
The current product documentation confirms configurable retry counts, but does not publicly document broader guarantees such as event replay, guaranteed ordering, dead-letter queues, or at-least-once delivery.
Can the same event notify both systems and people?
Yes. A single notification rule can use different publishers and receivers to deliver information to multiple destinations.
For example, a payment event can send a URL-based API request to a CRM, an email to a customer, an SMS to an operations team, and a log entry for internal tracking. The precise combination depends on the available event scope and configured notification rule.