Skip to main content
Direct Job creation is best for one-off workloads or quick experiments. For workloads you plan to run repeatedly, consider creating a Job Recipe instead — recipes save your configuration and make re-launching easier.

Create Job Request

Endpoint

Request Body

Hardware Requirements

Container Parameters


Example: Create a BATCH Job

All API requests require HMAC signature authentication. See Authenticate Requests for the generateAuthHeaders helper function used below.

Example: Create a PERSISTENT Job with SSH



Stop a Job

To stop a RUNNING job (or cancel a PENDING job):

Best Practices

  1. Use Job Recipes for repeated workloads — If you’ll run this configuration again, create a recipe instead of submitting the full payload each time
  2. Use BATCH for finite tasks — Set realistic timeouts to prevent runaway costs
  3. Use PERSISTENT for interactive work — SSH access, development, debugging
  4. Stop PERSISTENT jobs promptly — Set calendar reminders if needed

API Reference

For complete API documentation including all fields and response schemas, see the API Reference.