Recent Changes to HTTP API: Missing Values Issue Explained

Hi, has there been an update with HTTP API recently that will not run rows that don't contain all values? Naturally I'd like to include all data but if some are missing then it should still send? In the past it has done that. Any essential data that it should not run without is defined in the run settings part. I'm using a webhook from make.

9 comments

Channeled
APP
·
·
The HTTP API integration includes an optional setting called "Remove null & undefined values" that you can toggle to control how empty fields are handled. When this option is enabled, it removes any fields in the request that are empty, null, or undefined to prevent sending blank values to the API. If you want to ensure all data is sent regardless of empty values, you should check if this toggle is enabled and turn it off. The only fields that should prevent the API from running are those specifically defined in your conditional run criteria, which you can set up separately in the run settings. For proper operation, make sure to: 1. Check the "Remove null & undefined values" toggle setting 2. Verify your conditional run criteria in the run settings 3. Ensure your essential data requirements are correctly defined in the conditional run formulas
Sources: HTTP API integration overview | Documentation | Clay University HTTP API with Clay HTTP API with JWT Authentication with Clay
Channeled
APP
·
·
Did that answer your question?
Patryk Ł.
·
·
Thanks, haven't noticed this option before. Although I'm still getting this error whether the option is toggled on or off.
Channeled
APP
·
·
Based on your description, you're likely encountering a "failed to parse body" error, which is related to JSON formatting rather than the null values setting. Here's how to troubleshoot this: 1. Check your JSON body formatting: • Ensure all text values are in double quotes • Make sure keys are in double quotes • Remove any trailing commas • Check for proper syntax with colons and brackets Here's an example of correct formatting: LBKS{ "name": "John", "age": 30 }LBKSIf you're using dynamic columns: ** Add quotes around dynamic column tags for string values ** If combining plain text with dynamic column tags, create a Formula column first * Be careful of extra spaces and hidden characters You can validate your JSON using a tool 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?
Channeled
APP
·
·
Did that answer your question?
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Mohammad I.
·
·
I tried with everything you said it still does not work
Channeled
APP
·
·
Looks like you're still looking for help. We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond. If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.