| All Verbs | /GetFilePullIntegration |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserID | query | string | No | |
| IntegrationFrameworkHeaderID | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | body | List<Dictionary> | No | |
| Integrationdata | body | List<VwIntegrationExportFields> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Uuid | body | Guid | No | |
| FieldDefinitionId | body | int | No | |
| DisplayName | body | string | No | |
| TextField | body | string | No | |
| IntegrationID | body | int | No | |
| CreatedBy | body | string | No | |
| ModifiedBy | body | string | No | |
| CreatedDate | body | DateTime? | No | |
| ModifiedDate | body | DateTime? | 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/GetFilePullIntegration HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: application/json
Content-Length: length
{"UserID":"String","IntegrationFrameworkHeaderID":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Data":[{"String":{}}],"Integrationdata":[{"FieldDefinitionId":0,"DisplayName":"String","TextField":"String","IntegrationID":0,"CreatedBy":"String","ModifiedBy":"String","CreatedDate":"\/Date(-62135596800000-0000)\/","ModifiedDate":"\/Date(-62135596800000-0000)\/"}]}