One other question @alex-w - the behavior of the Test URL is different that the API Resource in terms of display. If I have a Base URL that looks like in https://www.example.com/api/v1/search, in the app API Resource editor, your team is appending a “/” at the end of the url, e.g. https://www.example.com/api/v1/search/ and it’s clear that I do not need to prepend the / before the route. So, if I am setting up a Query to hit my ping route in the app, all I would need to do is add ping to the input box.
For the Test URL, the trailing “/” is not appended to the Base URL, so I’m not sure if I should be inputting /ping or ping
In either case, when I’m using the button below, I am able to authenticate, but there’s no success message or anything like that to tell me if it truly worked. I’m also not seeing calls to my backend logs for this endpoint. Sorry, just not sure what I’m missing here!