Troubleshooting Deepseek API JSON Error in Clay Integration

Kaushik K. · 2025-01-26 11:27:30.969208+00

I’m unable to use deepseek api in clay with http api, i’m constantly getting the error “Expected ‘,’ or ‘}’ after property value in JSON at position 387 (line 6 column 312)” and i’m not sure how to fix it

Troubleshooting Deepseek API JSON Error in Clay Integration | Clay

15 comments

· Sorted by Oldest

Channeled
APP
·
·
This error indicates there's a JSON formatting issue in your HTTP API request body. Here's how to fix it: 1. Check for these common JSON formatting issues: • Ensure all text strings are enclosed in double quotes • Remove any extra commas at the end of properties • Verify proper syntax for special characters 2. For dynamic variables using /column: • Enclose string values in quotes • Leave numbers without quotes (except for numbers with trailing zeros like "0004") • If combining plain text with dynamic column tags, create a Formula column firstFor a quick fix, try pasting your JSON into a validator like JSONLint to identify and fix formatting errors. 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 HTTP API integration overview | Documentation | Clay University
Kaushik K.
·
·
this is constantly giving me the error
Loading attachments
Kaushik K.
·
·
talk to a human
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Kaushik K.
·
·
any update here?
Nicholas J.
·
·
hey did u figure out how to run deepseek. im trying to learn too
Kaushik K.
·
·
hello?
Mark L.
·
·
Kaushik, what table are you working in? Happy to have a look with you. Based on your screenshot, looks like an error with the JSON you're providing. (You might also consider working with a JSON validator you can find on the web to inspect format.)
LDB
·
·
So is it possible to use a DeepSeek Api key inside Clay?
Daniel K.
·
·
Hey! Thanks for getting in touch! 😊 Just wanted to let you know that we're currently in the process of implementing that feature. Stay tuned for updates! We don't have a specific timeframe yet, but we're on it!
Channeled
APP
·
·
Hi Kaushik K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Artur G.
·
·
Excited to see DeepSeek in Claygent specifically
Owen C.
·
·
Absolutely! So are we! Stay tuned. :)
Charlie S.
·
·
Is the API implemented yet? Whats the timeline?
Bo (.
·
·
Hi Kaushik! We don't have a specific timeline for API implementation yet. While our team is reviewing this feature request, I can't guarantee when it might be added. Let me know if you'd like to explore other ways to accomplish what you're trying to do, if so just let me know ! :)

Channeled
APP
·
·
This error indicates there's a JSON formatting issue in your HTTP API request body. Here's how to fix it: 1. Check for these common JSON formatting issues: • Ensure all text strings are enclosed in double quotes • Remove any extra commas at the end of properties • Verify proper syntax for special characters 2. For dynamic variables using /column: • Enclose string values in quotes • Leave numbers without quotes (except for numbers with trailing zeros like "0004") • If combining plain text with dynamic column tags, create a Formula column firstFor a quick fix, try pasting your JSON into a validator like JSONLint to identify and fix formatting errors. 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 HTTP API integration overview | Documentation | Clay University
Kaushik K.
·
·
this is constantly giving me the error
Loading attachments
Kaushik K.
·
·
talk to a human
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Kaushik K.
·
·
any update here?
Nicholas J.
·
·
hey did u figure out how to run deepseek. im trying to learn too
Kaushik K.
·
·
hello?
Mark L.
·
·
Kaushik, what table are you working in? Happy to have a look with you. Based on your screenshot, looks like an error with the JSON you're providing. (You might also consider working with a JSON validator you can find on the web to inspect format.)
LDB
·
·
So is it possible to use a DeepSeek Api key inside Clay?
Daniel K.
·
·
Hey! Thanks for getting in touch! 😊 Just wanted to let you know that we're currently in the process of implementing that feature. Stay tuned for updates! We don't have a specific timeframe yet, but we're on it!
Channeled
APP
·
·
Hi Kaushik K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Artur G.
·
·
Excited to see DeepSeek in Claygent specifically
Owen C.
·
·
Absolutely! So are we! Stay tuned. :)
Charlie S.
·
·
Is the API implemented yet? Whats the timeline?
Bo (.
·
·
Hi Kaushik! We don't have a specific timeline for API implementation yet. While our team is reviewing this feature request, I can't guarantee when it might be added. Let me know if you'd like to explore other ways to accomplish what you're trying to do, if so just let me know ! :)