Skip to main content
PUT
/
v2.0
/
calendar
/
{calendarId}
Update Calendar Event
curl --request PUT \
  --url https://api.lofty.com/v2.0/calendar/{calendarId} \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: <content-type>' \
  --data '
{
  "content": "<string>",
  "startAt": "<string>",
  "endAt": "<string>",
  "startAtMs": 123,
  "endAtMs": 123,
  "timeZoneCode": "<string>",
  "reminderType": "<string>",
  "reminderTime": "<string>",
  "leadId": 123,
  "address": "<string>"
}
'
{
  "message": "Calendar updated successfully"
}

Documentation Index

Fetch the complete documentation index at: https://developer.lofty.com/llms.txt

Use this file to discover all available pages before exploring further.

Headers

Authorization
string
required

Bearer [access_token]

Content-Type
string
required

application/json

Path Parameters

calendarId
string
required

Composite calendar ID returned by POST /v2.0/calendar, of the form '-task' or '-appointment'.

Body

application/json

Partial update payload; only non-empty fields are applied.

content
string

Updated content/description

startAt
string

Updated start time in ISO8601 format. Preferred over startAtMs when both are provided.

endAt
string

Updated end time in ISO8601 format. Preferred over endAtMs when both are provided.

startAtMs
integer<int64>

Updated start time as Unix timestamp in milliseconds. Used when startAt is not provided.

endAtMs
integer<int64>

Updated end time as Unix timestamp in milliseconds. Used when endAt is not provided.

timeZoneCode
string

Updated timezone code

reminderType
string

Updated reminder type

reminderTime
string

Updated reminder time

leadId
integer<int64>

Updated lead ID

address
string

Updated address (for APPOINTMENT)

Response

Calendar updated. Response body is a simple message envelope.

Simple message envelope used by PUT / DELETE / finish / unfinish calendar endpoints.

message
string

Result message for the calendar operation.

Example:

"Calendar updated successfully"