API Documentation: Getting private Observation location data for own observations on localhost

[pisum]

@nimmolo

I’m using my valid iNat app_id and app_secret, and authenticating with my own username and password, to get an oAuth token.

if you plan to use the /v1 API, once you get the oauth access token, ideally you should exchange that for an API token (JWT). in some cases, the access token will still work when making requests via /v1, but you’re supposd to use the JWT.

@nimmolo

if I try the request from Ruby restclient on the command line from my localhost, the location data is omitted from the response.

without knowing exactly what your request command looks like, i can only guess that you’re making a request that passes authorization information in an improper way.

i would suggest reading https://forum.inaturalist.org/t/error-in-api-recommended-practices-jwt-instructions/20229 and referenced links, and then come back if you still have questions.

@nimmolo

It’s not documented whether the new API even returns private location data

GET /v1/observations will return private_location and private_place_guess when you make an authorized request. the field that contains the “private” version of accuracy is positional_accuracy, and that is returned regardless of whether or not you make an authorized request. (i don’t know why accuracy is handled differently.)