For the last couple of weeks, I’ve been getting new 404 errors on API calls that used to work perfectly every time.
The API calls run every 5 minutes or so, and 90% of the time it works great, but now 10% of the time I’m getting back an error that sa...
Update from my side on this… a Zapier engineer discovered that I was using user-agent in my webhook header and not User-Agent the capitalized version would overwrite the default User-Agent:"Zapier" whereas the lower case would be sent along with the ...
EvanHahn:
In reality, it may be a bit of both. I know Airtable has some weird Zapier-specific code, and it’s possible that Zapier stopped triggering that special behavior. So it could be everyone’s fault!
To my point with @Bill.French it isn’t...
EvanHahn:
A lot of these decisions were made before I even joined the company, so I don’t have a lot of historical context on this. If it’s important, I can try to trace down the answer, but I’m not sure we’d even be able to share that publicly ...
@EvanHahn I’m still waiting on Zapier support to respond to my latest message (from last night) but they did remind me of something I knew from testing but had no confirmation on:
If a webhook makes a request to https://api.airtable.com/v0/{appId}/...
EvanHahn:
are all of these requests using the same User-Agent header?
yes as it’s “hard coded” into my request Crud, upon further inspection it appears as the sucessful ones are using the Zapier User-Agent and the failing one had Postman as th...
