Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Issue with Clay Stringifying JSON Payload in Customer.io Integration

·

·

Hey, I’m integrating Clay with Customer.io, but it seems like Clay is stringifying my JSON payload even when I use a raw structure for adding and updating attributes?

Issue with Clay Stringifying JSON Payload in Customer.io Integration | Clay

3 comments

· Sorted by Oldest

Channeled
APP
·
·
When sending data through our HTTP API integration, we require proper JSON formatting to ensure reliable communication with external services. This means: ** String values must be enclosed in quotes (e.g., "name": "Sam") ** Numbers and booleans should not have quotes (e.g., "age": 30) ** When using dynamic variables with /column, you still need to follow these JSON formatting rules ** Numbers with trailing zeros (like 0004) need to be in quotesThis standardized formatting helps prevent errors and ensures successful data transmission between Clay and external services. Sources: HTTP API integration overview | Clay University HTTP API with JWT authentication | Clay University
Channeled
APP
·
·
Hi Svein O.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Svein O.!