PrimeCal Events Upcoming v2
primecal_events_upcoming_v2 is optimized for reminder, notification, and join-the-meeting workflows.
Request Parameters
| Field | Type | Required | Notes |
|---|---|---|---|
withinMinutes | number | No | Default 60. Maximum 10080 (7 days). |
calendarIds | number[] | No | Optional subset of accessible calendars. |
userTimezone | string | No | Optional logical timezone override, used for timezone and startsAtLocal. Falls back to the caller's profile timezone, then UTC. Timed values still return a UTC Z timestamp in startsAt. |
Response Shape
This endpoint is intentionally compact and always returns:
idtitlestartsAtstartsAtLocal— the same instant as an ISO 8601 string with a numeric UTC offset (e.g.+02:00) in the resolved timezone; for all-day events this isstartDateat local midnightminutesUntilStartmeetingUrlcalendarIdcalendarNametimezone
Example
{
"items": [
{
"id": 203,
"title": "Upcoming MCP sync",
"startsAt": "2026-06-09T09:30:00.000Z",
"startsAtLocal": "2026-06-09T11:30:00+02:00",
"minutesUntilStart": 30,
"meetingUrl": null,
"calendarId": 14,
"calendarName": "May.B.Late Personal",
"timezone": "Europe/Budapest"
}
],
"timezone": "Europe/Budapest",
"withinMinutes": 60
}
Best Practices
- Use this endpoint for reminder cards, notification batching, and meeting-join affordances.
- Prefer
meetingUrlover custom description parsing. - Keep
withinMinutesnarrow for polling-style clients.