---
title: "KlaviyoExport: Update job"
method: PUT
path: "/job/klaviyo-export/{id}"
tags: ["Jobs"]
---

# KlaviyoExport: Update job

`PUT /job/klaviyo-export/{id}`

Update a KlaviyoExport job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

KlaviyoExport 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
      - `email_field` string — Select the field that contains the user emails
      - `email_marketing_consent` string — Select email marketing consent for users in the exported audience. Different consent groups should be sent through separate jobs to the same list
      - `email_marketing_consent_field` string — Select the field that has the date that the user consented to email marketing for this list
      - `force_add_to_list` boolean — Select to force add profiles to a list. This will ignore a list's opt-in settings
      - `historical_load` boolean — Select to state that this is a historical load. In order to send historical opt-in status, the consent date field must be set below and the date must be present on the user to be added
      - `list_id` string — Select an existing list to export to. If no list is selected, a new list will be created
      - `list_name` string — Enter a new list name to export to. If no list name is entered, a new list will be created with the name format "Lytics {Date}"
      - `mappings` object[] — Map all the fields from Lytics to Klaviyo by selecting the Lytics field on the left, and its Klaviyo destination on the right
      - `phone_field` string — Select the field that contains the user phone number
      - `segment_ids` string[] — Select Lytics audience(s) to send to Klaviyo
      - `sms_marketing_consent` string — Select SMS marketing consent for users in the exported audience. Different consent groups should be sent through separate jobs to the same list
      - `sms_marketing_consent_field` string — Select the field that has the date that the user consented to SMS marketing for this list
    - `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)