Correct API Endpoint for Updating a Clay Table Cell Value

I'm trying to update a cell value in a Clay table using your API but receiving a 404 error. I've tried the following endpoint formats without success:

Could you please provide the correct API endpoint and HTTP method for updating a specific cell value in a row? I'm authenticating properly with a JWT token, but it seems the endpoint URL format is incorrect

9 comments

Channeled
APP
·
·
Based on the information available, I don't have the exact API endpoint for updating a specific cell value in a Clay table. However, I can provide some general guidance on using HTTP APIs with Clay. For updating data, you typically use either the PUT or PATCH HTTP method. The endpoint structure usually follows a pattern like: LBKS[https://api.clay.com/v1/tables/{table_id}/rows/{row_id}](https://api.clay.com/v1/tables/{table_id}/rows/{row_id})LBKSTo update a specific cell, you'd include the new value in the request body as JSON. For example: LBKS{ "column_name": "new_value" }LBKSRemember to include your JWT token in the request headers for authentication. Could you please share the exact JSON body you're using in your request? This will help me troubleshoot any potential formatting issues.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Stephen S.
·
·
Thank you for your initial guidance. When I tried the suggested endpoint format https://api.clay.com/v1/tables/{table_id}/rows/{row_id} with the PUT method, I'm receiving a 404 error with the message 'deprecated API endpoint'. I'm building an integration that captures email data from Gmail and needs to store this as raw JSON in a Clay column. Our JSON payloads can be substantial (containing multiple email threads with metadata), so we're concerned about column size limits. Could you please provide:
1.
The current non-deprecated API endpoint for updating a cell value with large JSON data
2.
The exact format of the request body expected by the API
3.
A code snippet showing how to properly construct the JWT authentication token
4.
Best practices for storing large JSON data in Clay (we have the Pro Plan but want to avoid the 8kb column limit)
5.
Any alternative approaches you'd recommend for integrating external data sources that generate large JSON outputs
We want to ensure we're following Clay's recommended patterns for this type of integration. Any documentation or examples would be greatly appreciated.
Stephen S.
·
·
table url: https://app.clay.com/workspaces/25609/workbooks/wb_q2Xa78jihsgy/tables/t_g6gn2Rz9DHEH/views/gv_gVdi4zQxEcrm
Bo (.
·
·
Hey, At the moment, our API isn’t publicly supported, so unfortunately it’s not possible to update or upsert Clay tables via API for now. However, you can use Webhooks to send data into a Clay table. While it won’t let you update existing rows, it’s the recommended method for pushing in new data from external sources like Gmail. Let me know if you’d like help setting up a Webhook for this use case.
Stephen S.
·
·
Thanks, Bo (. That makes sense. Is there a way around A). Fields with 8 kb limit? B) importing a variable number of related child records within a data structure? (E.g., the number of emails that return for each email address when querying an email inbox?)
Channeled
APP
·
·
Hi Stephen, Just jumping in for Bo here. In regards to A): Clay has different size limits for cell types: basic cells allow up to 8KB, source cells up to 100KB, and action cells up to 200KB. Hitting those limits is common when dealing with large data.
These limits help keep your tables running smoothly. If you're running into issues, try splitting large data across columns, summarizing content, or passing data directly to the next step without storing it in a cell. Unfortunately there is no other workaround since we are not able to increase cell size at the moment. In regards to B) Could you share an example of what the current import looks like, along with what the ideal output would be? That’ll help me better understand the structure you're working with and see if there’s a workaround we can explore together. I look forward to your response!
Stephen S.
·
·
Thanks - I think I'm all set now with the web hook
Channeled
APP
·
·
That's great to hear! If you're all set with the other points we've covered let me know and I'll close out this ticket. If not, let us know and we'll be happy to help!
Channeled
APP
·
·