---
title: "AzuresqlImport: Get job"
method: GET
path: "/job/azuresql-import/{id}"
tags: ["Jobs"]
---

# AzuresqlImport: Get job

`GET /job/azuresql-import/{id}`

Get the summary of a AzuresqlImport job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

AzuresqlImport 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 — Select to repeatedly run this import on a schedule
      - `day_of_week` string — Day of week to run work
      - `query_timeout` integer — Enter the maximum time a query is allowed to run in minutes
      - `record_timestamp` string — Select the timestamp column to use as event timestamps, if left blank the Timestamp Column will be used
      - `row_limit` integer — Limit the number of rows to import for testing purposes
      - `run_frequency` string — Choose how often a repeated import should run
      - `since_date` string, date-time — Enter the earliest timestamp to import records from; only records with a Timestamp Column after this date will be imported. Use yyyy-mm-dd HH:MM:SS UTC format
      - `source` string — Select the table to import data from
      - `stream` string — Enter the data stream name you want to add data to. If the data stream does not exist, it will be created. if left blank the data will go to the azuresql_activity stream
      - `time_of_day` string — Time of day to start import
      - `timestamp_field` string — Select the timestamp column to order the events. This column is also used to determine updated rows when running continuously
      - `timezone` string — 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)