| 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 .jsv suffix or ?format=jsv
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: text/jsv
Content-Type: text/jsv
Content-Length: length
{
workflowId: String,
sessionId: String,
datacenterLocation: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
response: {},
reponseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}