Skip to main content
Was this helpful?

PrimeCal Events Upcoming v2

primecal_events_upcoming_v2 is optimized for reminder, notification, and join-the-meeting workflows.

Request Parameters

FieldTypeRequiredNotes
withinMinutesnumberNoDefault 60. Maximum 10080 (7 days).
calendarIdsnumber[]NoOptional subset of accessible calendars.
userTimezonestringNoOptional 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:

  • id
  • title
  • startsAt
  • startsAtLocal — 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 is startDate at local midnight
  • minutesUntilStart
  • meetingUrl
  • calendarId
  • calendarName
  • timezone

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 meetingUrl over custom description parsing.
  • Keep withinMinutes narrow for polling-style clients.