---
title: "AttentiveExport: Create job"
method: POST
path: "/job/attentive-export"
tags: ["Jobs"]
---

# AttentiveExport: Create job

`POST /job/attentive-export`

## Request

- Base URL: `https://api.lytics.io/v2`
- URL: `https://api.lytics.io/v2/job/attentive-export`
- Auth: API key in header `Authorization`

Create a AttentiveExport job

## Query parameters

- `account_id` string

## Request body `*/*`

- object
  - `auth_ids` string[]: Authorization IDs associated with the Job
  - `config` object, required: Job configuration, unique per-workflow
    - `attribute_mappings` object[]: Optional. Map Lytics fields to Attentive's well-known typed attributes (firstName, lastName, dateOfBirth, city, etc.).
    - `custom_attributes` string[]: Optional. Select Lytics fields to send as Attentive custom attributes using the Lytics field name as the attribute name.
    - `extra_identifiers` string[]: Optional. Select Lytics fields to send as Attentive custom identifiers. The Lytics field name is used as the customIdentifier key.
    - `identifier_mappings` object[]: Map Lytics fields to Attentive's standard user identifiers (phone, email, clientUserId, shopifyId, klaviyoId). At least one identifier mapping is required.
    - `segment_ids` string[], required: Select the Lytics audience(s) to sync to Attentive. Each audience slug becomes a boolean custom attribute on the user — true on enter, false on exit.
    - `withbackfill` boolean: Send existing audience members on first run
  - `description` string: A user-defined description
  - `drop_events_during_quiet_window` boolean
  - `expires_at` string, date-time
  - `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

## Response `201`

AttentiveExport 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
      - `attribute_mappings` object[]: Optional. Map Lytics fields to Attentive's well-known typed attributes (firstName, lastName, dateOfBirth, city, etc.).
      - `custom_attributes` string[]: Optional. Select Lytics fields to send as Attentive custom attributes using the Lytics field name as the attribute name.
      - `extra_identifiers` string[]: Optional. Select Lytics fields to send as Attentive custom identifiers. The Lytics field name is used as the customIdentifier key.
      - `identifier_mappings` object[]: Map Lytics fields to Attentive's standard user identifiers (phone, email, clientUserId, shopifyId, klaviyoId). At least one identifier mapping is required.
      - `segment_ids` string[], required: Select the Lytics audience(s) to sync to Attentive. Each audience slug becomes a boolean custom attribute on the user — true on enter, false on exit.
      - `withbackfill` boolean: Send existing audience members on first run
    - `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

## Changes

- **2026-11-03** `d8e975057aec`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/lytics/apis/lytics-api/changes/job/attentive-export/post.md)

---

[API](https://skmtc.dev/lytics/apis/lytics-api.md) - [All operations](https://skmtc.dev/lytics/apis/lytics-api/llms.txt) - [OpenAPI document](https://skmtc.dev/lytics/apis/lytics-api/revisions/d8e975057aec?raw)