Skip to content

Conversation

@ZenCocoon
Copy link
Member

No description provided.

401 response. When the token is valid, but doesn't have the scopes necessary to perform requested
action, the API will return a 403 response.

## Force Which Account To Authorize
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe call it Force authorization on certain account
Or Choose which account to authorize Prepick account for authorization

@ZenCocoon ZenCocoon force-pushed the explain-bookingsync_account_id-param branch 2 times, most recently from 7b7358e to 0fea696 Compare February 16, 2016 16:56
@Fredar
Copy link
Contributor

Fredar commented Feb 16, 2016

👍

ZenCocoon added a commit that referenced this pull request Feb 16, 2016
…id-param

Explain how to force which account get authorized
@ZenCocoon ZenCocoon merged commit 20b1c56 into master Feb 16, 2016
@ZenCocoon ZenCocoon deleted the explain-bookingsync_account_id-param branch February 16, 2016 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants