can't get JSON file with server versions due to cloudflare captcha

[frozn]

Hello,

to get the actual server versions I want to use the following JSON file:

https://teamspeak.com/versions/server.json

In my browser everything's fine, but unfortunately if I grab it with PHP, cloudflare decline the access and ask to resolve a captcha:

file_get_contents('https://teamspeak.com/versions/server.json');

result (HTML file, no JSON file as expected):

Please enable cookies.
One more step
Please complete the security check to access teamspeak.com


Why do I have to complete a CAPTCHA?
Completing the CAPTCHA proves you are a human and gives you temporary access to the web property.
What can I do to prevent this in the future?
If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.
If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices.
Cloudflare Ray ID: xxxxxxxxxxxxxxxx • Your IP: xxx.xxx.xxx.xxx • Performance & security by Cloudflare •

I think it's something to configure on the site of teamspeak.com, or am I missing something?


Thanks and greetings,

frozn

[samurai-virgin]

Provide User Agent in request

[ScP]

Thank you for letting us know. I'll forward the info to our IT department.

[frozn]

any update on this?

tested it again, but cloudflare decline the access furthermore.

[iPistachi]

If it's in PHP, try curl

<?php
$url="https://teamspeak.com/versions/server.json";
$agent= 'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)';
$ch = curl_init();
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_VERBOSE, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_USERAGENT, $agent);
curl_setopt($ch, CURLOPT_URL,$url);
$resultado=curl_exec($ch);
$json = json_decode($resultado,true);
print_r($json);
?>

The return is in json.
I tested and it worked

[RandomHost]

Having an "API" endpoint that is restricted to humans is kinda pointless.

I'd say what TeamSpeak needs is a new sub-domain like "api.teamspeak.com" or similar and a proper API implementation with rate limits, realtime data and a suitable DDoS mitigation that does not block automated access.

This JSON file that appears to get updated by hand some time after a new release was published is kinda awkward.

[frozn]

thanks for your example. @iPistachi

setting a user-agent in my request to simulate a "real user using its browser" works, but I think it's like RandomHost already mentioned:

this file should generally be accessible by automated access.