---
title: "Retrieve the Status of an Offline User Upload Job"
method: GET
path: "/jobs/{job_id}"
---

# Retrieve the Status of an Offline User Upload Job

`GET /jobs/{job_id}`

Retrieve the status of a single user upload job by job ID.

## Path parameters

- `job_id` string, required

## Query parameters

- `errors` integer

## Headers

- `appid` string, required
- `authorization` string, required

## Response `200`

Success

- union
  - object
    - `status` string
    - `message` object
      - `_id` string
      - `from_api` boolean
      - `group_id` string
      - `last_modified` string
      - `received_lines` integer — The number of lines of user profiles in the uploaded file.
      - `result` 'IN PROGRESS' | 'FINISHED' | 'INVALID SCHEMA' | 'FATAL ERROR' | 'FAILED' | 'NO DATA' — The result of the upload job. One of the following values: "**IN PROGRESS**": Upload job in progress. "**FINISHED**": Upload job finished successfully. "**INVALID SCHEMA**": Invalid request file. All records fail to meet the offline user file requirements. Returned if the data file contained no valid users or if the data file isn't valid NDJSON. "**FATAL ERROR**": No users were uploaded due to a server error. "**FAILED**": Upload job failed. "**NO DATA**": Uploaded file contains no data.
      - `s3_file` string
      - `status` object
        - `created` integer — The number of unmatched offline users created in the common database.
        - `updated` integer — The number of user profiles merged.
        - `invalid` integer — The number of invalid user profiles that failed to meet the offline user file requirements, for example, due to incorrect data format or missing identifiers.
        - `error` integer — The number of user profiles that couldn't be uploaded due to server errors.
  - object
    - `status` string
    - `message` object
      - `_id` string
      - `from_api` boolean
      - `group_id` string
      - `last_modified` string
      - `received_lines` integer — The number of lines of user profiles in the uploaded file.
      - `result` 'IN PROGRESS' | 'FINISHED' | 'INVALID SCHEMA' | 'FATAL ERROR' | 'FAILED' | 'NO DATA' — The result of the upload job. One of the following values: "**IN PROGRESS**": Upload job in progress. "**FINISHED**": Upload job finished successfully. "**INVALID SCHEMA**": Invalid request file. All records fail to meet the offline user file requirements. Returned if the data file contained no valid users or if the data file isn't valid NDJSON. "**FATAL ERROR**": No users were uploaded due to a server error. "**FAILED**": Upload job failed. "**NO DATA**": Uploaded file contains no data.
      - `s3_file` string
      - `status` object
        - `created` integer — The number of unmatched offline users created in the common database.
        - `updated` integer — The number of user profiles merged.
        - `invalid` integer — The number of invalid user profiles that failed to meet the offline user file requirements, for example, due to incorrect data format or missing identifiers.
        - `error` integer — The number of user profiles that couldn't be uploaded due to server errors.
      - `invalid_users` object — The first 100 invalid format errors.
        - `filename` string — The name of the full error log. Provide this filename to [Appier Support](mailto:ess_support@appier.com) to retrieve errors beyond the first 100 included in the response.
        - `users` object[] — The invalid user records and associated error messages.
          - `user` object — The user record from the data file.
          - `error` string — The error message.
      - `error_users` object — The first 100 internal server errors.
        - `filename` string — The name of the full error log. Provide this filename to [Appier Support](mailto:ess_support@appier.com) to retrieve errors beyond the first 100 included in the response.
        - `users` object[] — The user records that failed to upload and their associated error messages.
          - `user` object — The user record from the data file.
          - `error` string — The error message.

## Other responses

- `404` — Failure

---

[API](https://skmtc.net/appier/apis/retrieve-a-user.md) · [All operations](https://skmtc.net/appier/apis/retrieve-a-user/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/appier/retrieve-a-user/revisions/2885365fa9c9/schema)