GET | /workflows | Return information about Workflows | |
---|---|---|---|
GET | /workflow | Return detailed information about workflow | |
POST | /workflow/{workflowId} | Execute workflow |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
workflowId | path | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
sessionId | form | string | No | |
datacenterLocation | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Response | form | Object | No | |
ReponseStatus | form | ResponseStatus | 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 /workflow/{workflowId} HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"workflowId":"String","sessionId":"String","datacenterLocation":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"response":{},"reponseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}