GoHighLevel Calendars API

Update Event Notification

PUT/calendars/:calendarId/notifications/:notificationId

PUT /calendars/:calendarId/notifications/:notificationId Update Event notification by id It takes 2 path parameters and 16 body fields, requires the calendars/events.write scope and authenticates with a sub-account (location) token.

Request and authentication

Method: PUT
Full URL: https://services.leadconnectorhq.com/calendars/:calendarId/notifications/:notificationId
Scopes: calendars/events.write
Token type: Sub-account (location) token
Accepted auth: OAuth Access Token, Private Integration Token
API version header: Version: 2021-07-28
Schema verified: 22 June 2026

Path parameters

Substituted into the URL. Required by definition.

Name	Type	Description
`calendarId`required	`string`	—
`notificationId`required	`string`	—

Request body

JSON body fields. Nested objects are shown indented under their parent.

Name	Type	Description
`receiverType`	`string`	Notification recipient type One of: `contact`, `guest`, `assignedUser`, `emails`, `phoneNumbers`, `business`
`additionalEmailIds`	`array`	Additional email addresses to receive notifications. Example: `example1@email.com,example2@email.com`
`additionalPhoneNumbers`	`array`	Additional phone numbers to receive notifications. Example: `+919876744444,+919876744445`
`selectedUsers`	`array`	Selected users for in-App and business email notifications. Supports user IDs and special keyword "sub_account_admin" Example: `userId1,userId2,sub_account_admin`
`channel`	`string`	Notification channel One of: `email`, `inApp`, `sms`, `whatsapp`
`notificationType`	`string`	Notification type One of: `booked`, `confirmation`, `cancellation`, `reminder`, `followup`, `reschedule`
`isActive`	`boolean`	Is the notification active
`deleted`	`boolean`	Marks the notification as deleted (soft delete)
`templateId`	`string`	Template ID for email notification
`body`	`string`	Body for email notification. Not necessary for in-App notification
`subject`	`string`	Subject for email notification. Not necessary for in-App notification
`afterTime`	`array`	Specifies the time after which the follow-up notification should be sent. This is not required for other notification types. Example: `[object Object]`
`beforeTime`	`array`	Specifies the time before which the reminder notification should be sent. This is not required for other notification types. Example: `[object Object]`
`fromAddress`	`string`	From address for email notification
`fromNumber`	`string`	from number for sms notification
`fromName`	`string`	From name for email/sms notification

Response fields

Top-level fields returned on a successful call.

Name	Type	Description
`message`required	`string`	Result of delete/update operation

Example request

Copy-paste ready. Swap YOUR_TOKEN for your access token or Private Integration Token, and the sample IDs for your own.

curl -X PUT 'https://services.leadconnectorhq.com/calendars/YOUR_CALENDARID/notifications/YOUR_NOTIFICATIONID' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Version: 2021-07-28' \
  -H 'Content-Type: application/json' \
  -d '{
    "additionalEmailIds": [
      "example1@email.com",
      "example2@email.com"
    ],
    "additionalPhoneNumbers": [
      "+919876744444",
      "+919876744445"
    ]
  }'

Skip the schema lookup

Hylo gives your AI agent this schema — and the other 52 documented here — without you looking anything up. Ask in plain English; it picks the endpoint, fills the body, and can run the call against your own sub-account.

View pricing Read the setup guide

More calendars endpoints