Troubleshooting Outbound REST API in Qntrl | Web Services Online Help | Qntrl Online Help

Troubleshooting

1. Cannot execute API     

  1. 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 forbidden error (401/403)     

  1. Missing Authorization Header: Add the required authentication in the Headers section.

3. Invalid or broken endpoint (400/404)     

  1. Incorrect API URL: Confirm the full endpoint URL is correct, including path variables.
  2. Missing Query Parameters: Ensure mandatory parameters are passed either as static values or variables.


4. REST response returns errors

  • Invalid input parameters: Ensure all required parameters (in query, header, or body) are passed and formatted correctly. Validate against the external API's specification.
  • Server errors:
    • 400 – Server unreachable: Check the endpoint URL and your network/DRE connection.
    • 404 – Not found: Verify the API URL path and that the resource exists on the external server.
    • 500 – Internal server error: Indicates an issue with the external service. Check their server logs or contact the API provider for support.

5. Variables not replaced in request     

  1. Missing Variable Inputs: When executing via script or Codex, ensure all dynamic variables (e.g., {{jobId}}) are passed as a JSON object.
  2. Incorrect Syntax: Use double curly braces ({{variableName}}) for local variables and ${configVariable} for Config Store values.

6. Request Time Out     

  1. Slow External Server: The external API might be unresponsive or slow.
  2. Low Timeout Limit: Increase the Connection Timeout value under the Settings tab as needed. 

7. SSL Certificate Verification Fails     

  1. Invalid or Self-Signed Certificate: Disable SSL Certificate Verification if testing with an untrusted or local endpoint.
  2. Mismatched Hostname: Ensure the certificate matches the host name and port in the API URL.

8.  Applied Response Not Displaying     

  1. Response Parser Not Configured: Add required fields in the Response Parser using suggested JSON paths.
  2. Postscript Modifying Output: Review the Postscript for overwrites or null assignments to expected fields.

9. Prescript/Postscript Not Executing     

  1. Script Errors: Check script syntax and log values to troubleshoot.
  2. Undefined Variables: Declare all used variables and ensure they are correctly named.

    • Related Articles

    • 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 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 ...

    • Troubleshooting FAQs

      1. What are the pre-requisite for installing and using a Bridge in Qntrl? Ensure administrative privileges for installation. Java Runtime Environment (JRE) is required. If not available, the bundled Java with Bridge Agent can be used. 2. What are the ...

    • Troubleshooting FAQs - Data Transformation States

      1. When should I use a Data Transformation state instead of a Function state? Use Data Transformation states when the required logic can be achieved using built-in capabilities such as JSONata, JSLT, or dataset operations. This helps avoid custom ...

    You are currently viewing the help articles of Qntrl 3.0. If you are still using our older version and require guidance with it, Click here.