This deployment publishes 59 endpoints
Across 11 groups, and this portal documents exactly that set — it is generated from the same content as the reference, so a route listed here is a route this API answers.
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. A call that works in one and 404s in the other is a version difference, not a bug in your client.
Moving over is a base URL and a key
Nothing about the flow changes: the same prepare, the same rail branching, the same submit and the same polling. Point the base URL at the other host and use a credential issued there.
There is no environment switcher here
Each deployment of this portal shows only its own hosts, examples and Swagger links. That is deliberate: a copyable sample that silently belongs to the other environment is worse than no sample.
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. Expect an unauthorized response rather than a helpful wrong-host error.