---
title: "Function Schedules Add"
method: POST
path: "/functions/{function_id}/schedules"
tags: ["functions"]
---

# Function Schedules Add

`POST /functions/{function_id}/schedules`

## Request

- Base URL: `https://api.notte.cc` (the document declares no server; this is the origin it was published from)
- URL: `https://api.notte.cc/functions/{function_id}/schedules`
- Auth: OAuth 2
  - Password
  - Token URL: `token`

## Path parameters

- `function_id` string, required

## Headers

- `x-notte-request-origin` string, nullable
- `x-notte-sdk-version` string, nullable

## Request body

- FunctionScheduleCreateRequest
  - `cron` string, required: AWS EventBridge schedule expression. Six space-separated fields, minutes first: `minutes hours day-of-month month day-of-week year`. This is neither five-field Unix crontab nor the seconds-first six-field dialect used by Quartz and cron-parser. Exactly one of day-of-month and day-of-week must be `?`, the other must be a real value. Schedules fire in UTC. Example: `0 12 ? * * *` runs daily at noon UTC. `rate(...)` expressions such as `rate(1 hour)` are accepted too.
  - `variables` object, nullable, required: Values passed to the function on every scheduled run. Must supply every function variable that has no default, and no names the function does not declare.

## Response `200`

Successful Response

- FunctionSchedule
  - `schedule_id` string, required
  - `cron` string, required
  - `variables` object, nullable
  - `created_at` string, date-time, nullable

## Other responses

- `422`: Validation Error

## Changes

- **2026-11-04** `d56fcbf39bc9`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/notte/apis/notte-api/changes/functions/:function_id/schedules/post.md)

---

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