I’m sending https://www.patreon.com/api/oauth2/token?client_id=...
And I’m receiving:
{
"errors": [
{
"challenge_metadata": null,
"code": null,
"code_name": "InternalError",
"detail": "An unrecoverable internal server error has occurred.",
"id": "6a68c8b9-c752-5b90-99ed-66085e049d49",
"status": "500",
"title": "Internal Error."
}
]
}
EDIT:
Few hours later, still not working. My server is logging a lot of errors. This is pretty serious since almost all operations require a token which I can’t get anymore.
EDIT 2:
It works again, hurray!
Although the lack of any timely response here is troubling me. Is there a better way to report service bugs? I’ve only now realized how is my main payed service dependent on this service
.
What is the exact call that you are using?
Something like this, but I can’t post exact one due to sensitive fields:
https://www.patreon.com/api/oauth2/token?client_id=MY_ID&client_secret=MY_SECRET&grant_type=password&code=todo_use_code_here&username=MY_NAME&password=MY_PASS&scope=identity campaigns campaigns.members w:campaigns.webhook identity.memberships
If you know how to get these data without submitting my password, that would be great! 
You need to use POST method to call that endpoint and all the params need to be in the post body.
https://docs.patreon.com/#step-4-validating-receipt-of-the-oauth-token
I’m already using POST and it works now, this whole thread was about getting an error 500 response for a whole day without knowing why.
I’ve tried to update now the query by moving search params to body (as JSON), but I’m getting “unsupported_grant_type” error.
And if I send it as form-data, I’ll get 500 error:
{
"errors": [
{
"challenge_metadata": null,
"code": null,
"code_name": "InternalError",
"detail": "An unrecoverable internal server error has occurred.",
"id": "f9a504e9-9f87-5204-a1b1-87c728b491a9",
"status": "500",
"title": "Internal Error."
}
]
}
So I think I leave it as it is for now and pray it will stay working…
So after moving to post as detailed in the api doc it worked?
I haven’t change anything
, still the same POST request as written in my first/second comment. Redeploying server is not something I do often, not to mention changing API integration… that’s way too dangerous. I’ve used my Postman locally to test other type of requests as you suggested.
Anyway, the issue “resolved itself”. But I don’t suppose you can check the server logs from that time and see what went wrong.
But I don’t suppose you can check the server logs from that time and see what went wrong.
No, implementing some level of logging on your side may help troubleshoot future issues like this.