Issues with HTTP APIs Related to Column Value Insertion

Hey Clay S. - did anything change with HTTP APIs and inserting values from columns? Having multiple customers report issues where they are doing something like: "linkedInProfile": "/COLUMN_NAME" and the value is no longer being passed through? I'm guessing it has something to do with the Clay.formatForJSON changes from a few weeks back? but the weird thing is that these were tables that were working fine as of yesterday

5 comments

Julian T.
·
·
https://app.clay.com/workspaces/301477/tables/t_WaHyWnJhpc3m/views/gv_AmGmTRAhvJBv ~ table
Bo (.
·
·
Hi! Thanks for reporting this. The HTTP API column behavior shouldn't have changed - inserting values using "/COLUMN_NAME" should still work normally. The only recent change was adding quotation marks around string values while keeping numbers unquoted, as shown here: https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440?sid=679ea0ce-5151-4193-adbd-7790995dd8cb Since you mentioned these tables were working yesterday, could you share a specific example of what's not working now? I'd love to help investigate this!
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.
Mr D.
·
·
Having the same issue.
Julian T.
·
·
Hi team - any updates on this one? Bo (.