.png&w=3840&q=75){kind=logo}
Help Needed: Strange Error Running HTTP API Column
Hey! I've a pretty strange error while running HTTP API column. Could you look into it, pleas?
Hey! I've a pretty strange error while running HTTP API column. Could you look into it, pleas?
The "failed to parse body" error typically occurs when there's an issue with the formatting in the Body section of your HTTP API enrichment. Here's how to fix it:1. Check your JSON formatting: • Ensure all text strings are enclosed in double quotes • Remove any extra commas at the end of lines • Make sure dynamic column values are properly quoted 2. Key troubleshooting steps: • Double-check punctuation and syntax, including spaces, colons, and brackets • Copy and paste your body content into a text editor to check for hidden characters • If using dynamic columns, ensure they're properly enclosed in quotes • Verify you're using the correct API keyFor a quick validation, you can paste your JSON into a validator like JSONLint to spot any formatting issues. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Clay University HTTP API with JWT authentication | Clay University
It's adifferent error
Clay received a 404 error from the API with Content: please unsubscribe me!A 404 error indicates that the requested resource was not found on the server. This could be happening because:1. The API endpoint URL you entered might be incorrect or no longer exists 2. The resource you're trying to access has been moved or deletedTo resolve this, please:** Double-check your API endpoint URL is correct ** Verify that the endpoint is still active and accessible * Ensure you have the proper permissions to access the resourceThe message "please unsubscribe me" appears to be a custom error message from the server, suggesting you might be trying to access an endpoint that has been deactivated or is no longer available. Source: HTTP API integration overview | Clay University
Is there any data size limits for webhook from Hubspot to Clay?
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Yes, there are two main limits for webhooks:1. Size limit: Each webhook payload must not exceed 100KB. 2. Rate limits: • Up to 10 records can be processed per second • Maximum burst capacity of 20 records per workspace • If you have multiple webhook sources active in your workspace, you may need to adjust or batch your requests to stay within these limits. Source: Import Data to Clay Using Webhooks
What should I do if I've got message: Webhook size data limit exceeded?
If you receive the "Webhook size data limit exceeded" message, this means your webhook payload is larger than the maximum allowed size of 100KB. To resolve this, you'll need to reduce the size of the data being sent in each webhook request by:1. Breaking down larger payloads into smaller chunks 2. Removing any unnecessary data fields 3. Sending only essential information in each webhook requestRemember that each webhook payload must stay under the 100KB size limit. Source: Import Data to Clay Using Webhooks