Jobs

Name: Jobs API
Brand: Jobs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey,bearer11 EndpointsREST

For Agents

Trigger Coalesce data transformation runs, list environments and nodes, and fetch run results so an agent can orchestrate Snowflake pipelines without using the Coalesce UI.

Quickstart

Get started with Jobs in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a coalesce data transformation run"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Jobs API.

Trigger a scheduled Coalesce run via the /scheduler/startRun endpoint

Cancel an in-flight run with /scheduler/cancelRun before it consumes more compute

Re-run a failed transformation through /scheduler/rerun without rebuilding the schedule

List environments and inspect nodes inside an environment for pipeline introspection

GET STARTED

Start building with Jobs API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Jobs, keeping it validated and agent-ready.

The Coalesce Jobs API lets data teams trigger, monitor, and manage data transformation runs in the Coalesce platform programmatically. Operations cover starting and cancelling scheduled runs, listing environments and nodes, and retrieving run results so transformation pipelines can be orchestrated from external schedulers or CI workflows. The API is available across Coalesce regional deployments on AWS, Azure, and GCP and authenticates with bearer tokens or an Authorization header API key.

Use Cases

Patterns agents use Jobs API for, with concrete tasks.

★ External Scheduler Integration

Orchestrate Coalesce transformation runs from Airflow, Dagster, or a custom scheduler by calling /scheduler/startRun with the target environment and job, then polling /scheduler/runStatus until the run completes. This pattern replaces relying on Coalesce's built-in scheduler when teams already have a wider data orchestration stack and want a single source of truth for DAG dependencies.

Call POST /scheduler/startRun with environmentID and jobID, then poll /scheduler/runStatus every 30 seconds until status is SUCCESS or FAILED and surface the result

Run Failure Recovery

Detect failed Coalesce runs from a monitoring layer and recover by calling /scheduler/rerun with the failed run ID. Combined with /api/v1/runs/{runID}/results this lets a recovery agent identify which nodes failed, decide whether a rerun is safe, and trigger it without human intervention for idempotent transformations.

Fetch GET /api/v1/runs/{runID}/results for the latest failed run, identify node failures, and call /scheduler/rerun if all failed nodes are marked retry-safe

Environment and Node Discovery

Build internal tooling that documents which Coalesce environments and nodes exist across regions by listing /api/v1/environments and walking nodes for each environment. This is useful for governance teams cataloguing transformation assets or building lineage graphs across multiple Coalesce deployments.

List all environments via GET /api/v1/environments, then for each environment enumerate nodes via /api/v1/environments/{environmentID}/nodes and write a flat catalog to storage

Agent-Driven Pipeline Operations

Allow an AI agent to manage Coalesce data pipelines through natural language by exposing run start, cancel, rerun, and status checks as Jentic operations. The agent looks up Coalesce by intent, loads the operation schema, and executes calls without storing the bearer token in conversation context.

Search Jentic for 'trigger a coalesce run', load the startRun schema, and execute the call with environment 'prod' and the job ID requested by the user

Key Endpoints

11 endpoints — the coalesce jobs api lets data teams trigger, monitor, and manage data transformation runs in the coalesce platform programmatically.

METHOD

PATH

DESCRIPTION

POST

/scheduler/startRun

Trigger a scheduled run

GET

/scheduler/runStatus

Check status of a run

POST

/scheduler/rerun

Re-run a failed job

POST

/scheduler/cancelRun

Cancel an in-flight run

GET

/api/v1/environments

List environments

GET

/api/v1/runs

List runs

GET

/api/v1/runs/{runID}/results

Get results for a specific run

POST

/scheduler/startRun

Trigger a scheduled run

GET

/scheduler/runStatus

Check status of a run

POST

/scheduler/rerun

Re-run a failed job

POST

/scheduler/cancelRun

Cancel an in-flight run

GET

/api/v1/environments

List environments

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Coalesce bearer tokens and Authorization API keys are stored encrypted in the Jentic vault (MAXsystem). Agents call operations through scoped tokens — raw Coalesce credentials never reach the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'trigger a coalesce run' or 'cancel a coalesce job') and Jentic returns the matching scheduler operations with their input schemas, so the agent can call the right endpoint without browsing Coalesce docs.

Time to first call

Direct Coalesce integration: 1-2 days for auth, run polling, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Snowflake API

Coalesce transformations execute against Snowflake — call Snowflake directly for query results and warehouse control

Choose Snowflake when you need raw SQL execution or warehouse scaling; use Coalesce Jobs to orchestrate the transformation graph above it

Complementary

Airbyte API

Airbyte ingests source data; Coalesce transforms it once landed in the warehouse

Use Airbyte for EL (extract/load) and Coalesce for the T (transform) step in an ELT pipeline

Alternative

GitLab API

GitLab CI/CD pipelines can be used as a generic scheduler instead of Coalesce's built-in scheduler

Pick GitLab CI when the team already runs CI there and wants a single audit trail; pick Coalesce scheduler when you want native run-status semantics

FAQs

Specific to using Jobs API through Jentic.

What authentication does the Coalesce Jobs API use?

The Coalesce Jobs API supports two schemes: HTTP bearer tokens and an apiKey passed in the Authorization header. Through Jentic the bearer token is held in the encrypted vault (MAXsystem) and never enters agent context — agents receive scoped, short-lived access only.

Can I trigger a Coalesce run programmatically with this API?

Yes. POST /scheduler/startRun starts a scheduled run for a given job and environment, and /scheduler/runStatus returns its current state. /scheduler/cancelRun and /scheduler/rerun give you control over in-flight and failed runs respectively.

What are the rate limits for the Coalesce Jobs API?

The OpenAPI spec does not publish explicit rate limits. Coalesce runs are gated by your warehouse compute and account plan rather than a per-minute API quota — check your Coalesce account dashboard for current limits before high-frequency polling.

How do I trigger a Coalesce run through Jentic?

Run pip install jentic, then search for 'trigger a coalesce run' through the Jentic SDK. Jentic returns the /scheduler/startRun operation with its input schema; load the schema, populate environmentID and jobID, and execute.

Which Coalesce regions does this API cover?

The spec lists base URLs for US, EU, Canada, and Australia across AWS, Azure, and GCP, including PrivateLink variants for AWS. Pick the server URL that matches your Coalesce deployment region — the path layout is identical across regions.

Can I get per-node results for a completed run?

Yes. GET /api/v1/runs/{runID}/results returns the per-node outcome for a specific run, which is the recommended way to drive failure-recovery logic before calling /scheduler/rerun.