OAuth Flow - Placewise API

In Public API, whenever Member is required to be authenticated, we use OAuth flow based on member access token.

In such cases, we use standard Authorization HTTP header to pass member access token like this:

Authorization: Bearer <member_access_token>

Access token may be retrieved with Create Token
endpoint by authenticating member.

It is short-lived. The endpoint also returns refresh token which lasts longer and should be stored
until access token expires.

When access token is no longer valid, server returns 460 status code with a following error:

Status code: 460

{ "error": "Member not authorized" }

When this happens, you may use Refresh token grant
using a refresh token and reload your tokens with those that are returned from it.

When refresh token happens to be no longer valid, server returns 462 status code with following error:

Status code: 462

{ "error": "Invalid refresh token" }

In such case, member must be re-authenticated again in order to generate new refresh and access tokens.