---
title: "IterableExport: Get job"
method: GET
path: "/job/iterable-export/{id}"
tags: ["Jobs"]
---

# IterableExport: Get job

`GET /job/iterable-export/{id}`

Get the summary of a IterableExport job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

IterableExport 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
      - `convert_maps` boolean — Convert Lytics map fields into an array of key-value objects in Iterable. This minimizes the field count in Iterable. Uncheck if you would like to send map fields to Iterable as they are in Lytics; this can lead to a high field count since each distinct key will count as a new field in Iterable
      - `email_field` string
      - `field_changes` string[] — Select up to 75 user fields to trigger user change events. For any user in the exported audience, if any of the selected field values change, then the user will be updated in Iterable.
      - `fields` string[] — Select a list of user fields to create in Iterable. In Iterable, the created field will have the name inside the ()
      - `id_field` string
      - `include_segs` boolean — Select to include the entity's audience membership as a data field called 'LyticsAudiences'
      - `list` string — Choose the list to export to, or enter a name to create a new list in Iterable
      - `mappings` object[] — Map all the fields from Lytics to Iterable by selecting the Lytics field on the left, and its Iterable destination on the right
      - `max_bytes` integer
      - `prefer_email` boolean — Select to always prefer email address over user ID. This will stop users from being created if the email address does not exist in Iterable
      - `segment_id` string — Choose the audience of users to export to Iterable
      - `segment_ids` string[] — Select the audiences of users to export to Iterable
    - `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)