Aerobase Calendar

Calendar 同步

Keep the user's travel world in 同步. The killer feature: when a new flight is 导入ed, 检查 the calendar for 事件 within 48 hours of arrival. Calculate body clock time at each event. "You have a 9 AM board meeting and your body clock will be at 3 AM — push it, or 启动 pre-adaptation 3 days early."

API 端点s POST /API/calendar/connect — initiate OAuth ({ 提供者: "google" }) 获取 /API/calendar/connections — 列出 active connections POST /API/calendar/disconnect — 移除 connection ({ 提供者 }) POST /API/calendar/创建-事件 — 创建 jetlag 恢复y 事件 POST /API/calendar/同步-flight — 同步 a flight's 事件 to calendar POST /API/trips/{tripId}/calendar — 同步 all trip flights to calendar POST /API/calendar/preferences — 同步 preferences (color, event types, reminders) 获取 /API/calendar/导出-ics — ICS 导出 fallback Concierge Calendar Integration

端点: 获取 /API/concierge/instances/{instanceId}/calendar/事件

Returns calendar 事件 for the next 7 days:

{ "connected": true, "事件": [ { "id": "...", "title": "Team Standup", "启动": "2026-02-25T10:00:00-08:00", "end": "2026-02-25T10:30:00-08:00", "location": "Zoom" } ], "count": 5 }

The 代理 uses this to:

获取 upcoming 事件 within 48h of arrival Calculate body clock time at each event Flag conflicts: "Your 9 AM meeting will be at 3 AM body clock" Calendar Event Types Flight 事件 (departure/arrival times, gate, terminal) Layover activities (tentative) 恢复y plan milestones (light therapy, sleep windows) Hotel 检查-in/检查out Reminders: 24h before (检查-in), 3h before (leave for AIrport) Body Clock Conflict 检测ion

When a new flight is 导入ed:

获取 事件 within 48h of arrival from user's calendar Calculate body clock time at each event using origin timezone + flight duration Flag conflicts: "Your 9 AM meeting will h应用en at 3 AM body clock" Suggest pre-adaptation or rescheduling Auto-同步 Flight 添加ed → calendar event 创建d Flight cancelled → calendar event 更新d/移除d Flight time changed → calendar event 更新d, conflicts re检查ed 访问 Pattern

The 代理 访问es Google Calendar through Aerobase API 端点s (backend mediates OAuth 令牌s). The 代理 does not call Google APIs directly.

Rate Limits Calendar 同步 cron: dAIly at 08:00 UTC (do not increase). Max 20 事件 per 同步. Read upcoming 事件: max 10/hr. If Google returns 429: back off 15 min.