A customer asked, “Does the AddJob action exist? How do I find a list of possible actions?”
This is a great question because understanding the correct API endpoints and available actions is essential for smooth automation.
Refer to the article Adding Jobs to Schedules via the API to see an example of a POST request to the /scheduleActions endpoint to add a job to a schedule.
List of Available Actions
Here is a list compared to the normal event syntax:
| Event Syntax | API Action |
|---|---|
| JOB:ADD | {“addjobs”} |
| JOB:BAD | {“markJobsFailed”} |
| JOB:CANCEL | {“cancelJobs”} |
| JOB:FIXED | {“markjobsfixed”} |
| JOB:FORCESTART | {“forceRestartJobs”} |
| JOB:GOOD | {“markJobsFinishedOk”} |
| JOB:HOLD | {“holdjobs”} |
| JOB:KILL | {“killJobs”} |
| JOB:RELEASE | {“releaseJobs”} |
| JOB:RESTART | {“restartJobs”} |
| JOB:RESTARTHLD | {“restartJobsOnHold”} |
| JOB:SKIP | {“skipJobs”} |
| JOB:START | {“startJobs”} |
| JOB:UNDERREVIEW | {“markjobsunderreview”} |
| SCHEDULE:CANCEL | {“close”} |
| SCHEDULE:HOLD | {“hold”} |
| SCHEDULE:RELEASE | {“release”} |
| SCHEDULE:START | {“start”} |