If you still need help resolving the data size error with your API call, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
Use the Field Paths to Return option in your HTTP API integration to fetch only specific fields. [1]
Enter these field paths separated by commas:
name
tagline
product.featuredAt
Use dot notation for nested fields like featuredAt inside the product object. [2] This will filter out unnecessary data and keep you under the 200kb limit. [3]
The "Field Paths to Return" option should appear as a separate input field in your HTTP API configuration panel. It's typically located after the headers section and before the run settings. [1]
If you don't see it, scroll down in the configuration panel - it may be below the visible area in your screenshot. The field allows you to enter multiple field paths separated by commas, like: name, tagline, product.featuredAt [2]
This field is specifically designed for APIs with large responses to pull only the data you need. [3]
Yes, that's correct! You've properly configured the "Field Paths to Return" with name, tagline, product.featuredAt using comma separation and dot notation for the nested field. [1] This will filter out unnecessary data and keep you under the 200kb limit. [2]
The field paths are case-sensitive and must match the exact structure in the API response. [1] Your response shows "Product" (capital P) but you specified "product.featuredAt" (lowercase p).
Update your field paths to match the actual response structure:
name
tagline
Product.featuredAt
The field paths must use dot notation for nested parameters and match the exact casing from the API response. [2] Click into the specific cell to see more details about the response structure if needed.
