# Client error: \`POST https://www.patreon.com/api/oauth2/token\` resulted in a \`403 Forbidden\`

**URL:** <https://www.patreondevelopers.com/t/client-error-post-https-www-patreon-com-api-oauth2-token-resulted-in-a-403-forbidden/2210>\
**Category:** Friendly Help\
**Created:** [September 3, 2019, 2:12am UTC](https://www.patreondevelopers.com/t/client-error-post-https-www-patreon-com-api-oauth2-token-resulted-in-a-403-forbidden/2210 "2019-09-03T02:12:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryahn](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/ryahn/32/1035_2.png) [@Ryahn](https://www.patreondevelopers.com/u/Ryahn)\
**Post date:** [September 3, 2019, 2:12am UTC](https://www.patreondevelopers.com/t/client-error-post-https-www-patreon-com-api-oauth2-token-resulted-in-a-403-forbidden/2210/1 "2019-09-03T02:12:27Z")

</div>

I am not sure what has changed or if its something I have done. I have created new API keys but I am still getting forbidden when I try to login with the API.

I am using Laravel Socialite with Patreon provider.

When a user logins on my site. It uses this to create the authorization url to redirect back with the code.

```auto
public function redirectToProvider($provider)
        {
            return Socialite::driver($provider)
                ->redirect();
        }

```

Once it redirects back, it should work with this like it did about a month ago.

```auto
    public function handleProviderCallback($provider)
        {
            $puser = Socialite::driver($provider)->user();
            dd($puser);
        }

```

I am not sure what has changed. When I tried using guzzle to do a post to the API, I got the same results. I am starting to get at my wits end on what I could be doing wrong.

Thank you in advance.