- My goal: I want to create UPS as a resource. Authenticate with it over API to be able to generate shipping labels.
- Issue: I cannot seem to get the authentication to work.
- Steps I've taken to troubleshoot: I have created my app on the developer side of up. I have created a resource in retool and attempted many configurations to get them to communicate with UPS. There is some useful documentation here However, due to the nature of the desired authentication I think I need a custom auth. I simply cannot figure out from the postmaster example and the documentation the exact configuration. I have tried many. I believe the sequence should be get oauth authorize and then post auth token but the authorization header I think is wrong and I am getting a missing UUID error.
- Additional info: (Cloud or Self-hosted, Screenshots) Cloud
Hello @Laith_Charles,
Can you share a screenshot of how you have your resource and authentication set up?
I would imagine that custom auth or OAuth are viable possibilities. Can you share a screenshot of the error? You may need to check with their support team to get more details on why your attempts to auth into the app is missing a UUID 
The main issue always seems to be around my authorization headers. I have tried oauth2.0 both client credentials and authorization code. I have tried basic authorization and I have tried a custom auth. Usually to configure a resource with retool oauth2.0 is the normal method and you use the magic bearer string. Once I get things configured far enough most of them seem to stop here with this error.
Hi @Laith_Charles,
That is a very odd error message, a 500 Internal Server Error is a generic HTTP status code indicating that a website's server encountered an unexpected condition that prevented it from fulfilling a request.
This error signifies a problem on the server side, rather than an issue with the user's internet connection or browse. It sounds like you tried a number of auth options with none of them working, not sure if this is a Retool side issue or if this is a known response that UPS might have further details about how to remedy 
I've had (and still have) the same issue with the UPS API. Although the authentication is a standard method I can't get the flow to work with Retool. With postman the same flow is working fine.
It has been a while since I gave up on this. Let me check which error I was facing.
I guess I solved my own issue. See below:
One of the issues was in the post request which had /token in the url this was actually being replaced by my token despite the variable names being different so I kinda hacked it to use a variable name. The environment variable is my calculated base64(username:password) which are the client id and client secret.
1 Like