| POST | /api/v1/register/complete |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| RegistrationToken | body | string | Yes | |
| FirstName | body | string | Yes | |
| LastName | body | string | Yes | |
| UserType | body | string | Yes | |
| Country | body | string | Yes | |
| DeviceId | body | string | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BearerToken | form | string | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Status | form | Status | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Message | form | string | Yes | |
| StatusCode | form | int | 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/v1/register/complete HTTP/1.1
Host: pecuario-backend.develsystems.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"registrationToken":"String","firstName":"String","lastName":"String","userType":"String","country":"String","deviceId":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"bearerToken":"String"}