Retrieve the results of a completed processing job
The Get Job Results endpoint retrieves the processed data from a completed job. This endpoint should only be called after confirming the job status is “COMPLETED” using the status endpoint.
Results are only available for completed jobs. Check job status first to ensure processing has finished.
The unique identifier of the completed job
API key for authentication (optional for some endpoints)
The response structure depends on the job type (extraction, parsing, classification, etc.).
The extracted data matching the provided JSON schema
Total processing time in seconds
Array of detected elements with bounding boxes and confidence scores
Citation information for extracted data
Paths to visualization images (if requested)
Here’s a complete example of submitting a job, monitoring its progress, and retrieving results:
Bounding boxes use the format [x1, y1, x2, y2]
where:
x1, y1
: Top-left corner coordinatesx2, y2
: Bottom-right corner coordinatesJob Still Processing (400)
The job hasn’t completed yet. Wait for the status to change to “COMPLETED” before requesting results.
Job Failed (500)
The job encountered an error during processing. Check the error message for details about what went wrong.
Results Not Found (404)
Either the job doesn’t exist, or the results have been cleaned up. Results are typically stored for 7 days.
Job Not Found (404)
The job ID is invalid or the job has been deleted. Verify you’re using the correct job ID.
Check Status First: Always verify job status is “COMPLETED” before requesting results to avoid unnecessary API calls.
Handle Errors Gracefully: Implement proper error handling for different HTTP status codes and error scenarios.
Cache Results: Store important results locally, as they may be cleaned up after 7 days.
Result Persistence: Job results are automatically cleaned up after 7 days to manage storage costs.