Skip to main content
POST
Create a schedule

Authorizations

Authorization
string
header
required

Send your API key in the Authorization header as Bearer API_KEY. Account API keys work in every workspace you belong to: send X-Notra-Organization-Id with the workspace id or slug to choose one. Workspace endpoints require it when you belong to more than one workspace; GET /v1/me/workspaces works without it. Organization keys only accept their own workspace there.

Body

application/json
name
string
required

Display name shown in the dashboard.

Required string length: 1 - 120
Example:

"Weekly changelog"

sourceType
enum<string>
required

Always cron for schedules.

Available options:
cron
sourceConfig
object
required
targets
object
required

Data sources each run reads from. Set at least one GitHub or Linear integration.

outputType
enum<string>
required

Type of content each run generates.

Available options:
changelog,
blog_post,
linkedin_post,
twitter_post,
image
Example:

"changelog"

enabled
boolean
required

Whether the schedule runs. Disabled schedules are stored but never fire.

Example:

true

outputConfig
object
autoPublish
boolean
default:false

Save generated changelogs and blog posts with status published instead of draft. This only marks them published in Notra; nothing is pushed to GitHub or a Notra site. Other output types always stay drafts.

Example:

false

lookbackWindow
enum<string>
default:last_7_days

How far back each run collects source activity.

Available options:
current_day,
yesterday,
last_7_days,
last_14_days,
last_30_days
Example:

"last_7_days"

Response

Schedule created successfully

schedule
object
required
organization
object
required