Get job result data
GET/jobs/:jobId/result/:resultId
Get result data, typically a document, of a job that has completed successfully.
Request
Path Parameters
The job ID as returned by createJob
.
The result data's ID as returned by getJobResult
.
Responses
- 200
- 404
- 409
Successful response to the getJobResultData request
- */*
- Schema
Schema
string
The job or result with the specified ID could not be found.
- application/problem+json
- application/problem+xml
- Schema
- Example (from schema)
- jobNotFoundJson
Schema
A URI reference that identifies the problem type. Note that this URI cannot be dereferenced.
A short, human-readable summary of the problem type.
The HTTP status code.
A human-readable explanation specific to this occurrence of the problem.
{
"type": "string",
"title": "string",
"status": "string",
"detail": "string"
}
{
"type": "http://www.pdf-tools.com/service/rest/errors/jobNotFound",
"title": "Job not found.",
"detail": "The job with ID 'job_XYZ' could not be found",
"status": 404
}
- Schema
- Example (from schema)
- jobNotFoundJson
Schema
A URI reference that identifies the problem type. Note that this URI cannot be dereferenced.
A short, human-readable summary of the problem type.
The HTTP status code.
A human-readable explanation specific to this occurrence of the problem.
<root>
<type>string</type>
<title>string</title>
<status>string</status>
<detail>string</detail>
</root>
<problem xmlns="urn:ietf:rfc:7807">
<type>http://www.pdf-tools.com/service/rest/errors/jobNotFound</type>
<title>Job not found.</title>
<detail>The job with ID 'job_XYZ' could not be found</detail>
<status>404</status>
</problem>
Unable to get result data, e.g. because it is not yet available. Call getJobResult
first.