Get Subject Data Job — GET /api/v1/subject-data-jobs/{subject_job_id}
Get Subject Data Job
One export or erasure job (the cards poll it). Writes nothing.
Endpoint: GET /api/v1/subject-data-jobs/{subject_job_id}
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>. API keys are refused.
- You must have access to this personal-data job.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
subject_job_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | SubjectJobRead (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Subject rights
- Operation ID:
get_subject_data_job_api_v1_subject_data_jobs__subject_job_id__get - Source code:
backend/app/routers/subject_rights.py, line 194 - Specification: OpenAPI JSON