Validate a user-defined process (graph)
Validates a user-defined process without executing it. A user-defined process is considered valid unless the errors array in the response contains at least one error.
Checks whether the process graph is schematically correct and the processes are supported by the back-end. It MUST also check the arguments against the schema, but checking whether the arguments are adequate in the context of data is OPTIONAL. For example, a non-existing band name may get rejected only by a few back-ends. The validation MUST NOT throw an error for unresolvable process parameters.
Back-ends MUST validate the process graph. Validating the corresponding metadata is OPTIONAL.
Errors that usually occur during processing MAY NOT get reported, e.g. if a referenced file is accessible at the time of execution.
Back-ends can either report all errors at once or stop the validation once they found the first error.
Please note that a validation always returns with HTTP status code 200. Error codes in the 4xx and 5xx ranges MUST be returned only when the general validation request is invalid (e.g. server is busy or properties in the request body are missing), but never if an error was found during validation of the user-defined process (e.g. an unsupported process).
Request body
Response
Returns the validation result as a list of errors. An empty list indicates a successful validation.
Example response
{
"errors": [
{
"id": "550e8400-e29b-11d4-a716-446655440000",
"code": "SampleError",
"message": "Parameter 'sample' is missing.",
"links": [
{
"href": "https://openeo.example/docs/errors/SampleError",
"rel": "about"
}
]
}
]
}