In the light of this discussion, and to follow up my original email, one thing 
I would want to do is associate uploaded panoramas with user IDs, for which I 
would need the OSM user details API. I would need this to only allow a given 
user to rotate or move their own panoramas, and not other users'. I presume 
this would be acceptable (if mentioned on an appropriate privacy policy)?

I tried to play around with Mapillary to see how they handle OSM authentication 
but I'm not sure whether it's working correctly- as  when I am returned to 
Mapillary after authentication with OSM, I get the error "User does not exist".

From: Colin Smale <>
Sent: 02 August 2019 10:15:45
To: <>; Tigerfell 
<>; Jóhannes Birgir Jensson <>
Cc: dev Openstreetmap <>
Subject: Re: [OSM-dev] Use of OSM API for non-editing third party applications

Now you are confusing authentication with authorisation.

On 2 August 2019 10:07:19 BST, Tigerfell <> wrote:
Not necessarily, the API calls
( and
 are used by some services to provide login and user organisation.


Aug. 2, 2019, 2:14 a.m. by
Hello Martin.

I'm afraid you are confusing two different things.

The relevant page for authentication is this one

This is a totally different thing from the editing API.


1. ágúst 2019 kl. 21:45, skrifaði "Martin Koppenhoefer" 

sent from a phone

On 1. Aug 2019, at 16:21, Jóhannes Birgir Jensson 
<<>> wrote:
I never read anything where it said that OSM-auth was only for editing. So I 
have worked on the assumption that the answer would be yes, you can piggyback.

it’s written here:

Cheers Martin

dev mailing list

Reply via email to