POST | /processjobs |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
userid | body | string | No | |
processid | body | string | No | |
CreatedDate | body | DateTime | No | |
LessThan | body | bool | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | int | No | |
User_Id | form | Guid | No | |
Process_Id | form | Guid | No | |
Job_Id | form | Guid | No | |
Customer_Id | form | Guid | No | |
Precedence | form | int | No | |
Status | form | int | No | |
Name | form | string | No | |
Created_UTC | form | DateTime | No | |
Start_UTC | form | DateTime | No | |
Finish_UTC | form | DateTime | No | |
Updated_UTC | form | DateTime | No | |
JobType | form | string | No | |
JobStatus_Percentage | form | int | 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 /processjobs HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userid":"String","processid":"String","createdDate":"\/Date(-62135596800000-0000)\/","lessThan":false}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"id":0,"user_Id":"00000000000000000000000000000000","process_Id":"00000000000000000000000000000000","job_Id":"00000000000000000000000000000000","customer_Id":"00000000000000000000000000000000","precedence":0,"status":0,"name":"String","created_UTC":"\/Date(-62135596800000-0000)\/","start_UTC":"\/Date(-62135596800000-0000)\/","finish_UTC":"\/Date(-62135596800000-0000)\/","updated_UTC":"\/Date(-62135596800000-0000)\/","jobType":"String","jobStatus_Percentage":0}