POST | /newgeometry |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CompanyId | body | int | No | |
Geometry | body | Geometry | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ApiKey | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Name | form | string | No | |
CompanyId | form | int | No | |
Wkt | form | string | No | |
Color | form | string | No | |
Type | form | GeometryType | No | |
Zoom | form | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | int | No | |
Modified | form | DateTime | No | |
Created | form | DateTime | No | |
ModifiedBy | form | int | No | |
CreatedBy | form | int | No | |
Deleted | form | bool | 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 /newgeometry HTTP/1.1
Host: api.v3.monitorsystem.ru
Accept: application/json
Content-Type: application/json
Content-Length: length
{"CompanyId":0,"Geometry":{"Name":"String","CompanyId":0,"Wkt":"String","Color":"String","Type":"Noone","Zoom":0,"Id":0,"Modified":"\/Date(-62135596800000-0000)\/","Created":"\/Date(-62135596800000-0000)\/","ModifiedBy":0,"CreatedBy":0,"Deleted":false},"ApiKey":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length 0