---
title: "BigcommerceExportAudience: Create job"
method: POST
path: "/job/bigcommerce-export-audience"
tags: ["Jobs"]
---

# BigcommerceExportAudience: Create job

`POST /job/bigcommerce-export-audience`

Create a BigcommerceExportAudience job

## Query parameters

- `account_id` string

## Response `201`

BigcommerceExportAudience 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
      - `audience_attribute` integer — Select the attribute field that should contain the Lytics audience name. If none is selected, one with the name 'LyticsAudience_{JobID}' will be created for your account
      - `custom_attributes` object[] — Map custom attributes from Lytics to BigCommerce by selecting the Lytics field on the left, and its BigCommerce destination on the right
      - `id_field` string, required — Select the field that contains the user's BigCommerce ID field
      - `segment_id` string, required — Select the Lytics audience to send to BigCommerce
      - `standard_fields` object[] — Map standard fields from Lytics to BigCommerce by selecting the Lytics field on the left, and its BigCommerce destination on the right
      - `withbackfill` boolean — Select to send users who already exist in the selected Lytics audience
    - `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)