---
title: "FacebookAudiencePopulate: Update job"
method: PUT
path: "/job/facebook-audience-populate/{id}"
tags: ["Jobs"]
---

# FacebookAudiencePopulate: Update job

`PUT /job/facebook-audience-populate/{id}`

Update a FacebookAudiencePopulate job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

FacebookAudiencePopulate 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
      - `ads_account_id` string — If it says "must accept Custom Audiences Terms" next to the Ads Account ID, go to https://business.facebook.com/ads/manage/customaudiences/tos/?act=YOUR_ADS_ACCOUNT_ID to accept the Facebook Ads Custom Audience terms and conditions, and then refresh this list
      - `audience_description` string — Optional description to be used for the audience in Facebook
      - `audience_name` string — Optional name to be used for the audience in Facebook
      - `audience_source` string — Select whether data was collected directly from customers, directly from partners, or from both
      - `duplicate_exports` string[] — Select additional audiences to send to Snapchat with the same configuration. Each additional audience will be sent as it's own job in Lytics
      - `hashed_email_field` string — Field that contains the SHA256 hash of user emails
      - `identifier_field` string — Field that contains the user emails
      - `mappings` object[] — Map Lytics fields on the left to their Facebook fields on the right for a greater matching resolution
      - `opt_out_link` string — Optional opt-out link to be used for the audience in Facebook
      - `segment_id` string — Choose the audience of users to export to Facebook
      - `segment_ids` string[] — Select Lytics audience(s) to send to Facebook
      - `withbackfill` boolean — Add 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)