Inbound REST API | Troubleshooting REST API | Qntrl Online Help

Troubleshooting

 1. Cannot create inbound REST module     

  • Missing required fields: Ensure Name, Base URI, and Authentication Type are provided.
  • Duplicate base URI: Use a unique base URI for each module.
  • Invalid base URI format: The base URI should begin with a / and contain no spaces or special characters.

2. API endpoint not getting triggered     

  • Incorrect endpoint path: Verify that the final URL includes the correct base URI and endpoint path.
  • Function or Circuit not linked: Ensure a valid resource is selected.
 

3. Validation error: Request not processed

  • Missing mandatory parameters: Ensure all required parameters are included in the request.
  • Incorrect parameter format: Match the data types (e.g., number, text) and allowed values.
  • Regex or length mismatch: Input may not meet defined pattern or length constraints.

 

4. Request body issues     

  • Wrong body type selected: Choose the correct body format—Raw, x-www-form-urlencoded, or None.
  • File upload not working: File uploads are only supported with Function resources, not Circuits.
  • Min/Max length not satisfied: Ensure the body content respects the length validation rules if set.
 

5. Authentication failures     

  • Invalid OAuth token: Make sure the token is valid and includes the correct scopes.
  • Incorrect API key: Check if the API key provided matches the one set in Qntrl.
  • Missing authorization header: Ensure the required authentication headers are passed correctly.
 

6. Rate limit errors     

  • Too many requests (429 Error): The request rate has exceeded the defined limit.
  • Wrong policy attached: Confirm the correct rate limit policy is selected.
  • Per-IP not working as expected: Review whether the Per-IP option is enabled as needed.
 

7. Function/Circuit error debugging  

  • Check Script Logs – Review the logs for any errors or issues in the script execution.
  • Review Circuit Execution Logs – Look into the circuit execution logs for step-by-step insights into where the error occurred.

Best practices  
  • Use Postman, CURL or Qntrl's Outbound REST Web Service to test the endpoint during development.
  • If using OAuth, ensure the correct scope is set and token is valid.
  • Always test each endpoint before publishing.

    • Related Articles

    • Bridge Troubleshooting FAQs

      1. Prerequisites & System Requirements 1.1 What are the prerequisites for installing and using Qntrl Bridge? Before installing Qntrl Bridge, ensure the following prerequisites are met: Administrative (Windows) or sudo (Linux/macOS) privileges are ...

    • Troubleshooting

      1. WSDL URL fetch failure Invalid WSDL URL: Verify the WSDL URL and ensure it is accessible. Test the URL in a browser. Authentication required: If authentication is needed, provide the correct credentials. 2. Cannot modify WSDL contract Downloaded ...

    • Troubleshooting

      1. Cannot create Inbound soap Missing required fields: Ensure Name, URI, and Authentication Type are provided. Duplicate URI: Use a unique URI for each request. 2. Cannot receive incoming SOAP requests Incorrect endpoint URL: Ensure clients are ...

    • Troubleshooting

      1. Cannot execute API Make sure all required fields are filled in correctly — this includes the URL, query parameters, headers, and request body. Missing or incorrect values can prevent the API from executing successfully. 2. Unauthorized or ...

    • Troubleshooting FAQ

      1. Why is my WebSocket not connecting? Check if the endpoint URL is correct Verify the Authentication Type(OAuth/API Key) Ensure the connection is not blocked by network/firewall 2. Why are messages not being processed? Verify the Resource Selection ...