| POST | /merge-file |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| WorkflowId | body | int | No | |
| Template | body | TemplateDefinitionDto | Yes | |
| Elements | body | Dictionary<string, ElementInputDto> | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | int | No | |
| DocumentId | form | int | No | |
| Title | form | string | Yes | |
| Description | form | string | Yes | |
| IsActive | form | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Value | form | Object | Yes | |
| DataType | form | string | Yes |
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 /merge-file HTTP/1.1
Host: etc-api.vsmlab.vn
Accept: application/json
Content-Type: application/json
Content-Length: length
{"workflowId":0,"template":{"id":0,"documentId":0,"title":"String","description":"String","isActive":false},"elements":{"String":{"value":{},"dataType":"String"}}}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{}