POST
/signup
application/json
POST /signup HTTP/1.1Content-Type: application/jsonAuthorization: Basic VEVOQU5UX0NMSUVOVF9JRDpURU5BTlRfQ0xJRU5UX1NFQ1JFVA==Host: sample.portal.tencentciam.com{"username" : "MOCK_USERNAME","password" : "MOCK_PASSWORD"}
POST /signup HTTP/1.1Content-Type: application/jsonAuthorization: Basic VEVOQU5UX0NMSUVOVF9JRDpURU5BTlRfQ0xJRU5UX1NFQ1JFVA==Host: sample.portal.tencentciam.com{"email" : "MOCK_USERNAME@example.com","email_otp_token" : "MOCK_EMAIL_OTP_TOKEN","email_otp" : "MOCK_EMAIL_OTP","password" : "MOCK_PASSWORD","nickname" : "MOCK_NICKNAME"}
POST /signup HTTP/1.1Content-Type: application/jsonAuthorization: Basic VEVOQU5UX0NMSUVOVF9JRDpURU5BTlRfQ0xJRU5UX1NFQ1JFVA==Host: sample.portal.tencentciam.com{"phone_number" : "13612345678","phone_number_otp_token" : "MOCK_PHONE_NUMBER_OTP_TOKEN","phone_number_otp" : "MOCK_PHONE_NUMBER_OTP"}
Parameter | Description |
Authorization | HTTP Basic authentication request header. The format is Basic <credentials> , where Basic is a fixed string and <credentials> is calculated by base64(url_encode(client_id) + ":" + url_encode( client_secret)) . Basic and <credentials> are separated by a space. |
JSON Path | Data Type | Description |
username | String | Username. It can contain up to 32 characters of letters, numbers and underscores. It must start with a letter. |
password | String | User password. The password you set must comply with the policies of the account and password authentication source associated with the application. |
phone_number | String | The user's mobile number, which should be an 11-digit mobile number of the three major carriers in Chinese mainland. When this parameter is specified, both phone_number_otp_token and phone_number_otp are required. |
hone_number_otp_token | String | The otp_token returned by the server after the SMS verification code is sent. |
phone_number_otp | String | The OTP verification code received by the user's mobile phone. |
email | String | The user's email address. When this parameter is specified, both email_otp_token and email_otp are required. |
email_otp_token | String | The otp_token returned by the server after the email verification code is sent. |
email_otp | String | The OTP verification code received by the user's email. |
Name | String | Username |
nickname | String | The user's alias. |
zoneinfo | String | The user’s time zone, such as Asia/Shanghai or Europe/Paris . |
locale | String | The user locale information, such as zh-CN or en-US . |
HTTP/1.1 200 OKContent-Type: application/json{"sub" : "MOCK_USER_ID"}
Parameter | Data Type | Description |
sub | String | Unique identifier of the user. |
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "misconfigured","error_description" : "Sign up flow of the application is not enabled."}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "invalid_request","error_description" : "Missing required sign-up attribute(s)."}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "invalid_request","error_description" : "Unconfigured sign-up attribute(s) found."}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "invalid_request","error_description" : "Unknown attribute(s) found."}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "invalid_username"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "duplicate_username"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "malformed_phone_number"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "duplicate_phone_number"}
phone_number_otp_token
parameter is incorrect or has expired, or the parameter used for sign-up is not the same as the one for sending the verification code. For example, the mobile numbers are different.HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "bad_phone_number_otp_token"}
phone_number_otp
parameter is incorrect or has expired.HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "bad_phone_number_otp"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "malformed_email"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "duplicate_email"}
email_otp_token
parameter is incorrect or has expired, or the parameter value used for sign-up is not the same as the one used for sending the verification code. For example, the email addresses are different.HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "bad_email_otp_token"}
email_otp
parameter is incorrect or has expired.HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "bad_email_otp"}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "misconfigured","error_description" : "No password auth source is associated with the application."}
HTTP/1.1 400 Bad RequestContent-Type: application/json;charset=UTF-8{"error" : "invalid_password"}
Was this page helpful?