Custom Connector returns 502 despite API working in Flows

(2) Share

Report

Posted on by bobesponja

258

I'm trying to set up a custom connector for a REST API I'm using in Power Apps so we don't have to use Flows anymore. Calls to this API using the HTTP connector in Power Automate work fine, but when I try to recreate those same calls as a custom connector, I consistently get "Operation failed (502), see response below" like in this screenshot.

This happens regardless of whether I import the API as a Postman collection or try to start from scratch (the screenshot above is from a smaller test connector I made that just uses 1 of the available functions). Tests for this connector always return the same result seen above regardless of what values (if any) are given in the query parameters. We do not host or have creative privileges over the API because it is hosted by another business, so I cannot make any CORS changes. The API doesn't have any public documentation that I'm aware of, so I cannot publicly post the Swagger setup for the connector. What do I do?

Categories:

Authentication

I have the same question (1)

All responses (1)

Answers (0)

NK-03111010-0 3 on at

Like (0)

Report

Custom Connector returns 502 despite API working in Flows

We have the same problem now, we configured enterprise policies for being able to connect to from the custom connector to our vnet in Azure through subnet injection. But testing the custom connector always ends up with 502, whatever we configure. Is there some networking issue with the APIM that is being hit from the custom connector?

Was this reply helpful? Yes No