eQuipAPI

GetMobile_Workflow_Transaction_Sync_Data

The following routes are available for this service:
All Verbs	/GetMobile_Workflow_Transaction_Sync_Data/{UserID}/{WorkflowID}

**GetMobile_Workflow_Transaction_Sync_Data** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	path	string	No
WorkflowID	path	string	No

**Mobile_Workflow_Transaction_Sync_Data_Result** Parameters:
Name	Parameter	Data Type	Required	Description
Mobile_Workflow_Transaction_Sync_Data	body	List<Mobile_Workflow_Transaction_Sync_Data>	No

**Mobile_Workflow_Transaction_Sync_Data** Parameters:
Name	Parameter	Data Type	Required
Mobile_Workflow_Transaction_Sync_ID	body	string	No
WorkflowID	body	string	No
Transaction_JSON	body	string	No
Sync_Request_Recieved	body	string	No
Sync_Request_Processed	body	string	No
Sync_Request_Result	body	string	No
Is_Sync_Request_Processed	body	bool	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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/GetMobile_Workflow_Transaction_Sync_Data HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/json
Content-Length: length

{"UserID":"String","WorkflowID":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Mobile_Workflow_Transaction_Sync_Data":[{"Mobile_Workflow_Transaction_Sync_ID":"String","WorkflowID":"String","Transaction_JSON":"String","Sync_Request_Recieved":"String","Sync_Request_Processed":"String","Sync_Request_Result":"String","Is_Sync_Request_Processed":false}]}