Does anyone know of a way to access the browser agent that was used to initiate an API Gateway call, in the triggered lambda?

It's not in headers?

Yes it is, the previous requests I was looking at were coming from a 3rd party system rather than via a browser and they're not specified - annoying as I really could do with having the origin but that's my problem