BarryS.04877 (Customer) asked a question.
Since the corresponding Okta connector function lacks the "expand" feature that I need, I am attempting to make a GET request using an API connector to the following API. This "expand" works in Postman and adds the app user's app profile to the results.
Works in Postman: GET {url}/api/v1/apps?filter=user.id+eq+"00u34REDACTEDu1d6"&expand=user/00u34REDACTEDu1d6&limit=200
I have tried every trick I can think of but only get Bad Request due to the query parameters.
1 - Compose query with and without Encode Query. In this image I had tried both output from Construct and output from Encode Query as input to Query on the API Connector.
2 - Various forms of the query as a string, with and without encoding, borrowed from Postman
3 - Try the API Connectory Query query box as both object and string, entering directly into the query box or running through compose, with and without encoding.
There seems to be no way to get the API connector to send the exact same request as sent by Postman. Does anyone understand what the API connector might be doing with the request and is there any way to correct the input?
@BarryS.04877 (Customer) - Seems to work fine for me:
The "inputs" on the construct could be fed in dynamically but I just did a static representation for simple demo.