The HTTP API enrichement always returns an empty cell as if no data was returned but it shows status code 200. The same request runs fine and returns data when running via python. Why is the http response not shown in clay?
This issue is likely related to how the request body is formatted in Clay. Here are a few key things to check: 1. Make sure all string values in your request body are enclosed in double quotes, including dynamic column variables. 2. Check for these common formatting issues: • Ensure all keys are properly quoted • Remove any trailing commas • Check for proper syntax and punctuation • Look for any hidden characters that might have been copied over 3. Consider using the "Remove null and undefined values" option in the enrichment settings if you have any empty fields that might be affecting the response.You can validate your JSON formatting by pasting it into a JSON validator like JSONLint to spot any formatting issues. Sources: HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT authentication | Documentation | Clay University
It's a simple GET request to an URL. No JSON is submitted.
For GET requests in Clay's HTTP API enrichment, there are a few potential reasons why you might see an empty cell despite a 200 status code: 1. Check if you've specified the correct field paths in the "Field Paths to Return" section. If this field is enabled but not properly configured, it may filter out all the response data. 2. Verify your headers are properly set up, especially if the API requires specific authentication or content-type headers.While HTTP API in Clay is designed to work with most standard APIs, it operates slightly differently from direct Python requests. It's considered a low-code feature that bridges user-friendly interfaces with more complex integrations.If you continue experiencing issues after checking these settings, you may want to explicitly request human support to help troubleshoot your specific API configuration. Sources: HTTP API integration overview | Documentation | Clay University HTTP/API [Clay 101] - Clay University
The "Field Paths to Return" is not used. No headers are needed when running the same request using python.
Since you're getting a 200 status code, the request is successfully reaching the endpoint, but there might be differences in how Clay processes the API response compared to Python. Here are a few things to consider: 1. By default, Clay expects JSON responses and processes them with Content-Type: application/json. 2. While HTTP API in Clay is designed to work with most standard APIs, it operates as a low-code feature that bridges user-friendly interfaces with more complex integrations. This means there might be some differences in how it handles responses compared to direct Python requests.To troubleshoot this: ** Verify that the API is returning data in JSON format ** Try adding the appropriate Content-Type header to your request * If possible, test the exact same endpoint with different response formats to see if that affects the resultIf these suggestions don't resolve the issue, you should request human support to help investigate your specific API configuration, as there might be nuances with how your particular API response needs to be handled in Clay. Sources: HTTP API integration overview | Documentation | Clay University HTTP/API [Clay 101] - Clay University
The endpoint is returning a html response not json.
Since Clay's HTTP API integration is designed to work with JSON responses (Content-Type: application/json), you'll need to add the appropriate Content-Type header to handle HTML responses.To resolve this: 1. In the HTTP API enrichment settings, add a header with:
• Key: Content-Type
• Value: text/htmlThis will tell Clay how to properly interpret the HTML response from your endpoint.If you continue to experience issues after setting the Content-Type header, you should request human support to help investigate your specific configuration, as there might be additional considerations needed for handling HTML responses in your use case.
Sources:
HTTP API integration overview | Documentation | Clay University
HTTP API with JWT authentication | Documentation | Clay University
cell details are still empty
Clay's HTTP API integration is specifically designed to work with JSON responses only. The Content-Type within Clay will always be application/json, and this cannot be overridden.To resolve this situation, you have two options: 1. Check if the API endpoint offers a JSON response format alternative 2. Request human support to help with your specific use case, as handling HTML responses may require special configuration or alternative approaches Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
.png){kind=logo}
