All Verbs | /api/register |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserName | query | string | No | |
FirstName | query | string | No | |
LastName | query | string | No | |
DisplayName | query | string | No | |
query | string | No | ||
Password | query | string | No | |
ConfirmPassword | query | string | No | |
AutoLogin | query | bool? | No | |
ErrorView | query | string | No | |
Meta | query | Dictionary<string, string> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserId | form | string | No | |
SessionId | form | string | No | |
UserName | form | string | No | |
ReferrerUrl | form | string | No | |
BearerToken | form | string | No | |
RefreshToken | form | string | No | |
ResponseStatus | form | ResponseStatus | No | |
Meta | form | Dictionary<string, string> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /api/register HTTP/1.1
Host: mdn.bazefield.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userName":"String","firstName":"String","lastName":"String","displayName":"String","email":"String","password":"String","confirmPassword":"String","autoLogin":false,"errorView":"String","meta":{"String":"String"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"userId":"String","sessionId":"String","userName":"String","referrerUrl":"String","bearerToken":"String","refreshToken":"String","responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}},"meta":{"String":"String"}}