I’m working with Airtable and trying to fetch records from a specific view using a Java library. The connection setup looks fine and my API key works correctly. Here’s how I initialize everything:
Airtable client = new Airtable().configure(API_TOKEN);
Base database = client.base("my-database-id");
But I keep getting this error message:
Nov 12, 2020 5:53:08 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: brw=brwkel6HWNoWVEl49; path=/; expires=Fri, 12 Nov 2021 17:53:08 GMT; domain=.airtable.com; samesite=none; secure; httponly". Invalid 'expires' attribute: Fri, 12 Nov 2021 17:53:08 GMT
Exception in thread "main" com.sybit.airtable.exception.AirtableException: {"error":"NOT_FOUND"} (UNDEFINED_ERROR) [Http code 404]
at com.sybit.airtable.exception.HttpResponseExceptionHandler.onResponse(HttpResponseExceptionHandler.java:29)
at com.sybit.airtable.Table.select(Table.java:206)
The method that triggers this issue:
public void fetchTableData() throws AirtableException, HttpResponseException {
List<Vehicle> records = database.table("Vehicle").select("Routes");
}
I expected this to pull all route data from the vehicle table into my list. What could be causing this problem?
Had this exact nightmare last month. The cookie warning is just HttpClient being picky about date formats - totally harmless.
Your 404 is definitely a config issue. Here’s what others missed - check if you’re using the right environment. I’ve wasted hours debugging this only to discover I was hitting a test base while my code pointed to production IDs.
That select(“Routes”) call looks suspicious too. If “Routes” is a view name, use the view() method instead:
List<Vehicle> records = database.table("Vehicle").view("Routes").select();
If Routes is a field name you’re filtering by, your syntax is wrong anyway.
Quick debug step - log your actual base ID and table name right before the call. I bet one doesn’t match what’s in Airtable. Base IDs are case sensitive and table names need exact matches including spaces and special characters.
That cookie warning is just noise from the HTTP client - ignore it completely. The real problem is the 404 error, which screams configuration mismatch. I’ve seen this exact thing happen when the base ID gets corrupted or copied wrong. Go back to your Airtable workspace, click on your base, and check the URL. Your base ID should look like “appXYZ123456789”. Also, “Routes” in your select call is a view name, not a field. If you want specific fields, use the actual field names. Try ditching the “Routes” parameter completely and see if you can connect to the table first.
The cookie warning doesn’t matter - ignore it. Your real problem is the 404 NOT_FOUND error. This usually means your table name or view is wrong. Double-check that “Vehicle” matches exactly what you have in Airtable (capitalization matters). Also verify your base ID is correct - it should start with “app” followed by random letters and numbers (you can see this in your Airtable URL). Make sure your API key has permission to access this specific table and base. Try running a simple select() call without any view parameter first to test if your connection works.