From 1236529e39a7e2534fdd34686a749b5a386c109b Mon Sep 17 00:00:00 2001 From: Eugen Date: Tue, 11 Apr 2017 18:03:02 +0200 Subject: Moving docs to tootsuite/documentation (#1550) --- docs/Using-the-API/OAuth-details.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) (limited to 'docs/Using-the-API/OAuth-details.md') diff --git a/docs/Using-the-API/OAuth-details.md b/docs/Using-the-API/OAuth-details.md index e88a25682..6a6926bb9 100644 --- a/docs/Using-the-API/OAuth-details.md +++ b/docs/Using-the-API/OAuth-details.md @@ -1,12 +1 @@ -OAuth details -============= - -We use the [Doorkeeper gem for OAuth](https://github.com/doorkeeper-gem/doorkeeper/wiki), so you can refer to their docs on specifics of the end-points. - -The API is divided up into access scopes: - -- `read`: Read data -- `write`: Post statuses and upload media for statuses -- `follow`: Follow, unfollow, block, unblock - -Multiple scopes can be requested during the authorization phase with the `scope` query param (space-separate the scopes). If you do not specify a `scope` in your authorization request, the resulting access token will default to `read` access. +[The documentation has moved to its own repository](https://github.com/tootsuite/documentation/blob/master/Using-the-API/OAuth-details.md) -- cgit