What can I do when my API response is 200 kb?

For large API responses like your 200kb JSON file, you can use the "Define field paths to return" option in your HTTP API integration. This allows you to specify which parts of the API response you want to retrieve, filtering out unnecessary data when the response contains a lot of information but you only need specific fields. For nested parameters, use dot path notation (e.g. object1.object2.name) and separate multiple field paths with commas. Could you copy and paste your JSON into the chat so I can help troubleshoot the specific structure and suggest optimal field paths?

Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University HTTP API with JWT Authentication with Clay

You're absolutely right! For large API responses exceeding 200kb, use the "Define field paths to return" option in your HTTP API integration to filter out unnecessary data. Enter multiple field paths separated by commas, using dot notation for nested parameters (e.g. object1.object2.name). This pulls only the specific fields you need instead of storing the entire response. This approach prevents data truncation and keeps your responses within Clay's limits.

Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University HTTP API with JWT Authentication with Clay HTTP API with Clay

The "Define field paths to return" option is found in Step 7 of your HTTP API integration setup. It's an optional field that appears after you've configured your endpoint, headers, and other basic settings. In this field, enter multiple field paths separated by commas, using dot notation for nested parameters (e.g. object1.object2.name). This filters your API response to only return the specific data you need instead of the full 200kb response.

Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University HTTP API with JWT Authentication with Clay HTTP API with Clay

You can add a new column by clicking Add Column > Add Column using AI and describing what you want to extract. Alternatively, if you have existing enrichment data, click on the cell containing your JSON data to open the Cell details panel, then hover over specific endpoints and click "Add as column" to create individual child columns with only the fields you need. This approach extracts only specific data points instead of storing the full 200kb response.

Sources: Table columns | Documentation | Clay University Add Column Using AI & Add New Rows

You can extract specific fields from objects using the "Extract Values from Data" integration. To extract fields from enrichment data, click on the cell containing your object data to open the Cell details panel, then expand the object to access its fields and select "Add as column" for the specific endpoints you need. For nested objects, you can drill down into items to reference specific fields like URLs, titles, or other properties using dot notation. Could you copy and paste your JSON object into the chat so I can help troubleshoot the specific structure and suggest the best extraction approach?

Sources: Extract Values from Data with Clay Referencing dynamic data from other columns | Documentation | Clay University Referencing dynamic data from other columns | Documentation | Clay University