---
title: "Create a release trigger"
method: POST
path: "/accounts/{account_id}/distributions/{distribution_id}/release_triggers"
tags: ["Release Triggers"]
---

# Create a release trigger

`POST /accounts/{account_id}/distributions/{distribution_id}/release_triggers`

Create a new recurring release. New releases will be published automatically, based on the cron schedule provided. Currently, only one release trigger can exist per distribution.

## Path parameters

- `account_id` string, required
- `distribution_id` string, required

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `cron_schedule` string — Cron schedule for the scheduler. Read more about the format of this field at https://en.wikipedia.org/wiki/Cron
  - `time_zone` string — Time zone for the scheduler
  - `locale_ids` string[] — List of locale ids that will be included in the release.
  - `tags` string[] — Only include tagged keys in the release. For a key to be included it must be tagged with all tags provided
  - `branch` string — Branch used for release
  - `app_min_version` string — The created releases will be available only for apps with version greater or equal to this value
  - `app_max_version` string — The created releases will be available only for apps with version less or equal to this value

## Response `201`

Created

- ReleaseTrigger
  - `id` string
  - `branch` string
  - `cron_schedule` string — Cron schedule for the scheduler. Read more about the format of this field at https://en.wikipedia.org/wiki/Cron
  - `time_zone` string — Time zone for the scheduler
  - `next_run_at` string, date-time — The next time a release will be created for this trigger
  - `app_min_version` string
  - `app_max_version` string
  - `locales` LocalePreview[]
    - `id` string
    - `name` string
    - `code` string
  - `tags` string[]
  - `created_at` string, date-time
  - `updated_at` string, date-time

## Other responses

- `400` — Bad request. The request could not be parsed or a parameter failed validation. Verify the request body, the content type, and the parameter types, then retry.
- `404` — Not found. The requested resource does not exist or is not visible to the authenticated user. Verify the identifiers in the request path and that the token has access to them, then retry.
- `429` — Too many requests. The rate limit has been exceeded. Wait until the time indicated by the `X-Rate-Limit-Reset` response header before retrying.

---

[API](https://skmtc.net/phrase/apis/control-hub-service.md) · [All operations](https://skmtc.net/phrase/apis/control-hub-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/phrase/control-hub-service/versions/98ecac7ba2bf/schema)