Calendar

The Calendar API returns one person's calendar (their tasks and events, the viewings and open houses they host or attend, their deals' expected closes and their own Google or Outlook appointments) and creates and changes Fondaro events.

These endpoints take a signed-in member's session token (Authorization: Bearer <session-token>); API keys do not open them. See Authentication.

Reading is open to every member. Writes need an active plan (403 SUBSCRIPTION_REQUIRED otherwise), and only the owner of an event can change it. Fondaro never sends invitations itself: an event with invited people is written to the owner's own Google or Outlook calendar, and that provider invites them from the owner's address.

Tasks and events

Every Fondaro entry is an event. A task is an event with a lead and nobody invited from outside the team: it is owed until it is ticked done, and overdue once its time has passed. Anything else (a meeting with invited people, a viewing, an event with no lead) is never owed.

Create and edit requests may send kind:

The event reports which it is in taskLike (see Read one event).

Read a window

GET /calendar

Everything on the caller's calendar between two local dates, as one flat list.

curl "https://api.fondaro.com/calendar?from=2026-10-05&to=2026-10-12&tz=Europe/Madrid" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "window": { "from": "2026-10-05", "to": "2026-10-12", "tz": "Europe/Madrid" },  "items": [    {      "key": "meeting:6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b",      "kind": "meeting",      "startsAt": "2026-10-07T09:00:00.000Z",      "endsAt": "2026-10-07T09:30:00.000Z",      "allDay": false,      "date": null,      "title": "Meeting with a buyer",      "eventId": "6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b",      "leadId": 4182,      "leadName": "A. Buyer",      "sync": "synced",      "ownerUserId": "user_2a",      "readOnly": false,      "status": "confirmed",      "attendeeCount": 1,      "leadResponse": "accepted",      "done": false,      "owed": false,      "overdue": false    }  ],  "truncated": false}

Timed items are placed by their instant in tz; an all-day item has allDay: true and a date that never shifts with the zone. An overdue task stays on its own day. truncated is true only when a source hit its safety bound.

Item fields

Per kind: a meeting adds status, location, attendeeCount, invitedCount, leadResponse (accepted, declined, tentative, needs_action or null), done, owed and overdue. A viewing adds status and viewingId; an open house status and address; a deal_close status and stage; an external item status, location and recurring; a post status (scheduled, publishing or published), postId, channel, postKind and providerPostUrl.

Who sees what

• Events are listed on the owner's calendar and on the calendar of every teammate on the event.
• Expected closes: a member sees their own; an admin sees everyone's, or those of assigneeIds and teamIds.
• An admin reading a teammate gets their Fondaro events and viewings, never their external appointments.
• An event on a lead you cannot open still shows, with leadName: null.

Count overdue tasks

GET /calendar/summary

How many owed tasks are overdue.

curl "https://api.fondaro.com/calendar/summary?tz=Europe/Madrid" \  -H "Authorization: Bearer $SESSION_TOKEN"

{ "overdueCount": 3 }

List overdue tasks

GET /calendar/overdue

The overdue tasks themselves, oldest first, at most 200.

curl "https://api.fondaro.com/calendar/overdue?tz=Europe/Madrid" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "items": [    {      "eventId": "0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f",      "title": "Call about the offer",      "startsAt": "2026-10-01T00:00:00.000Z",      "endsAt": "2026-10-02T00:00:00.000Z",      "allDay": true,      "date": "2026-10-01",      "leadId": 4182,      "leadName": "A. Buyer",      "ownerUserId": "user_2a"    }  ],  "truncated": false}

truncated is true when more than 200 were overdue.

Read busy time

GET /calendar/busy

The caller's booked time for conflict warnings: events they own or are on that are neither done nor cancelled, their own appointments and the viewings they host. Read from what Fondaro holds; no request goes to Google or Microsoft.

curl "https://api.fondaro.com/calendar/busy?from=2026-10-07T09:00:00Z&to=2026-10-07T10:00:00Z" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "busy": [    {      "key": "external:8c7d6e5f-4a3b-4c2d-9e1f-0a9b8c7d6e5f",      "kind": "external",      "startsAt": "2026-10-07T09:15:00.000Z",      "endsAt": "2026-10-07T10:00:00.000Z",      "allDay": false,      "title": "Dentist",      "eventId": "8c7d6e5f-4a3b-4c2d-9e1f-0a9b8c7d6e5f"    }  ]}

Read a lead's next events

GET /calendar/lead/:leadId/next

A lead's overdue tasks and its next five events, with no date window. The lead may be on an event as its lead, as another lead or collaborator, or as the collaborator of a viewing.

curl "https://api.fondaro.com/calendar/lead/4182/next?tz=Europe/Madrid" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "overdue": [    {      "key": "event:0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f",      "eventId": "0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f",      "kind": "meeting",      "title": "Call about the offer",      "startsAt": "2026-10-01T08:00:00.000Z",      "endsAt": "2026-10-01T08:15:00.000Z",      "allDay": false,      "status": "confirmed",      "ownerUserId": "user_2a",      "leadId": 4182,      "leadName": "A. Buyer",      "viewingId": null,      "done": false,      "owed": true,      "overdue": true,      "canComplete": true    }  ],  "next": [],  "hasMore": false}

overdue holds at most 200, oldest first. next holds the next five events that are neither done nor cancelled, including one under way; hasMore says more follow. canComplete says whether you may tick it.

Read one event

GET /calendar/events/:id

One event in full, with its people. You can read your own events, any viewing's event and, as an admin, a teammate's Fondaro events.

