---
title: "LocalyticsExportAudience: Get job"
method: GET
path: "/job/localytics-export-audience/{id}"
tags: ["Jobs"]
---

# LocalyticsExportAudience: Get job

`GET /job/localytics-export-audience/{id}`

Get the summary of a LocalyticsExportAudience job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

LocalyticsExportAudience 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
      - `app_id` string — Select the Localytics app to send your Lytics audiences to
      - `attributes` string[] — Select the field in the Lytics audience user that you would like to send as Localytics profile attributes
      - `audience_membership` boolean — Check to send Lytics audience membership as an attribute of Localytics profile. Checking this will create a set attribute in Localytics with name `lytics_audiences` and populate it with Lytics audience slugs that the user is part of
      - `profile_id_field` string — Select the field in the Lytics audience user that corresponds to Localytics profile ID. If a user does not exist for this ID in Localytics, then we will create the user with this ID. **Note:** Lytics users who do not have the selected ID field will be dropped
      - `segment_ids` string[] — Choose the audiences to export to Localytics app
      - `special_attributes` string[] — Select the fields in the Lytics audience user that are special profile IDs in Localytics. Please refer to the [Localytics documentation](https://docs.localytics.com/dev/profile-api.html#profile-special-ids) for more information on this
      - `withbackfill` boolean — Export users who are already in the selected Lytics audiences
    - `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)