All Verbs | /service/DeleteScheduledJob | ||
---|---|---|---|
All Verbs | /service/DeleteScheduledJob/{Id} |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | string | No | |
JobType | form | string | No | |
JobRoute | form | string | No | |
JobDescription | form | string | No | |
Frequency | form | string | No | |
LastExecuted | form | DateTime? | No | |
Day | form | string | No | |
Hour | form | int | No | |
CronExpression | form | string | No | |
UserId | form | string | No | |
CreatedOn | form | DateTime | No | |
Meta | form | Dictionary<string, string> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | K | 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 /service/DeleteScheduledJob HTTP/1.1
Host: www.bernhardt.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":"String","jobType":"String","jobRoute":"String","jobDescription":"String","frequency":"String","lastExecuted":"0001-01-01T00:00:00.0000000Z","day":"String","hour":0,"cronExpression":"String","userId":"String","createdOn":"0001-01-01T00:00:00.0000000Z","meta":{"String":"String"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"id":"String","jobType":"String","jobRoute":"String","jobDescription":"String","frequency":"String","lastExecuted":"0001-01-01T00:00:00.0000000Z","day":"String","hour":0,"cronExpression":"String","userId":"String","createdOn":"0001-01-01T00:00:00.0000000Z","meta":{"String":"String"}}