---
title: "Create import schedule"
method: POST
path: "/importsource/{importSourceId}/importschedule"
---

# Create import schedule

`POST /importsource/{importSourceId}/importschedule`

Creates a new scheduled import configuration for the specified import source. Scheduled imports allow you to automate data imports on a recurring basis (daily, weekly, monthly) or run them once at a specific time.

## Path parameters

- `importSourceId` string, required

## Request body

- ImportScheduleRequest
  - `startTime` string, date-time, required — The date and time when the first import should execute, in ISO 8601 format (e.g., '2024-01-15T02:00:00Z'). Must be in the future.
  - `runInterval` 'ONCE' | 'DAILY' | 'WEEKLY' | 'MONTHLY', required — The frequency of the scheduled import. ONCE: runs only at startTime. DAILY: runs every day at the specified time. WEEKLY: runs every 7 days. MONTHLY: runs on the same day of each month.
  - `callbackUrl` string, uri, nullable — Optional webhook URL to call after each scheduled import execution. The URL will receive a POST request with execution status.

## Response `200`

Import schedule created successfully

- ImportScheduleResponse
  - `id` string — The unique identifier of the import schedule
  - `importSourceId` string — The ID of the associated import source
  - `startTime` string, date-time — The start time of the schedule in ISO 8601 format
  - `runInterval` 'ONCE' | 'DAILY' | 'WEEKLY' | 'MONTHLY' — The frequency of the scheduled import
  - `created` string, date-time — Timestamp when the schedule was created
  - `updated` string, date-time — Timestamp when the schedule was last updated
  - `collectionId` string — The collection (object schema) ID associated with this import

## Other responses

- `400` — Invalid schedule configuration (e.g., schedule already exists, invalid date format, unsupported import source type)
- `401` — Client must be authenticated to access this resource.
- `403` — Forbidden - Insufficient permissions to create schedule
- `404` — Import source not found
- `500` — Something went wrong. Please try again later. If the error persists, contact our support team.

---

[API](https://skmtc.net/atlassian/apis/rest.md) · [All operations](https://skmtc.net/atlassian/apis/rest/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/rest/versions/07137e668210/schema)