GET /api/v1/jobs/{jobId} endpoint lets you check the status of a job and retrieve its result once parsing completes. Because FileRouter processes documents asynchronously, you call this endpoint repeatedly until the job transitions to complete or failed. The response shape changes depending on the job’s current status.
Path Parameters
string
required
The UUID of the job to retrieve. You get this value from the
id field in the POST /api/v1/jobs response. Example: 550e8400-e29b-41d4-a716-446655440000.Required Headers
string
required
Bearer token authentication. Format:
Bearer <your-api-key>. See Authentication for details.Response Shapes by Status
The response body varies based on the job’s current status. Poll until you see"complete" or "failed".
- queued / running
- complete
- failed
Polling Example
Poll every few seconds until the job reaches a terminal status (complete or failed):
Polling loop (bash)
Error Responses
404 Not Found
404 Not Found
No job with the given
jobId exists for your account. Verify the UUID and ensure you’re using the same API key that created the job.404 error body
410 Gone — Result expired
410 Gone — Result expired
The job completed, but its result has passed the 7-day retention window and has been deleted. You can no longer retrieve the result for this job ID.
410 error body
500 Internal Server Error
500 Internal Server Error
An unexpected server-side error occurred. The response includes a
request_id — include it when contacting support.