This portal documents 55 integration endpoints
The reference covers 10 groups. It excludes monitoring, internal and platform-owner-only routes. Check this deployment's Swagger for its full published API contract.
Environments
Validate against staging, then move the same flow to production.
What differs between deployments
Base URL
https://api.ugtp.io/v1Every path in this documentation is relative to https://api.ugtp.io/v1. Production metadata and examples do not expose staging hosts.
The two deployments are not interchangeable
They can publish different route sets while one is ahead of the other, so validate against the deployment you are going to ship to. If a route returns 404 in one deployment, check its Swagger and the requested path before assuming the route is available.
Moving over is a base URL and a key
Use the target environment's base URL and credentials, then verify its supported networks, tokens and API contract. Keep the prepare-sign-submit-poll flow and branch on the returned rail.
There is no environment switcher here
This portal's API URLs and Swagger links target one environment. Use that environment's credentials and catalog values when adapting an example.
Credentials do not cross over
A key issued on one deployment is not valid on the other, and a session JWT is scoped the same way. An environment mismatch can return an unauthorized response.