| POST | /Authentication |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| body | string | No | ||
| Password | body | string | No | |
| Code | body | string | No | |
| SubscriptionObject | body | Object | No | |
| DeviceId | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| AuthToken | form | string | No | |
| Workspace | form | string | No | |
| UserId | form | string | No | |
| Teams | form | List<string> | No | |
| MobileTaskRangePast | form | int | No | |
| MobileTaskRangeFuture | form | int | No | |
| RetainCustomerDatabase | form | string | No | |
| RetainAssetDatabase | form | string | No | |
| UserType | form | 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 /Authentication HTTP/1.1
Host: dev.fieldsquared.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Email":"String","Password":"String","Code":"String","SubscriptionObject":{},"DeviceId":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"AuthToken":"String","Workspace":"String","UserId":"String","Teams":["String"],"MobileTaskRangePast":0,"MobileTaskRangeFuture":0,"RetainCustomerDatabase":"String","RetainAssetDatabase":"String","UserType":"String"}