PUT,POST | /api/objects |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ObjectId | body | string | No | |
attributes | body | Dictionary<string, string> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
data | form | Dictionary<string, ChildObjects> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ReplyInfo | form | ReplyInfo | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
RcvTime | form | double | No | |
ReplyTime | form | double | No | |
ClientRequestHandle | form | string | No | |
Error | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
mdmobjects | form | Dictionary<int, List<DomainObject>> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Attributes | 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/objects HTTP/1.1
Host: mdn.bazefield.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"objectId":"String","attributes":{"String":"String"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"data":{"String":{"mdmobjects":{"0":[{"objectId":"String","mdmid":"String","attributes":{"String":"String"}}]},"attributes":{"String":"String"}}},"replyInfo":{"rcvTime":0,"replyTime":0,"clientRequestHandle":"String","error":"String"}}