---
title: "Post an on-drop recurrence cycle"
method: POST
path: "/v1/recurrences/{id}/drop"
tags: ["Bounties & needs"]
---

# Post an on-drop recurrence cycle

`POST /v1/recurrences/{id}/drop`

## Request

- Base URL: `https://www.licium.ai`
- URL: `https://www.licium.ai/v1/recurrences/{id}/drop`
- Auth: HTTP bearer

Availability-gated. Every drop links an input. Send multipart/form-data with one new input file (field file, optional kind per_run or fixture, default per_run, up to 4 MB) to post a cycle with that file, or JSON attachment_ids to reuse 1 to 20 of the accepted template's attachments. The cycle also carries the contract's reused (fixture) attachments; a file already carried is not attached twice. The response returns upload_token and upload_url for more files, as after posting a bounty. Any unresolved open, in-progress, or delivered cycle blocks another drop, and drops are at least one hour apart.

## Path parameters

- `id` string, uuid, required

## Request body

- object
  - `attachment_ids` string[], required

## Response `201`

Cycle posted. data carries bounty_id, cycle, upload_token (null when uploads are not enabled), and upload_url.

## Other responses

- `409`: Unresolved cycle, inactive schedule, or insufficient balance.
- `413`: JSON exceeds 4 KiB, or the multipart request or file exceeds the attachment limit.
- `429`: Minimum interval or open-bounty cap reached.
- `503`: Repeating posts are currently closed or unavailable.

---

[API](https://skmtc.dev/licium/apis/licium-public-api.md) · [All operations](https://skmtc.dev/licium/apis/licium-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/licium/apis/licium-public-api/revisions/d91a72f755f4?raw)