What Katana asks for
The Katana connection form asks for two values from TPS: your API URL and your API Key.
API URL: the API host TPS issued for your account, entered in full including https://, for example https://your-tps-api.example.com, with no path such as /api/v1 added.
API Key: the key TPS issued for the environment you are connecting (sandbox or production). Treat it like a password.
Find your credentials in TPS
Ask your TPS contact for your API host and API key for the environment you want to connect. TPS gives each client its own host, so your address is unique to your account. Sandbox and production use separate keys, and they are never interchangeable.
To check your credentials, sign in to the TPS API client portal. This is your API host with /portal added, for example https://your-tps-api.example.com/portal. In the portal you can review the API traffic on your account and manage sandbox credentials.
To confirm which client your key belongs to, open the Developer Center at /portal/docs in the same portal. It also shows the API documentation for your account.
In Katana, enter your full host in the API URL field and your key in the API Key field. Make sure the key matches the environment of the host: never use a sandbox key against production or the other way round.
Need help? Contact your TPS account manager.