Skip to content
calternal docs

Create an Event from a Note

POST
/api/v1/calendar/events/from-note
curl --request POST \
  --url https://example.com/api/v1/calendar/events/from-note \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "calendar_id": "example", "end": "example", "note_id": "example", "start": "example", "timezone": "example" }'

Requires a signed-in User. It creates an Event with the Note title and a link to the Note. It returns 404 when the Note or Calendar is missing. Route: /api/v1/calendar/events/from-note. Inputs: . Do not automatically replay this operation after an uncertain result.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
calendar_id

Optional destination; omission uses the synced Event default (#827, DESIGN §30 C14).

string | null
end
required

RFC 3339 instant selected by the user.

string
note_id
required
string
start
required

RFC 3339 instant selected by the user.

string
timezone
required
string
Examplegenerated
{
  "calendar_id": "example",
  "end": "example",
  "note_id": "example",
  "start": "example",
  "timezone": "example"
}

Responses

Section titled “Responses”

201

Section titled “201”
Media typeapplication/json
object
event
required
object
all_day
required
boolean
calendar_id
required
string
end
string | null
etag
required
string
id
required
string
location
string | null
start
string | null
summary
required
string
tags
required
Array<string>
timezone
string | null
uid
string | null
updated_at
required
string
icalendar
required
string
Examplegenerated
{
  "event": {
    "all_day": true,
    "calendar_id": "example",
    "end": "example",
    "etag": "example",
    "id": "example",
    "location": "example",
    "start": "example",
    "summary": "example",
    "tags": [
      "example"
    ],
    "timezone": "example",
    "uid": "example",
    "updated_at": "example"
  },
  "icalendar": "example"
}

404

Section titled “404”
Media typeapplication/json

The standard API error response: { "error": { ... } }.

object
error
required

Error details.

object
code
required

Stable machine-readable code.

string
Allowed values: bad_request unauthorized forbidden not_found conflict name_conflict_case name_too_long push_endpoint_rejected too_many_requests internal service_unavailable
details
One of:

Optional field or operation details.

object
key
additional properties
string
message
required

Safe text for logs or a user-facing error message.

string
Example
{
  "error": {
    "code": "bad_request"
  }
}

429

Section titled “429”
Media typeapplication/json

The standard API error response: { "error": { ... } }.

object
error
required

Error details.

object
code
required

Stable machine-readable code.

string
Allowed values: bad_request unauthorized forbidden not_found conflict name_conflict_case name_too_long push_endpoint_rejected too_many_requests internal service_unavailable
details
One of:

Optional field or operation details.

object
key
additional properties
string
message
required

Safe text for logs or a user-facing error message.

string
Example
{
  "error": {
    "code": "bad_request"
  }
}