curl "https://api.fondaro.com/calendar/events/6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b?tz=Europe/Madrid" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "id": "6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b",  "kind": "meeting",  "title": "Meeting with a buyer",  "description": "Bring the floor plans.",  "location": "Office",  "startsAt": "2026-10-07T09:00:00.000Z",  "endsAt": "2026-10-07T09:30:00.000Z",  "allDay": false,  "timezone": "Europe/Madrid",  "status": "confirmed",  "ownerUserId": "user_2a",  "people": [    { "kind": "lead", "leadId": 4182, "name": "A. Buyer", "email": "buyer@example.com", "invited": true, "response": "accepted" },    { "kind": "teammate", "userId": "user_2b", "name": "Ana Ruiz", "invited": false, "response": "accepted" }  ],  "attendeeCount": 2,  "sync": "synced",  "syncError": null,  "provider": "google",  "lead": { "id": 4182, "name": "A. Buyer" },  "viewing": null,  "canEdit": true,  "completedAt": null,  "owed": false,  "overdue": false,  "canComplete": true,  "taskLike": false,  "videoMissing": false}

A lead you cannot open reads with an empty name and no email.

Create an event

POST /calendar/events

Creates a task, an event, or a viewing of one of your listings. With a connected calendar the event is written there at once and the provider sends the invitations. Without one, an event that invites anyone is refused.

curl -X POST "https://api.fondaro.com/calendar/events" \  -H "Authorization: Bearer $SESSION_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "kind": "task",    "title": "Call A. Buyer",    "startsAt": "2026-10-08T10:00:00.000Z",    "endsAt": "2026-10-08T10:15:00.000Z",    "timezone": "Europe/Madrid",    "leads": [{ "leadId": 4182 }]  }'

{  "id": "0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f",  "kind": "meeting",  "title": "Call A. Buyer",  "startsAt": "2026-10-08T10:00:00.000Z",  "endsAt": "2026-10-08T10:15:00.000Z",  "lead": { "id": 4182, "name": "A. Buyer" },  "sync": "pending",  "owed": true,  "taskLike": true}

The response is the event as Read one event returns it. A viewing ignores connectedAccountId and calendarId and goes to the default calendar. The accounts and their calendars are listed by Connected inboxes.

Move or edit an event

PATCH /calendar/events/:id

Send only what changes. Takes the create fields except propertyListingId, ownerUserId, videoCall, connectedAccountId and calendarId.

• Moving keeps the length unless you send endsAt. Attendees who stay keep their answers.
• leads, teammateIds and attendees each replace their own group only when sent. leadId and inviteLead change the event's lead and keep the other leads.
• A kind different from the event's own re-applies its rule to the people already on it.
• A viewing's event moves the viewing. :id may be viewing:<viewingId>; the event is created first and the response carries its new id.
• An edit never moves an event to another calendar. Open houses are changed from the open house (400 CALENDAR_EVENT_OPEN_HOUSE).

curl -X PATCH "https://api.fondaro.com/calendar/events/6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b" \  -H "Authorization: Bearer $SESSION_TOKEN" \  -H "Content-Type: application/json" \  -d '{ "startsAt": "2026-10-07T11:00:00.000Z" }'

{  "id": "6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b",  "startsAt": "2026-10-07T11:00:00.000Z",  "endsAt": "2026-10-07T11:30:00.000Z",  "sync": "pending"}

Cancel an event

DELETE /calendar/events/:id

A meeting becomes cancelled and is removed from the owner's calendar, whose provider tells the attendees. A viewing is cancelled as a viewing (viewing:<viewingId> works here too). Open houses are cancelled from the open house.

curl -X DELETE "https://api.fondaro.com/calendar/events/6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b" \  -H "Authorization: Bearer $SESSION_TOKEN"

{ "id": "6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b", "status": "cancelled" }

Tick an event done

POST /calendar/events/:id/complete ticks it; DELETE /calendar/events/:id/complete unticks it.

Both are idempotent and return the event with completedAt set or cleared. The owner, a teammate on the event or an admin may tick it. A done task stays on its day, and ticking changes nothing in Google or Outlook. Your own appointments, viewings, open houses and cancelled events cannot be ticked.

curl -X POST "https://api.fondaro.com/calendar/events/0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f/complete" \  -H "Authorization: Bearer $SESSION_TOKEN"

{ "id": "0f9c3a1e-2b4d-4c6e-8f10-2a3b4c5d6e7f", "completedAt": "2026-10-08T10:20:00.000Z", "owed": false }

The CRM task endpoints and the MCP task tools follow the same rule: only the owner, a teammate on the event or an admin can tick, untick or delete a task.

Retry a calendar write

POST /calendar/events/:id/retry-sync

Writes the event to the owner's calendar again, or removes it there if cancelled. It also restores a viewing or open house deleted in Google or Outlook. Fondaro retries failed writes on its own every 15 minutes.

curl -X POST "https://api.fondaro.com/calendar/events/6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b/retry-sync" \  -H "Authorization: Bearer $SESSION_TOKEN"

{ "id": "6b1f0c2e-7d3a-4e5f-9a8b-1c2d3e4f5a6b", "sync": "synced", "syncError": null }

Webhooks

Every event made in Fondaro fires one created webhook:

• A task (a lead, nobody invited from outside the team) fires task.created.
• Any other event fires meeting.created, with leadIds listing every lead on it, the event's lead first.

An edit with kind: "task" that makes an event owed fires task.created; inviting someone onto a task fires meeting.created. Other edits fire nothing, and bulk task creation fires no webhooks. Ticking a task fires task.completed. See Integration reporting for payloads.

Errors

Errors carry a stable code.

Limits: a window or busy range is at most 42 days; overdue lists return at most 200 items; an event holds up to 20 leads, 50 teammates and 50 invited guests.