---
title: "DotmailerMultiSegExport: Get job"
method: GET
path: "/job/dotmailer-multi-seg-export/{id}"
tags: ["Jobs"]
---

# DotmailerMultiSegExport: Get job

`GET /job/dotmailer-multi-seg-export/{id}`

Get the summary of a DotmailerMultiSegExport job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

DotmailerMultiSegExport 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
      - `backfill_only` boolean — Select this to do a one time export of the selected audiences
      - `collection_id` string — Content collection to include recommendations from - if not selected, no recommendations are sent to dotdigital
      - `email_field` string — Field that contains the contact's email
      - `email_type` string — The type of emails these contacts can receive
      - `exit_action` string — The action to take when an entity exits the audience. Note: Unsubscribing will significantly increase API usage
      - `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 dotdigital.
      - `id_field` string — Field that contains the contact's dotdigital ID. This may be a map field if importing users from multiple accounts
      - `insight_fields` string[] — Select the Lytics user fields you would like to send to the lytics_fields insight collection in dotdigital. Insight data supports complex data types like arrays and maps
      - `insight_recommendations` boolean — Select to add content recommendations for users to the lytics_recommendations insight collection in dotdigital
      - `mappings` object[] — Map all the fields from Lytics to dotdigital by selecting the Lytics field on the left, and its dotdigital destination on the right. NOTE: Complex fields such as sets and maps are not supported by dotdigital.
      - `opt_in_type` string — Opt-in type for the contacts that will be created; see [dotdigital documentation](https://support.dotdigital.com/hc/en-gb/articles/212212098-Explaining-contact-opt-in-types) for details
      - `recommender_mappings` object[] — Map all the recommender fields from Lytics to dotdigital by selecting the Lytics field on the left, and its dotdigital destination on the right. NOTE: Complex fields such as sets and maps are not supported by contact fields. This field is required if a Content Collection is set and Insight Recommendations is not set
      - `resubscribe` boolean — Contacts will be resubscribed to address books. Address-book level resubscribes are only supported for exports triggering join actions
      - `resubscribe_no_challenge` boolean — Contacts will be resubscribed to address books without triggering a confirmation email. Address-book level resubscribes are only supported for exports triggering join actions. Bulk exports will only resubscribe contacts if they have been suppressed at the account level
      - `seg_mappings` object[] — Map all Lytics Audiences to dotdigital address books by selecting the Lytics audience on the left, and its dotdigital destination on the right
      - `segment_ids` string[] — Which Lytics Audience(s) to export to dotdigital
      - `trigger_join` boolean — Contacts will trigger join actions when added to the address book. Note: Selecting this will significantly increase API usage
    - `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)