Skip to main content
The Jobs API allows you to define schedules for objects that perform work. You can schedule datasources, tasks, and Spark jobs. This topic explains how to format requests to the Jobs API. To learn how to work with jobs and schedules in the Fusion UI, see Jobs and Schedules.

Job runtime configuration

In order to see this object within the Fusion UI, it must be associated with an app. To do this, create the object using the /apps endpoint.
Job configuration requests have these parameters:
  • <type>:<id> path parameter (required)
    The resource identifier takes the form <type>:<id>, such as datasource:movie-db, spark:dailyMetricsRollup-counters, or task:delete-old-system-logs.
    See Job types below.
  • enabled body parameter
    ”True” or “false” to enable or disable the job.
  • triggers body parameter
    This parameter defines one or more conditions that trigger the job. See Job triggers below.
Below is an example request that configures a job:

Job types

The job type must be specified as part of the resource identifier in PUT, POST, and DELETE calls. These are the possible job types:

Job triggers

Each job can have multiple triggers, and each trigger configuration requires enabled and type parameters. Additional parameters are required by each trigger type, described below:

Examples

Get all datasource jobs

Input
Output

Start a datasource job now

Input
Output

Get the job history for a datasource

Input
Output

Define a trigger for a datasource job

Input
Output