PUT | /POS/Manzana/Object/Update |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
EntityName | body | string | No | |
EntityId | body | Guid | No | |
ExternalId | body | string | No | |
Name | body | string | No | |
Parent | body | string | No | |
ParentId | body | Guid? | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | |
Result | form | Guid? | 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.
PUT /POS/Manzana/Object/Update HTTP/1.1
Host: apex.nikoratrade.ge
Accept: application/json
Content-Type: application/json
Content-Length: length
{"EntityName":"String","EntityId":"00000000000000000000000000000000","ExternalId":"String","Name":"String","Parent":"String","ParentId":"00000000000000000000000000000000"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"Result":"00000000000000000000000000000000"}