---
title: "CampaignmonitorActivate: Get job"
method: GET
path: "/job/campaignmonitor-activate/{id}"
tags: ["Jobs"]
---

# CampaignmonitorActivate: Get job

`GET /job/campaignmonitor-activate/{id}`

Get the summary of a CampaignmonitorActivate job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

CampaignmonitorActivate 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
      - `client_id` string — Choose the Campaign Monitor account you would like to export to
      - `email_field` string — The field name that contains the user's email
      - `list_id` string — Select the list where you'd like Lytics to send audience members. Note: duplicate users across lists in Campaign Monitor results in a bill per user per list.
      - `mappings` object[] — Map Lytics user fields to Campaign Monitor custom fields for the selected list
      - `name_field` string — The field name that contains the user's full name
      - `queue_subscription` boolean — Check this box to automate workflow emails that are based on the subscription date. On Campaign Monitor, emails are not sent by default when subscribers are imported into an email campaign based on the subscription date
      - `resubscribe` boolean — Add users who have previously been deleted or unsubscribed from the Campaign Monitor list
      - `segment_ids` string[] — The name of the Lytics audiences that contains the users you want to sync to Campaign Monitor. Lytics will create segments within the Campaign Monitor list for each selected audience.
      - `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)