Issue with API Templates: Double Quotes Misformatted in Octave Agent | Clay

Issue with API Templates: Double Quotes Misformatted in Octave Agent

Hello Support Team, I'm trying to use some API Templates and the double quotes have turned into single quotes making it have some errors Specifically it's the Octave: Sequence Agent Would somebody please be able to take a look into this?

15 comments

Clay
APP
·
·
This issue is likely causing a "failed to parse body" error because JSON requires double quotes for keys and string values. Single quotes aren't valid in JSON formatting. Could you please copy and paste the exact JSON from the Octave: Sequence Agent template into this chat? I'll help troubleshoot the specific formatting issues and provide a corrected version.
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?
Charles E.
·
·
{ 'agentOId': 'INSERT_AGENT_ID_HERE', 'jobTitle': ' Title ', 'companyDomain': ' Company Domain ', 'companyName': ' Company Name ', 'firstName': ' First Name ', 'linkedInProfile': ' Profile Url ', 'runtimeContext': { '1': '', '2': '', '3': '', '4': '', 'all': '' }, 'runtimeInstructions': { '1': '', '2': '', '3': '', '4': '', 'all': '' }, 'lang': 'en' }
Clay
APP
·
The JSON in the Octave: Sequence Agent template is using single quotes instead of double quotes, which causes the "failed to parse body" error. JSON requires double quotes for keys and string values. Here's the corrected version: LBKS{ "agentOId": "INSERT_AGENT_ID_HERE", "jobTitle": " Title ", "companyDomain": " Company Domain ", "companyName": " Company Name ", "firstName": " First Name ", "linkedInProfile": " Profile Url ", "runtimeContext": { "1": "", "2": "", "3": "", "4": "", "all": "" }, "runtimeInstructions": { "1": "", "2": "", "3": "", "4": "", "all": "" }, "lang": "en" }LBKSSimply replace all single quotes with double quotes to fix the error.
Sources: 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
Charles E.
·
·
The template was properly formatted when I used it a few days ago, did something happen on the Clay side that cause these changes? Thanks for all the assistance
Clay
APP
·
·
There's no record of a system-wide change that would have converted double quotes to single quotes in our API templates. JSON requires double quotes for keys and string values, and single quotes aren't valid in JSON formatting. The template may have been inadvertently modified. I've provided the corrected version with proper double quotes in our previous messages, which should resolve the "failed to parse body" error.
Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Documentation | Clay University
Charles E.
·
·
Julian T.
Clay
APP
·
·
There's no record of a system-wide change that would have converted double quotes to single quotes in our API templates. JSON requires double quotes for keys and string values, and single quotes aren't valid in JSON formatting. The template may have been inadvertently modified. I've provided the corrected version with proper double quotes in our previous messages, which should resolve the "failed to parse body" error.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Julian T.
·
·
cc Bolaji (. - any idea what might be happening? these are the templates created by Clay
Clay
APP
·
·
There's no record of a system-wide change that would have converted double quotes to single quotes in our API templates. JSON requires double quotes for keys and string values - single quotes aren't valid in JSON formatting. The "failed to parse body" error occurs when JSON isn't properly formatted, with one common issue being incorrect quote usage. I've provided the corrected version with proper double quotes in our previous messages, which should resolve the error.
Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
LuisArturo
·
·
Hey there Charles thanks for reaching out, sorry for the delay here, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Charles E.
·
·
Here's 1 example, it's the API Call column at the far right - https://app.clay.com/workspaces/301477/workbooks/wb_0sydpx7ZHEBxYjKmVVM/tables/t_0sydpyopsPkGiP5wMXs/views/gv_0sydpyoD2XVXnoafcvC
Charles E.
·
·
But it's happening to other Octave HTTP API templates as well like the sequence one, the example I shared is for prospector agent
Julian T.
·
·
cc Aaron L. who said he was looking into this
LuisArturo
·
·
Sorry for the delay here, the team is currently looking into this issue, as it is appearing for multiple templates
Julian T.
·
·
Thanks for the update - please keep us posted as you find out more and have an ETA on a fix 🙏