# Google and Facebook Client Authentication via API

**URL:** https://tech-support.simplybook.me/t/google-and-facebook-client-authentication-via-api/2304
**Category:** General
**Created:** [September 14, 2026, 7:16am UTC](https://tech-support.simplybook.me/t/google-and-facebook-client-authentication-via-api/2304 "2026-09-14T07:16:06Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Pandi](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/p/e19b73/32.png) [@Pandi](https://tech-support.simplybook.me/u/Pandi)
#### Post date: [September 14, 2026, 7:16am UTC](https://tech-support.simplybook.me/t/google-and-facebook-client-authentication-via-api/2304/1 "2026-09-14T07:16:07Z")

</div>

Hello, we are developing a fully custom booking website for IndoPsyCare using the [SimplyBook.me](http://SimplyBook.me) JSON-RPC API, without the default booking page or booking widget.

We need to implement:

1. Client sign-in with Google
2. Client sign-up with Google
3. Client sign-in with Facebook
4. Client sign-up with Facebook

We reviewed the API Explorer, API Documentation, and User API Guide but could not find methods for social client authentication.

Does the public API support exchanging a Google or Facebook OAuth token for a [SimplyBook.me](http://SimplyBook.me) client account or session?

If supported, please provide the method name, required parameters, provider values, token response, account-matching behavior, and implementation example.

If social authentication is only supported on the [SimplyBook.me](http://SimplyBook.me) booking page or widget, please confirm that it is unavailable through the public API.

---

<div class="post-metadata">

### Author: ![mib](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/m/ec9cab/32.png) [@mib](https://tech-support.simplybook.me/u/mib)
#### Post date: [September 14, 2026, 7:16am UTC](https://tech-support.simplybook.me/t/google-and-facebook-client-authentication-via-api/2304/2 "2026-09-14T07:16:36Z")

</div>



---

<div class="post-metadata">

### Author: ![vetalkor](https://tech-support.simplybook.me/user_avatar/tech-support.simplybook.me/vetalkor/32/26_2.png) [@vetalkor](https://tech-support.simplybook.me/u/vetalkor)
#### Post date: [September 18, 2026, 7:23am UTC](https://tech-support.simplybook.me/t/google-and-facebook-client-authentication-via-api/2304/3 "2026-09-18T07:23:33Z")

</div>

Hi **[Pandi](https://tech-support.simplybook.me/u/pandi)**,

The public API doesn’t support exchanging a Google or Facebook OAuth token for a [simplybook.me](http://simplybook.me) client account or session.

The only client authentication methods currently available in the public API are:

- POST /public/clients/register — creates a new client account with email, name, password (no OAuth/social provider option)
- POST /public/clients/login — authenticates with login/password
- POST /public/clients/login-by-hash — authenticates via a hash link sent by email
- POST /public/auth/token — company/widget-level auth token (not client-level)

None of these accept a provider name, an OAuth/id\_token, or an access\_token, and there’s no account-matching logic for social identities exposed via the API.

Social sign-in with Google/Facebook is currently only available on the native [simplybook.me](http://simplybook.me) booking page/widget, not through the public API. If you need this on a custom booking site, you’d have to implement the OAuth flow yourself (verify the Google/Facebook token client-side or on your backend) and then create/log in the client via the standard register/login methods using the email address returned by the provider.

Best regards,  
Vitalii
