Try & fix RST errors
This commit is contained in:
parent
c583bf9570
commit
b71aaddad0
2 changed files with 7 additions and 3 deletions
|
@ -424,7 +424,7 @@ For the default HTTP transport, all API calls use a Content-Type of
|
|||
``application/json``. In addition, all strings MUST be encoded as UTF-8.
|
||||
|
||||
Clients are authenticated using opaque ``access_token`` strings (see
|
||||
`Registration and Login`_ for details), passed as a query string parameter on
|
||||
`Client Authentication`_ for details), passed as a query string parameter on
|
||||
all requests.
|
||||
|
||||
.. TODO
|
||||
|
|
|
@ -17,8 +17,8 @@ Version 2 is currently in development (as of Jan-March 2015) as an incremental
|
|||
but backwards-incompatible refinement of Version 1 and will be released
|
||||
shortly.
|
||||
|
||||
Authentication
|
||||
--------------
|
||||
Client Authentication
|
||||
---------------------
|
||||
Most API endpoints require the user to identify themselves by presenting
|
||||
previously obtained credentials in the form of an ``access_token`` query
|
||||
parameter.
|
||||
|
@ -1041,10 +1041,14 @@ performing User-Interactive Authentication, although they may also return
|
|||
them after authentication is completed if, for example, the requested user ID
|
||||
was registered whilst the client was performing authentication.
|
||||
|
||||
Old V1 API docs: |register|_
|
||||
|
||||
Login
|
||||
~~~~~
|
||||
This section refers to API Version 1.
|
||||
|
||||
API docs: |login|_
|
||||
|
||||
Obtaining an access token for an existing user account is done using the
|
||||
request::
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue