As far as I know, the only way to reduce the number of fields returned by Airtable in an API payload is to specify which fields to include using the Field parameter. If I want to inlude 200 fields, I have to include 200 Field parameters, which takes a long time to specify and can be problematic for the integration application; I’m using Jitterbit and I have so many fields to specify, the resulting URL is 3000 characters long, which Jitterbit is complaining about. It would be a LOT easier if, when using a View in the API, we could specify whether all fields are returned, or just those in the view.
... View more