I have reviewed the contracts available on Swagger and the documentation you referenced earlier. Based on this analysis, here are the key implementation requirements:
Use the correct authentication endpoint: Use the api/auth/v1.0/token method for token acquisition. The encoded key-secret value must be passed in the x-authorization header exactly as-is (do not add "Basic" prefix).
Handle the Bearer token properly: The response will contain a Bearer token. You must extract this token and use it for all subsequent API calls.
Configure the Authorization header correctly: Pass the obtained token in the Authorization header. The value must start with "Bearer " followed by a space. Format: Bearer XXX.
Important: You need to use different headers (x-authorization vs Authorization) depending on the authentication step you're currently executing.
Additional notes:
When navigating to https://uat.mydupr.com/api/swagger-ui/index.html#/Authentication/login, use the highlighted URL (e.g., POST /auth/{version}/token) in the WebRequest's Path field. Ensure you populate all required fields (in this case, the version parameter) before execution.
Configure your connector with the base path (https://uat.mydupr.com/api/) to eliminate redundant URL path segment duplication across WebRequests.
Validation step: Use Preview mode in EasyMorph WebRequest to compare your generated request against the one you create in Swagger. This will ensure accuracy.
Thank you @ckononenko. This worked well.
To use the token I had to add Bearer infront of the token.
I appreciate it that you took the time to sort this one for me.