---
title: "GooglePubsubEgress: Update job"
method: PUT
path: "/job/google-pubsub-egress/{id}"
tags: ["Jobs"]
---

# GooglePubsubEgress: Update job

`PUT /job/google-pubsub-egress/{id}`

Update a GooglePubsubEgress job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

GooglePubsubEgress 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
      - `cloudevents` boolean — Select to send Pub/Sub messages as v1.0 JSON CloudEvents
      - `cloudevents_source` string — Enter a custom CloudEvents source. If left empty, the default source is `/work/id`
      - `cloudevents_type` string — Enter a custom CloudEvents type. If left empty, the default type is `com.lytics.audience.user.event`
      - `create_topic` boolean — If the Cloud Pub/Sub topic does not yet exist and this is selected, Lytics will create one
      - `json_template` string — Legacy inline JSON template for message transformation
      - `segment_ids` string[] — Which Lytics Audience(s) to emit events from. Each enter/exit event from the selected audiences will be sent to the Pub/Sub topic
      - `template_id` string — ID of stored template for message transformation (preferred over json_template)
      - `topic_id` string, required — The Topic ID of the Cloud Pub/Sub topic
      - `user_fields` string[] — Which user fields to export. The default is to send all fields
      - `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

---

[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)