---
title: "BqSystemEventExport: Get job"
method: GET
path: "/job/bq-system-event-export/{id}"
tags: ["Jobs"]
---

# BqSystemEventExport: Get job

`GET /job/bq-system-event-export/{id}`

Get the summary of a BqSystemEventExport job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

BqSystemEventExport Job

- object
  - `_meta` object — Response Metadata
  - `data` object — Response Payload
    - `account_id` string — Lytics Account ID
    - `anomaly_rule` ModelsAnomalyRuleResp
      - `aid` integer
      - `checks` ModelsRuleCheckConfigReq[]
        - `allowable_violations` integer
        - `interval` string
        - `lookback_count` integer
        - `max_threshold` integer
        - `metric_type` string
        - `min_threshold` integer
        - `type` string
        - `variance_pct` number
      - `created` string
      - `id` string
      - `subject_id` string
      - `subject_type` string
      - `updated` string
    - `api_token_auth_id` string — this is set when work is create using access token
    - `auth_ids` string[] — Authorization IDs associated with the Job
    - `config` object, required — Job configuration, unique per-workflow
      - `continuous_update` boolean — (Optional) Continuously run this export
      - `dataset` string — Select the Google BigQuery Dataset you want to export system events to
      - `end_date` string — (Optional) Export system events upto this date (ex: 2020-01-01). If no end date is given then system events up to the current date will be exported.
      - `project` string — Select the Google BigQuery Project you want to export system events to
      - `start_date` string — (Optional) Export system events after this date (ex: 2020-01-01). If no start date is given then system events for last 30 days will be exported.
      - `subject_id` string — (Optional) Provide the Subject ID for above system event subject type you would like to export (work_id, segment_id, account_id). Only events specific to this Subject ID will be exported.
      - `subject_type` string — (Optional) Provide the Subject Type of system events you would like to export (work, segment, account). Only events specific to this Subject Type will be exported.
      - `table_name` string — (Optional) Select the Google BigQuery table you want to export system events to. If an existing table is not selected then one will be created. If no table name is entered lytics\\_{system_event}\\_export\\_{AID} will be used
      - `time_of_day` string — (Optional) Time of day to start export each day
      - `timezone` string — (Optional) Timezone for time of day
    - `created` string
    - `deleted` boolean — The Job has been deleted
    - `description` string — A user-defined description
    - `drop_events_during_quiet_window` boolean
    - `expires_at` string, date-time
    - `id` string — A Lytics-assigned, immutable unique ID for the Job
    - `meta` object — Extra meta data about the job
    - `monitoring` object — Inline monitoring config. On write: omit to keep, null to clear, or a config to set.
    - `name` string, required — A user-defined name
    - `quiet_period` integer
    - `quiet_time_of_day` string
    - `quiet_timezone` string
    - `sleep_until` string
    - `status` 'runnable' | 'sleeping' | 'paused' | 'completed' | 'fault' | 'failed' | 'killed' | 'deleted' | 'unknown' — The status of the job
    - `updated` string
    - `user_id` string — The user ID that created or updated the job
    - `workflow` string — The workflow slug
    - `workflow_id` string — The workflow ID
  - `request_id` string
  - `status` integer — HTTP Status Code

## Other responses

- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/lytics/apis/lytics-api.md) · [All operations](https://skmtc.net/lytics/apis/lytics-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lytics/lytics-api/versions/366eeabcb6de/schema)