---
title: "BluekaiSftpExport: Create job"
method: POST
path: "/job/bluekai-sftp-export"
tags: ["Jobs"]
---

# BluekaiSftpExport: Create job

`POST /job/bluekai-sftp-export`

Create a BluekaiSftpExport job

## Query parameters

- `account_id` string

## Response `201`

BluekaiSftpExport 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
      - `append_segment_name` boolean — Select to add a column with the name of the exported Lytics audience
      - `continuous_update` boolean — Select to run this export continuously
      - `day_of_week` string — Day of week to run work
      - `delimiter` string
      - `export_segments` boolean — Select to add a column containing all the audiences a user is a member of
      - `fields` string[] — Select user fields to export. If none are selected all user fields will be included
      - `identifier_field` string — This field will be placed in the first column of the file and should be a unique identifier, this field should also be mapped
      - `join` string — Designate a custom join character for fields that have multiple values. Default is to join multi-value fields with &, e.g., emails=test@gmail.com&test2@gmail.com
      - `run_frequency` string — Choose how often a continuous export should create a new file
      - `segment_ids` string[] — Select the audience(s) that contains the users to export
      - `segments` string[] — Add columns for each of the selected Lytics audiences a user is a member of
      - `skip_user_fields` boolean — To send all user fields, leave this unselected and leave the Fields to Export selection empty, then all fields will be included in the export
      - `time_of_day` string — Time of day to start export each day. Applies to Daily, weekly, and Monthly frequencies only
      - `timezone` string — Timezone for time of day
    - `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)