| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ItemId | query | string | No | |
| EwsUrl | query | string | No | |
| Token | query | string | No | |
| DocumentId | query | Guid | No | |
| pidTag | query | 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 /json/reply/UpdateDocumentWithPidTag HTTP/1.1
Host: doapigw.baasbv.nl
Accept: application/json
Content-Type: application/json
Content-Length: length
{"__type":"IDB.API.DMS.Operations.UpdateDocumentWithPidTag, IDB.API.DTO","ItemId":"String","EwsUrl":"String","Token":"String","DocumentId":"00000000-0000-0000-0000-000000000000","pidTag":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length false