400 Bad Request on client_credentials request, but only in production!

BarryCarlyon · June 9, 2021, 10:25am

First off you probably want to do something more like

BarryCarlyon/twitch_misc/blob/main/authentication/app_access_tokens/php/generate_token_as_qs.php

<?php

include(__DIR__ . '/config.php');

$ch = curl_init('https://id.twitch.tv/oauth2/token?client_id=' . CLIENT_ID . '&client_secret=' . CLIENT_SECRET . '&grant_type=client_credentials');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_POST, true);

$r = curl_exec($ch);
$i = curl_getinfo($ch);
curl_close($ch);

if ($i['http_code'] == 200) {
    $data = json_decode($r);
    if (json_last_error() == JSON_ERROR_NONE) {
        echo 'Got token';
        print_r($data);
    } else {
        echo 'Failed to parse JSON';
    }

This file has been truncated. show original

Which will handle things and test responses more gracefully.

As the the 400, not sure whats going on here. as this endpoint should always return JSON.
I don’t see anything wrong with your code.

This could suggests there is a problem between you and Twitch on production.
Either a firewall or other system.
Or you have having a residual issue from yesterdsays fastly outage. Since fastly will sit in from of the API.
And/or your production provided is having a bad day with routing.