Retrieving inputs for a job ...

[pvretano]

Right now the only way to get the inputs for a job is to check the "request" member in the status info. The problem with that is that it is not mandatory and so if the job fails a client may or may not know which inputs were used to initiate the job. Perhaps we can consider making the request member required or adding a /job/{jobId}/inputs path.

[fmigneault]

I support the /job/{jobId}/inputs. Note that it is already defined in Part 4: https://github.com/opengeospatial/ogcapi-processes/blob/master/extensions/job_management/standard/requirements/provenance/inputs/REQ_get-op.adoc
It was added precisely because it is often needed when dealing with Provenance.

[pvretano]

@fmigneault thanks for pointing that out. I took a quick look at Part 4 but I missed that!. Is there any specific advantage of having a dedicated path for getting each input rather than making the request member mandatory? Also, how would you feel about moving this content to Part 1?

[fmigneault]

I wouldn't mind moving it to part 1.
The endpoint allows directly getting the inputs, which can be resubmitted as is to the execution endpoint.
Note that "inputs" in this case refers to https://github.com/opengeospatial/ogcapi-processes/blob/master/openapi/schemas/processes-job-management/inputs.yaml, so it is actually the contents of inputs, outputs(selection) and other optional important execution details like headers for Prefer for example.
The schema name could be changed to make this clearer.

[pvretano]

@fmigneault OK. I'll move this content to Part 1 ... I'll need you and @gfenoy to review that part when it is ready.

[pvretano]

11-MAY-2026: Changes should be ready for next SWG. @fmigneault and @gfenoy to review.