Question

Httpcaller not a valid browser with API

  • 19 December 2022
  • 2 replies
  • 2 views

Hi,

 

Using a standard browser there is no problem using Mapillary API and navigating to: https://www.mapillary.com/connect?client_id=XXX

After submitting my credentials there is a redirect that gives a code in the url: https://localhost/?code=XXX

 

Using the httpcaller I get a annoying problem that I only get a http status code 200 and a response body saying that I need to use different browser. I am using a web connection that would deal with authentication. Any ideas?

 

The documentation is here:

https://www.mapillary.com/developer/api-documentation?locale=en_US#authentication


2 replies

Badge +9

I have no experience with mapillary but looking at the documentation there is also a section about OAuth2. Clearly the API thinks you are not connecting with a valid browser which is correct, as FME is not a browser at all. Mapillary probably sees your FME as an unknown app which needs to be granted access which is done through OAuth 2.

I have no experience with mapillary but looking at the documentation there is also a section about OAuth2. Clearly the API thinks you are not connecting with a valid browser which is correct, as FME is not a browser at all. Mapillary probably sees your FME as an unknown app which needs to be granted access which is done through OAuth 2.

Hi @birgit​,

Thank you for your response. The access using OAuth 2 is done using my web connection. I have tested it against other parts of their API without problem, so the OAuth 2 authentication should not be the problem. It works against their endpoint for metadata https://graph.mapillary.com

 

My thinking is that invalid credentials/authorization should return something other than http status code 200. I don't think the authorization is the problem, but can't really pinpoint the problem.

Reply