---
title: "MarketingcloudDataExtExport: Create job"
method: POST
path: "/job/marketingcloud-data-ext-export"
tags: ["Jobs"]
---

# MarketingcloudDataExtExport: Create job

`POST /job/marketingcloud-data-ext-export`

## Request

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

Create a MarketingcloudDataExtExport 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
    - `business_unit` string: Select the business unit where the data extension exists. Leave empty to export to your base Marketing Cloud account
    - `data_extension_id` string: Select the Data Extension to export to. If you would like to create a new data extension, select the "New Data Extension" option
    - `field_changes` string[]: Select up to 75 user fields to trigger user change events.
    - `folder_id` string: Select the Marketing Cloud Folder to export Lytics user data to.
    - `key_field` string: Select the Lytics field containing the subscriber key for the exported data extension. **NOTE: If you are exporting to an existing data extension, you must map your selected key field in the mapping section below**
    - `key_type` string: Select the Marketing Cloud type of the Subscriber Key
    - `mappings` object[]: Select all the fields to send to Marketing Cloud by mapping the Lytics user profile field on the left to the Marketing Cloud field on the right. **NOTE: This section is only applicable if you are exporting to an existing data extension. You must map your selected subscriber key field in this section**
    - `max_key_length v2api-default:10000` integer: Enter the maximum length for a data extension key
    - `non_scalar_fields` string[]: Choose a list of non-scalar fields to export (note: these will be created in a separate data extensions)
    - `segment_id` string: Choose the Lytics audience to export to Salesforce Marketing Cloud
    - `withbackfill` boolean: Add users who already exist in the selected Lytics audiences
  - `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`

MarketingcloudDataExtExport 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
      - `business_unit` string: Select the business unit where the data extension exists. Leave empty to export to your base Marketing Cloud account
      - `data_extension_id` string: Select the Data Extension to export to. If you would like to create a new data extension, select the "New Data Extension" option
      - `field_changes` string[]: Select up to 75 user fields to trigger user change events.
      - `folder_id` string: Select the Marketing Cloud Folder to export Lytics user data to.
      - `key_field` string: Select the Lytics field containing the subscriber key for the exported data extension. **NOTE: If you are exporting to an existing data extension, you must map your selected key field in the mapping section below**
      - `key_type` string: Select the Marketing Cloud type of the Subscriber Key
      - `mappings` object[]: Select all the fields to send to Marketing Cloud by mapping the Lytics user profile field on the left to the Marketing Cloud field on the right. **NOTE: This section is only applicable if you are exporting to an existing data extension. You must map your selected subscriber key field in this section**
      - `max_key_length v2api-default:10000` integer: Enter the maximum length for a data extension key
      - `non_scalar_fields` string[]: Choose a list of non-scalar fields to export (note: these will be created in a separate data extensions)
      - `segment_id` string: Choose the Lytics audience to export to Salesforce Marketing Cloud
      - `withbackfill` boolean: Add users who already exist 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

## Changes

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

[Operation history](https://skmtc.dev/lytics/apis/lytics-api/changes/job/marketingcloud-data-ext-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)