Perplexity Support and HTTP API Request Body Update Timeline

·

When you add normal Perplexity support and proper HTTP API request body support?

Channeled
APP
·
·
We currently offer Perplexity AI integration that allows you to use their online AI to search the web or their non-online AI model. For HTTP API request body issues, could you please copy and paste the JSON you're working with so I can help troubleshoot further? Note that HTTP API features are only available with the Explorer plan or higher.
Sources: Perplexity AI x Clay integration | Clay.com Perplexity integration overview | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Vik
·
·
https://app.clay.com/workspaces/43738/workbooks/wb_0swy40yhU7dcVCCqWsF/tables/t_0sy0lt9Ygsgvw9PSc6o/views/gv_0swy41cqr3Eb2BUaXfG
Vik
·
·
Your stuff does not work

·

Failed to parse body input: Unexpected token "N" (0x4E) in JSON at position 1816 while parsing near "...ness_model_bucket ="NO INFO"E.

Vik
·
·
I can't make it work
Vik
·
·
Whatever I do I can't make it work
Bo (.
·
·
Hey, this error usually means the body of your request isn’t formatted correctly—there’s likely a misplaced token or missing quotation mark. In this case, the issue was caused by business_model_bucket = "NO INFO" not being properly formatted as valid JSON. Next time, you can paste your body into an AI or JSON validator to quickly spot formatting issues. Let me know if you want help fixing the current payload.
Vik
·
·
not yet, it worked, but I couldn't find what changed
Bo (.
·
·
Got it—glad to hear it ended up working. Appreciate you letting us know!