Integration reporting

The integrations API (/integrations/v1) lets your own automation read and write your organization's CRM: leads, deals, tasks, notes and tags, call and activity history, viewings, and webhooks for what changes. It is the API behind the n8n node, and any HTTP client can call it. For access as one person, use the REST API with an API key; this API stays for agency-wide automation and webhooks.

Authenticate

Send an integration key as a Bearer token:

curl https://api.fondaro.com/integrations/v1/whoami \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY"

{  "organizationId": "5b1f0c1e-8a54-4f1d-9d7e-3f2a1c9b7e21",  "organizationName": "Costa Homes",  "keyId": "0c9e1d2a-7b3f-4e8a-9d61-2b7a1c9e4d10",  "keyName": "n8n production",  "scopes": ["leads:read", "leads:write"]}

An integration key starts with fdr_n8n_. An organization admin creates it in Settings > Integrations > n8n; the full key is shown once. It acts for the whole organization within its scopes, and works until it is revoked or expires. A disabled organization's keys stop working. Property API keys (fondaro_pk_) and MCP credentials do not open these routes, and an integration key opens nothing else. See Authentication.

Scopes

A key created without a scope list gets every scope except viewings:read. A request without the scope its route needs returns 403.

Endpoints

Every lead payload carries companyName (string or null). POST /integrations/v1/leads accepts it; PATCH /integrations/v1/leads/:id/contact sets it, or clears it with null or an empty string (at most 255 characters).

The lead, deal, task and assignee writes accept an optional teamIds list (up to 20 team ids) next to their user ids. Each team becomes its current members when the request runs. One request assigns at most 50 people; past that it returns 400 with code: "ASSIGNEE_LIMIT_EXCEEDED" and writes nothing. See Teams.

List a lead's calls

GET /integrations/v1/leads/:id/calls

Returns the lead's calls, newest first, without recordings or transcripts.

curl "https://api.fondaro.com/integrations/v1/leads/10132/calls?limit=20" \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY"

{  "calls": [    {      "id": "3f1c2b9e-7a4d-4e0b-8c61-0d2e5f7a9b13",      "ownerId": "user_2abc",      "direction": "outbound",      "outcome": "success",      "status": "completed",      "durationSeconds": 184,      "startedAt": "2026-09-30T09:12:00.000Z",      "endedAt": "2026-09-30T09:15:04.000Z",      "hasRecording": true    }  ],  "total": 1,  "totalIsExact": true,  "hasMore": false,  "nextOffset": 1}

outcome is the call result (success, no_answer, busy, failed, invalid_number and similar), null when none was set. ownerId is the team member recorded as making or taking the call, and null when none was recorded. It is not the lead's current assignee: a lead reassigned after the call keeps the call's ownerId. Resolve it with GET /integrations/v1/users/:id.

List a lead's activity

GET /integrations/v1/leads/:id/activities

Returns the lead's history as typed entries, newest first. Each entry has type, occurredAt and one object named for its kind (call, note, task, email, statusChange, dealStageChange, deal, assigneeChange, document, viewing). Entries carry ids and short previews, never email bodies, note HTML or transcripts.

curl "https://api.fondaro.com/integrations/v1/leads/10132/activities?types=note,email&limit=20" \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY"

{  "entries": [    {      "type": "note",      "occurredAt": "2026-09-29T16:40:00.000Z",      "note": { "id": "a7d0...", "preview": "Wants a sea view, budget up to 1.2M", "authorId": "user_2abc" }    }  ],  "total": 14,  "totalIsExact": false,  "hasMore": true,  "nextOffset": 20}

The type filter applies before paging. Page with nextOffset until hasMore is false. When totalIsExact is false, total is a lower bound: count calls with the calls endpoint, not this one. A viewing appears on each of its client leads and on the collaborator lead that brought them.

List viewings

GET /integrations/v1/viewings

Returns viewings registered on your organization's listings, newest first (viewingAt, then id). Needs viewings:read. A viewing can have several clients: leadId is the viewing's lead and otherLeadIds lists the others, empty when there are none.

curl "https://api.fondaro.com/integrations/v1/viewings?leadId=10132&status=scheduled" \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY"

{  "viewings": [    {      "id": "9b2e4c1a-0d3f-4a7b-8e6c-5d4f3a2b1c0e",      "propertyListingId": "d41f0b7c-2e9a-4c5d-8f13-6a7b8c9d0e1f",      "leadId": 10132,      "otherLeadIds": [10133],      "collaboratorLeadId": null,      "agentUserId": "user_2abc",      "dealId": null,      "viewingAt": "2026-10-04T10:00:00.000Z",      "kind": "in_person",      "status": "scheduled",      "source": "dashboard",      "createdBy": "user_2abc",      "createdAt": "2026-09-30T08:00:00.000Z",      "updatedAt": "2026-09-30T08:00:00.000Z",      "notes": "Bring the keys for the guest house",      "notesTruncated": false    }  ],  "total": 1,  "hasMore": false,  "nextOffset": 1}

In the list, notes is the first 500 characters and notesTruncated says whether there is more. GET /integrations/v1/viewings/:id returns one viewing with its full notes, or 404.

Find leads by what they said

POST /integrations/v1/leads/semantic-search

Ranks leads by meaning across their notes, call transcripts and summaries, emails and messages.

curl -X POST https://api.fondaro.com/integrations/v1/leads/semantic-search \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY" \  -H "Content-Type: application/json" \  -d '{"query": "buyers who mentioned a garden near the beach", "maxResults": 10}'

{  "matches": [    {      "leadId": 10132,      "firstName": "Anna",      "lastName": "Berg",      "rank": 1,      "matchCount": 3,      "sourceCount": 2,      "bestMatchAt": "2026-09-12T14:03:00.000Z",      "evidence": [        {          "sourceType": "call_transcript",          "sourceId": "3f1c2b9e-7a4d-4e0b-8c61-0d2e5f7a9b13",          "occurredAt": "2026-09-12T14:03:00.000Z",          "snippet": "...a small garden, walking distance to the beach..."        }      ]    }  ],  "tookMs": 412,  "reranked": true}

sourceType is note, call_transcript, call_summary, email, message or lead_memory. reranked: false means the final ranking step was unavailable and the first-pass order was returned. The index covers about the last 24 months and fills shortly after records are written, so no match does not prove a lead does not exist.

Find leads for a listing

POST /integrations/v1/leads/listing-match

Ranks leads whose wishes fit a listing. Send exactly one of propertyListingId or listingRef.

curl -X POST https://api.fondaro.com/integrations/v1/leads/listing-match \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY" \  -H "Content-Type: application/json" \  -d '{"listingRef": {"source": "resales_online", "id": "R123456"}, "maxResults": 10}'

The response has the same shape as meaning-based search.

Webhooks

Subscribe

POST /integrations/v1/subscriptions

Sends the events you choose to an HTTPS URL. Subscribing the same events to the same URL again returns the existing subscription and reactivates it.

curl -X POST https://api.fondaro.com/integrations/v1/subscriptions \  -H "Authorization: Bearer $FONDARO_INTEGRATION_KEY" \  -H "Content-Type: application/json" \  -d '{"targetUrl": "https://example.com/fondaro", "eventTypes": ["lead.created", "message.received"]}'

{  "id": "6e5d4c3b-2a19-4807-b6f5-e4d3c2b1a090",  "secret": "4f2a...c91e",  "eventTypes": ["lead.created", "message.received"],  "targetUrl": "https://example.com/fondaro"}

Store secret: it signs every delivery. GET /integrations/v1/subscriptions/:id returns id, eventTypes, targetUrl and isActive; DELETE /integrations/v1/subscriptions/:id removes it and returns { "success": true }. An organization can hold 25 subscriptions.

Events

Payloads carry ids and times, not message bodies, subjects or addresses (call.analyzed excepted). Read details back with the endpoints above. A message from someone who is not a lead yet fires nothing, and neither does mail brought in when a mailbox is first connected.

Deliveries

Each delivery is a POST with a JSON body and three headers:

{  "event": "message.received",  "deliveryId": "b1c2d3e4-f5a6-4b7c-8d9e-0f1a2b3c4d5e",  "occurredAt": "2026-09-25T10:00:02.000Z",  "data": {    "organizationId": "5b1f0c1e-8a54-4f1d-9d7e-3f2a1c9b7e21",    "leadId": 10132,    "messageId": "c2a4e1f0-6b7d-4c3e-9a1f-0e2d3c4b5a69",    "messageType": "message",    "channel": "whatsapp",    "direction": "inbound",    "connectedAccountId": "8e7d6c5b-4a39-4281-9f0e-1d2c3b4a5968",    "userId": null,    "occurredAt": "2026-09-25T10:00:00.000Z"  }}

Verify the signature over the raw body and reject old timestamps (for example older than 5 minutes). Answer with any 2xx within 10 seconds; anything else is retried with backoff, up to 8 attempts. A subscription that fails 20 times in a row is deactivated; subscribe again to turn it back on. Delivery is at least once, so deduplicate on deliveryId.

For message.received, message.sent, message.updated and message.deleted, messageType is email or message, channel is email, whatsapp, linkedin, instagram or telegram, and userId is the member who pressed Send in Fondaro (null for inbound messages and for messages sent from the agent's own phone or mail app). On message.updated and message.deleted, occurredAt is when the message was changed, and you read its current text back from the lead's timeline (a deleted message has none).

meeting.created carries organizationId, eventId, leadId, leadIds (every lead and collaborator on the meeting, its own lead first), viewingId, ownerId, startsAt, endsAt and occurredAt. meeting.responded carries organizationId, eventId, leadId, ownerId, response (accepted, declined or tentative) and occurredAt.

Errors and limits

Each key may make 120 requests per minute. The two meaning-based search routes also share 30 requests per minute per key and per organization.