Activity and viewings

Record viewings on your own listings and read everything that happened to a listing (viewings, changes, deal moves and brochures) as one feed.

These routes take a signed-in dashboard session with an active organization (Authorization: Bearer <session token>); a property API key is refused. To read viewings with a key, use GET /integrations/v1/viewings (see Integrations API). A listing outside your organization returns 404.

Any member can read and register viewings. A member can change or delete only viewings they created; an admin can change any.

List viewings

GET /properties/:id/viewings

curl "https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4/viewings?limit=20" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "viewings": [    {      "id": "67444de5-bfa4-4aa4-87c3-a1b2f1a4af59",      "propertyListingId": "29a1e184-237a-40c8-a1fe-624b0bcbb2f4",      "leadId": 4312,      "otherLeadIds": [4318],      "collaboratorLeadId": null,      "agentUserId": "user_2abc123",      "dealId": null,      "viewingAt": "2026-10-08T09:30:00.000Z",      "kind": "in_person",      "status": "scheduled",      "notes": "Meet at reception.",      "source": "user",      "createdBy": "user_2abc123"    }  ],  "total": 1,  "hasMore": false}

Newest viewingAt first. kind is in_person or virtual; status is scheduled, completed, cancelled or no_show. Deleting a linked lead or deal clears the link, never the viewing.

Register a viewing

POST /properties/:id/viewings

curl -X POST https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4/viewings \  -H "Authorization: Bearer $SESSION_TOKEN" \  -H "Content-Type: application/json" \  -d '{"viewingAt":"2026-10-08T09:30:00Z","kind":"in_person","leadId":4312}'

Returns the created viewing. A member may link only leads assigned to them; an admin may link any lead in the organization. Linking a lead grants no access to it.

Change or delete a viewing

PATCH /viewings/:viewingId

Takes the create fields, all optional. A key you leave out is unchanged; otherLeadIds replaces the other clients, and [] removes them; null clears leadId, collaboratorLeadId, agentUserId, dealId or notes. A new viewingAt does not recalculate status: send it too.

curl -X PATCH https://api.fondaro.com/viewings/67444de5-bfa4-4aa4-87c3-a1b2f1a4af59 \  -H "Authorization: Bearer $SESSION_TOKEN" \  -H "Content-Type: application/json" \  -d '{"status":"completed","notes":"Wants a second visit."}'

DELETE /viewings/:viewingId

{ "success": true }

Read activity

GET /properties/:id/activity

One feed of a listing's viewings, changes, deal events and brochures, newest first.

curl "https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4/activity?types=viewing,deal" \  -H "Authorization: Bearer $SESSION_TOKEN"

{  "entries": [    {      "type": "viewing",      "date": "2026-10-08T09:30:00.000Z",      "viewing": { "id": "67444de5-bfa4-4aa4-87c3-a1b2f1a4af59", "kind": "in_person", "status": "scheduled" },      "lead": { "id": 4312, "firstName": "Alex", "lastName": "Morgan" },      "collaborator": null    }  ],  "total": 1,  "hasMore": false}

Entry types: viewing (with lead and collaborator names), change (a history event), deal-stage-change, deal-won and deal-lost (all under the deal filter), and brochure. Page with hasMore and offset; total can be a lower bound for long histories.

Errors