Connect Union Pacific API Credentials to Terminal49
Last updated: October 16, 2026
Connect your Union Pacific (UP) API credentials to retrieve rail shipment data in Terminal49. This connection uses the App Id and Secret Key issued by UP. Do not enter your UP customer portal username or password into Terminal49.
Before you start
You need a UP (MyUPRR) user ID and password to request API access from UP. Your company’s UP account administrator can help if you do not already have access.
UP must authorise the API identity and the shipment data, roles, and locations it can access. A working portal login alone does not establish API access.
Intermodal Rail must be enabled on your Terminal49 account. Contact sales@terminal49.com if you need to enable it.
1. Request API credentials from Union Pacific
Start at the Union Pacific API Developer Center.
Open Register as a Developer / API registration and sign in with your UP user account. The UP API documentation also requires a UP login.
Request a company API application for connecting Union Pacific shipment visibility to Terminal49. Ask UP to confirm the API services and shipment data access needed for your account, including any required roles or authorised locations.
Complete UP’s authorisation process and obtain the application’s App Id and Secret Key. Confirm with UP that the credentials are approved for production use before adding them to Terminal49.
2. Whitelist Terminal49’s IP addresses in UP
Add all four entries to the IP whitelist for the UP API application used by Terminal49:
3.230.67.145/32
44.217.15.129/32
54.145.240.98/32
13.216.219.126/32Save the whitelist changes before connecting. If you cannot find the whitelist setting or do not have permission to update it, ask your UP administrator or UP API Support to add these entries to your application.
3. Add the credentials to Terminal49
Open Settings → Data Sources in Terminal49.
Select Union Pacific and enter the API credentials using this mapping:
Username: your UP App Id
Password: your UP Secret Key
Save the connection.
The fields are labeled Username and Password in Terminal49, but they must contain the UP API application credentials. Your UP portal login credentials will not work for this connection.
If you cannot connect or shipment data is missing
Confirm that the App Id and Secret Key belong to the same approved UP application and were copied without extra spaces.
Check that all four Terminal49 IP entries are saved on that application’s whitelist.
Ask UP to confirm production access and the roles, accounts, and locations authorized for the shipments you expect to see.
If the Secret Key changes, update the Password field in Terminal49.
Contact Terminal49 support with the error message if the issue continues. Do not include your Secret Key in a support message.