Merge pull request #343 from matrix-org/dbkr/threepid_requesttoken
Spec for endpoint-specific 3pid verification token
This commit is contained in:
commit
ef4c03894d
3 changed files with 74 additions and 1 deletions
|
@ -113,6 +113,12 @@ Some requests have unique error codes:
|
|||
:``M_BAD_PAGINATION``:
|
||||
Encountered when specifying bad pagination query parameters.
|
||||
|
||||
:``M_THREEPID_IN_USE``:
|
||||
Sent when a threepid given to an API cannot be used because the same threepid is already in use.
|
||||
|
||||
:``M_SERVER_NOT_TRUSTED``:
|
||||
The client's request used a third party server, eg. ID server, that this server does not trust.
|
||||
|
||||
.. _sect:txn_ids:
|
||||
|
||||
The client-server API typically uses ``HTTP PUT`` to submit requests with a
|
||||
|
|
|
@ -124,6 +124,11 @@ This is to avoid repeatedly sending the same email in the case of request
|
|||
retries between the POSTing user and the identity service. The client should
|
||||
increment this value if they desire a new email (e.g. a reminder) to be sent.
|
||||
|
||||
Note that Home Servers offer APIs that proxy this API, adding additional
|
||||
behaviour on top, for example, ``/register/email/requestToken`` is designed
|
||||
specifically for use when registering an account and therefore will inform
|
||||
the user if the email address given is already registered on the server.
|
||||
|
||||
Validating ownership of an email
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue