Custom Connector:404 Error while Generate Token API

(0) Share

Report

Posted on by CU06030855-0

Hi Team,

I am trying to implement the canvas app login using IDP. We have a generate token API which is working fine when tested in Postman, but giving 404 error when tested in PowerApps Custom Connector.

Also the request URL which i am providing in the definition while defining the custom connector is getting changed when i test it. It's giving similar like this- "azure-apihub.net/apim".

Custom Connector Details-

No Authentication, also provided the request body parameters same as given in Postman with no header.

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (0)

Sort by

MS.Ragavendar 6,616 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

Ensure the Base URL in the connector definition is exactly what your API expects.

Postman might auto-generate headers (like Content-Type: application/json), but in Powerapps i dont think so, please explicitly adding Content-Type: application/json in the Headers section of your Custom Connector.

If the connector still does not work, try calling the API via Power Automate and return the response to PowerApps.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item

Was this reply helpful? Yes No
CU06030855-0 4 on at

Like (0)

Report
Copy link

Link copied!

Thanks @MSR@08012015 for your quick reply, I have checked the base URL and also added header as Content-Type. Still i am getting same error. Also the URL which i am passing in the connector definition is automatically getting changed something similar to this- "azure-apihub.net/apim" when i am testing it. Is there anything related to azure-apim which needs some setup or policy change etc.

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 6,616 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

If your request URL is automatically changing to something like azure-apihub.net/apim, it means your Custom Connector is routing through APIM instead of your actual API endpoint.

Azure API Management (APIM) → APIs → Your API and check:

Is your API actually registered in APIM?

Is APIM changing the request headers or URL?

To further check redirection is happening

Edit your Custom Connector and update the Base URL to the exact API URL you used in Postman.

Power Apps enforced the changes again means somewhere the redirection policy is set in APIM.

How to Check

Go to APIM → APIs → Your API → Inbound Processing.

Check if there are any URL rewrites or authentication policies.

Look for any rewrite-uri or set-backend-service policies and adjust them

Create a simple HTTP Request in Power Automate. If it works in Power Automate but not in Power Apps, then we can raise a ticket with Microsoft Support Team.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item

Was this reply helpful? Yes No