On 17/02/2016 15:54, Jasper den Hertog wrote:

Thanks.  Can this documentation update be included in:
https://atlas.ripe.net/docs/rest/
Under the last topic of "Querying for Your Own Measurements"

Thanks,
Hank

> Hi Sebastian, Hi List,
>
> I would like to inform you that we’ve created an API endpoint with a
> key= query parameter on the (stil in progress) v2 API.
>
> You can get a listing of your own measurements if you include a key -
> with sufficient permissions - that was created by you:
>
> https://atlas.ripe.net/api/v2/measurements/my/?key=<YOURKEY>
>
> The key has to to have either ‘create measurement’ or ‘download
> results of measurements’  permissions. The listing will return ALL
> measurements belonging to the user who created the given key, not only
> the measurements created with that key.
>
> The resource 
>
> https://atlas.ripe.net/api/v2/measurements/my/
>
> also gives a listing of you measurements if you’re logged in and will
> replace the ?mine=true query parameter. The query parameter will be
> deprecated in v2.
>
> greetings,
>
> Jasper
>
>> 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
>>
>

Reply via email to