| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| FileID | query | Guid? | No | |
| Description | query | string | No | |
| Note | query | string | No | |
| UploadOrigin | query | string | No | |
| AssignToUserID | query | int? | No | |
| AssignToGroupID | query | int? | No | |
| DocumentInfo | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| DocumentQueuedForRegistrationID | form | int | 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/AddDocumentQueuedForRegistrationWithDocumentInfo HTTP/1.1
Host: doapigw.baasbv.nl
Accept: application/json
Content-Type: application/json
Content-Length: length
{"__type":"IDB.API.DMS.Operations.AddDocumentQueuedForRegistrationWithDocumentInfo, IDB.API","FileID":"00000000-0000-0000-0000-000000000000","Description":"String","Note":"String","UploadOrigin":"String","AssignToUserID":0,"AssignToGroupID":0,"DocumentInfo":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"__type":"IDB.API.DMS.Operations.DocumentQueuedForRegistrationResponse, IDB.API","DocumentQueuedForRegistrationID":0}