We had a similar issue on 28th Feb -- though I think our error was that there were no grants on the key (it had been working for months, showed fine on the UI). I just made a new key and had no issue after.

-m

On Thu, Mar 8, 2018 at 9:30 AM, Ponikierski, Grzegorz <gponikie@akamai.com> wrote:

Hi!

 

I had the same issue 28th Feb. I had to add 'probes - Get non-public measurement results' to my API key to fix it.

 

Regards,

Grzegorz

 

From: Daniel Ankers <md1clv@md1clv.com>
Date: Thursday 2018-03-08 at 18:27
To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net>
Subject: [atlas] API Keys problem?

 

Hi,

Has there been a change in the way that API keys work for the measurement results API?

 

I've got an API key which is granted permission to get results from a non-public measurement.  When I do:

 

curl -H "Authorization: Key $KEY" "https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=1520510400"

 

(Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get:

 

{"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}}

 

 

This was previously working, but I'm not sure exactly when it stopped.  I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned.



Regards,

Dan




--
Marcel Flores, PhD | Research Scientist
VerizonDigitalMedia.com | AS15133
p: +1 310.593.6880 e: marcel.flores@verizondigitalmedia.com  
13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094