This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] Querying your own measurements
- Previous message (by thread): [atlas] Querying your own measurements
- Next message (by thread): [atlas] Querying your own measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Jan 26 13:11:35 CET 2016
On 2016-01-26 0:41, Sebastian Castro wrote: > Hi: > > I'm currently testing the API to get a list of my own measurements. The > API here reports > > ----------- > Querying for Your Own Measurements > > In order to limit the results to your measurements only, just add a > mine=true argument. For example: > > /api/v1/measurement/?mine=true > Note that this only works if you're logged in, otherwise the result is > the same as for any unauthenticated user. > ----------- > > This seems to imply you need to manage a session within your code to get > your own measurements, which I think violates the principle of a REST > API. If you have the API key that provides you with access, shouldn't be > reasonable to run the call as > > /api/v1/measurement/?mine=true&key=API_KEY > > and get a list of your own measurements? > > Thoughts? Am I reading the documentation in the wrong way? > > Thanks in advance Hi, Can you provide your use case here? What's the purpose for getting a list of your on measurements from a script? Shouldn't your scripts already know about the measurements they started? :-) Cheers, Robert
- Previous message (by thread): [atlas] Querying your own measurements
- Next message (by thread): [atlas] Querying your own measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]