Validate Prospective Inputs
I/O
Validate Prospective Inputs
Validate the inputs for a prospective job without creating a job
POST
Validate Prospective Inputs
Requires version 1.1.5 or later of the Archetype platform.
Overview
Validates a prospective job’s file inputs against the pipeline’s input-port validations, without creating a job. Used by the Developer Console to give immediate per-file feedback at job-creation time.The validation performed by this endpoint is intended primarily to provide basic guardrails
against starting a job with invalid inputs.It is not guaranteed to catch more than basic
errors in the format of the input files, and may in fact do no validation at all,
especially for files uploaded before platform version 1.1.5.
200 once the pipeline and ports are valid; each input
item is reported valid: true/false (with a message). Only file items on ports that declare a
validation are actually resolved/checked.
Checkpoints are not validated by this endpoint. They are accepted for request parameter
compatibility with Create Job. They are simply reported to be valid, as are files on
non-validated ports.
Request
This endpoint accepts the same request parameters as the Create Job endpoint. This is intentional; you can set up the parameters for Create Job, then call this endpoint first with the same parameters. If the validation succeeds, you can then immediately call Create Job with the same parameter block.Response
object
required
The per-item validation outcome, keyed by port exactly like the request
inputs. Each value
is an array of result items echoing the item’s identity plus whether it is valid and, if not,
why. Items on ports without a validation — and all checkpoint items — are always valid: true.For a file item:kind(string, required) — alwaysfilefile_id(string, required)valid(boolean, required)error(string |null)
kind(string, required) — alwayscheckpointcheckpoint_id(string, required)valid(boolean, required)error(string |null)
Validations
The validations performed depend on the job type and input formats. For example, a machine state classification job may ensure that an input CSV file actually has columns matching the names given in the job configuration, and an activity detection job may ensure that a JSON input file contains JSON objects with the fields expected by the job.The exact set of validations run by this endpoint may change over time.
Examples
200 OK
checkpoint_id instead, and is always valid:
Error responses
An invalid pipeline or port selection is rejected with400; per-file failures are reported in the 200 body instead.
400 - Invalid request (pipeline/ports)
suggestion field may be null.