|
|
|
@ -191,7 +191,7 @@ paths:
|
|
|
|
|
first checks that the given email address is **not** already associated
|
|
|
|
|
with an account on this homeserver. This API should be used to request
|
|
|
|
|
validation tokens when adding an email address to an account. This API's
|
|
|
|
|
parameters and response is identical to that of the |/register/email/requestToken|_
|
|
|
|
|
parameters and response are identical to that of the |/register/email/requestToken|_
|
|
|
|
|
endpoint.
|
|
|
|
|
operationId: requestTokenTo3PIDEmail
|
|
|
|
|
parameters:
|
|
|
|
@ -217,9 +217,8 @@ paths:
|
|
|
|
|
$ref: "../identity/definitions/sid.yaml"
|
|
|
|
|
403:
|
|
|
|
|
description: |-
|
|
|
|
|
The homeserver does not permit the user from having the third party
|
|
|
|
|
identifier as a contact option. This does not prevent the identity
|
|
|
|
|
service from binding the third party identifier, however.
|
|
|
|
|
The homeserver does not allow the third party identifier as a
|
|
|
|
|
contact option.
|
|
|
|
|
schema:
|
|
|
|
|
$ref: "definitions/errors/error.yaml"
|
|
|
|
|
examples:
|
|
|
|
@ -229,14 +228,14 @@ paths:
|
|
|
|
|
}
|
|
|
|
|
400:
|
|
|
|
|
description: |-
|
|
|
|
|
The homeserver was unable to locate a user with the third party identifier
|
|
|
|
|
already bound, or the request was invalid.
|
|
|
|
|
The third party identifier is already in use on the homeserver, or
|
|
|
|
|
the request was invalid.
|
|
|
|
|
schema:
|
|
|
|
|
$ref: "definitions/errors/error.yaml"
|
|
|
|
|
examples:
|
|
|
|
|
application/json: {
|
|
|
|
|
"errcode": "M_THREEPID_NOT_FOUND",
|
|
|
|
|
"error": "Third party identifier not found"
|
|
|
|
|
"errcode": "M_THREEPID_IN_USE",
|
|
|
|
|
"error": "Third party identifier already in use"
|
|
|
|
|
}
|
|
|
|
|
"/account/3pid/msisdn/requestToken":
|
|
|
|
|
post:
|
|
|
|
@ -246,7 +245,7 @@ paths:
|
|
|
|
|
first checks that the given phone number is **not** already associated
|
|
|
|
|
with an account on this Home Server. This API should be used to request
|
|
|
|
|
validation tokens when adding a phone number to an account. This API's
|
|
|
|
|
parameters and response is identical to that of the |/register/msisdn/requestToken|_
|
|
|
|
|
parameters and response are identical to that of the |/register/msisdn/requestToken|_
|
|
|
|
|
endpoint.
|
|
|
|
|
operationId: requestTokenTo3PIDMSISDN
|
|
|
|
|
parameters:
|
|
|
|
@ -272,9 +271,8 @@ paths:
|
|
|
|
|
$ref: "../identity/definitions/sid.yaml"
|
|
|
|
|
403:
|
|
|
|
|
description: |-
|
|
|
|
|
The homeserver does not permit the user from having the third party
|
|
|
|
|
identifier as a contact option. This does not prevent the identity
|
|
|
|
|
service from binding the third party identifier, however.
|
|
|
|
|
The homeserver does not allow the third party identifier as a
|
|
|
|
|
contact option.
|
|
|
|
|
schema:
|
|
|
|
|
$ref: "definitions/errors/error.yaml"
|
|
|
|
|
examples:
|
|
|
|
@ -284,12 +282,12 @@ paths:
|
|
|
|
|
}
|
|
|
|
|
400:
|
|
|
|
|
description: |-
|
|
|
|
|
The homeserver was unable to location a user with the third party identifier
|
|
|
|
|
alrady bound, or the request was invalid.
|
|
|
|
|
The third party identifier is already in use on the homeserver, or
|
|
|
|
|
the request was invalid.
|
|
|
|
|
schema:
|
|
|
|
|
$ref: "definitions/errors/error.yaml"
|
|
|
|
|
examples:
|
|
|
|
|
application/json: {
|
|
|
|
|
"errcode": "M_THREEPID_NOT_FOUND",
|
|
|
|
|
"error": "Third party identifier not found"
|
|
|
|
|
"errcode": "M_THREEPID_IN_USE",
|
|
|
|
|
"error": "Third party identifier already in use"
|
|
|
|
|
}
|
|
|
|
|