--- title: "ResponsysExport: Create job" method: POST path: "/job/responsys-export" tags: ["Jobs"] --- # ResponsysExport: Create job `POST /job/responsys-export` ## Request - Base URL: `https://api.lytics.io/v2` - URL: `https://api.lytics.io/v2/job/responsys-export` - Auth: API key in header `Authorization` Create a ResponsysExport 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 - `additional_fields` object[]: Select up to 29 user fields to export to Lytics_User_Fields extension table - `additional_membership_segment_ids` string[]: AdditionalMembershipSegmentIDs are evaluated per exported profile purely so the enrichment template can see membership in them. Unlike SegmentIDs they are not part of the export scope: they add no trigger and export no additional profiles. - `continuous_update` boolean - `enrichment_template_id` string: EnrichmentTemplateID, if set, renders the referenced template per user and merges its output fields onto the user before export, so they can be mapped like native fields. - `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 Responsys. - `fields_table` string: Optionally select a fields extension table to write to. If none is selected, a new extension table Lytics_User_Fields_{Job ID} will be created. Note the field names must match the Lytics field names - `id_mappings` object[]: Map all the fields from Lytics to Responsys by selecting the Lytics field on the left and the Responsys destination on the right - `list` string: The list in Responsys that you'd like to export data to - `match_column_1` string: Select the ID to use as the main identifier for matching - `match_column_2` string: Select the ID to use as the secondary identifier for matching - `segment_ids` string[], required: Select the Lytics audiences you'd like to export to Responsys. - `segment_membership_as` 'entity' | 'env': SegmentMembershipAs controls how segment membership reaches the enrichment template: "entity" (default) merges scoped _segments slugs into the data; "env" passes the ly_segment_association env var (names + slugs). - `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` ResponsysExport 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 - `additional_fields` object[]: Select up to 29 user fields to export to Lytics_User_Fields extension table - `additional_membership_segment_ids` string[]: AdditionalMembershipSegmentIDs are evaluated per exported profile purely so the enrichment template can see membership in them. Unlike SegmentIDs they are not part of the export scope: they add no trigger and export no additional profiles. - `continuous_update` boolean - `enrichment_template_id` string: EnrichmentTemplateID, if set, renders the referenced template per user and merges its output fields onto the user before export, so they can be mapped like native fields. - `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 Responsys. - `fields_table` string: Optionally select a fields extension table to write to. If none is selected, a new extension table Lytics_User_Fields_{Job ID} will be created. Note the field names must match the Lytics field names - `id_mappings` object[]: Map all the fields from Lytics to Responsys by selecting the Lytics field on the left and the Responsys destination on the right - `list` string: The list in Responsys that you'd like to export data to - `match_column_1` string: Select the ID to use as the main identifier for matching - `match_column_2` string: Select the ID to use as the secondary identifier for matching - `segment_ids` string[], required: Select the Lytics audiences you'd like to export to Responsys. - `segment_membership_as` 'entity' | 'env': SegmentMembershipAs controls how segment membership reaches the enrichment template: "entity" (default) merges scoped _segments slugs into the data; "env" passes the ly_segment_association env var (names + slugs). - `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/responsys-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)