Assigned
Status Update
No update yet.
Comments
ra...@google.com
Thanks for your suggestion!
We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.
we...@gmail.com Restricted
Restricted
pa...@gmail.com
"the API works just fine in a browser using fetch() if you set the right headers"
What are the right headers for Routes API to work in Browser?
What are the right headers for Routes API to work in Browser?
Description
Feature Request
What would you like to see us add to this API?
I would like the Routes API to continue working in Web Browsers. While the documentation currently describes how the Routes API can be used server-side via CURL and other tools, the API works just fine in a browser using
fetch()if you set the right headers.After chatting with "miguev@" in Discord, they mentioned this was not a supported use case and I should file a Feature Request.
I have several projects that use the JavaScript Distance Matrix API and want to migrate them to the new Routes API to achieve better performance and reduce the amount of JS code they depend on. I saw this new API supports GCP OAuth-style authentication so I was able to easily generate some short-lived JWTs to authenticate and improve the security of my application too.