'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Power Automate Custom Connector Request Rejected (HTTP 200)
Question details
The user needs to resolve an issue where a Power Automate custom connector returns an HTTP 200 success status, but the response payload indicates that the requested URL was rejected.
- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Executing an API request through a custom connector in Power Automate.
- Observed behavior
- The custom connector returns an HTTP 200 status code, but the response body states the requested URL was rejected, whereas the exact same API request works perfectly in Postman and Python.
Ensure you have the exact working Postman request details, headers, and the OpenAPI definition for your Power Automate connector open for a side-by-side comparison.
Compare Power Automate Request with Working Postman Request
Identify discrepancies between the failing Power Automate connector and the successful Postman request by verifying all URL components, authentication methods, and headers.
Many API gateways and endpoints are sensitive to missing headers, extra slashes, or specific encoding types. Postman often adds hidden headers automatically, which may need to be explicitly defined in your custom connector.
Check that the base URL and endpoint path in the Power Automate connector exactly match the working Postman setup, avoiding double slashes or missing path parameters.
Review all authorization tokens and custom headers. Ensure that the 'Content-Type' and encoding settings are configured correctly in the connector definition.
Confirm that the JSON or XML payload structure generated by Power Automate perfectly mirrors the working payload in Python or Postman without unexpected formatting or hidden characters.
Review OpenAPI Definition and Gateway Policies
Ensure the custom connector's OpenAPI schema is valid and check for any API gateway or firewall restrictions that might reject the request.
Consult the Power Automate Community
If local troubleshooting fails, seek specialized help by sharing sanitized request details with the Microsoft community.
Enhance Your Workflow Documentation with WPS Office
While troubleshooting complex API integrations and automated workflows, you often need a reliable suite for documenting processes, editing JSON logs in text files, or managing data sets. WPS Office is a lightweight, completely free alternative to Microsoft Office that meets all your daily documentation needs.
- 1. Download and Install: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Open Your Documentation: Launch WPS Office and open your existing Word or Excel documents to document your API payload structures.
- 3. Save and Export: Easily save your troubleshooting logs or export your custom connector guidelines to PDF for easy sharing with your team.
Frequently Asked Questions
Why does my API return HTTP 200 but the body says 'Request Rejected'?
This often happens when an intermediate server, such as a Web Application Firewall (WAF) or load balancer, blocks the request due to missing headers, invalid formatting, or security rules. The server is configured to return a 200 OK status to mask the exact internal routing error from potential attackers.
How can I view the raw HTTP request in Power Automate?
You can view the exact HTTP request details by going to the Flow Run History, selecting the specific failed run, and clicking 'Show raw inputs' or 'Show raw outputs' on the custom connector action step.
Why does my API work perfectly in Postman but fail in a custom connector?
Postman is designed to automatically add essential hidden headers (like Host, Accept, and User-Agent) and handle content formatting seamlessly. Power Automate custom connectors require explicit configuration for many of these properties in the OpenAPI definition.
