TM API URLs and Authentication Unified with Fenergo SaaS Platform
Transaction Monitoring APIs route through the unified Fenergo SaaS API gateway (TMProxy) and share the same OAuth 2.0 authentication flow as CLM and other Fenergo SaaS APIs. Integrators with existing Fenergo SaaS credentials can call TM APIs without a separate authentication setup.
API Base URL Change
TM API server URLs have moved from sentinels.cloud service endpoints to the standard Fenergo SaaS API gateway, following this pattern:
https://api.{region}.fenergox.com/tm/<service>
Replace {region} with your tenant's region identifier (e.g. emea1b). For the default EMEA tenant, the region segment can be omitted:
https://api.fenergox.com/tm/<service>
The <service> segment identifies the TM API being called (for example, realtime for the Transaction API or observability for the Observability API). The full URL for each operation is shown in the corresponding API specification page.
This aligns TM with the rest of the Fenergo platform — TM API traffic flows through the same infrastructure as CLM and other SaaS APIs, including the same network policies, rate limiting, and observability tooling.
Authentication
Transaction Monitoring APIs use the OAuth 2.0 Client Credentials flow, the same as all other Fenergo SaaS APIs. Credentials already configured for CLM or another Fenergo SaaS API are fully compatible with TM — the same client_id, client_secret, and token endpoint apply across all services.
Authentication works by exchanging credentials once for a short-lived Bearer token, which is then passed in the Authorization header of every API request. Advanced options such as mTLS are also supported.
See Fenergo SaaS API Authentication for the full authentication reference, including mTLS endpoints and regional token URLs.