Ta strona nie została jeszcze przetłumaczona na Twój język. Wyświetlamy wersję angielski (Wielka Brytania).

API overview

Make your first Fondaro API call with an API key that acts as you, and see which credential and which page covers each part of the API.

The Fondaro API lets your own code do what you do in Fondaro: work your leads, tasks, deals and notes, search and show listings, and send brochures and documents. One API key acts as the person who made it, with the access that person has. This page gets you to a first call and shows where each area lives.

Find the base URL

https://api.fondaro.com

Every path in these docs is relative to it. Requests and responses are JSON over HTTPS unless a page says otherwise (file uploads use multipart/form-data). The API is for servers: call it from your backend, an automation or a script, not from a web page.

Make your first call

  1. Create a key on the API keys page (Settings › Integrations › For developers › API keys). See API keys. Copy it when it is shown: you see it once.
  2. Save it as an environment variable:
bash
export FONDARO_API_KEY="fondaro_pk_..."
  1. Ask the API who the key acts as:
bash
curl https://api.fondaro.com/v1/me \  -H "Authorization: Bearer $FONDARO_API_KEY"
json
{  "user": { "id": "user_2abcDEF", "name": "Maria Lopez", "email": "maria@youragency.com" },  "organization": { "id": "b7c1e0a2-1d4f-4e55-9a31-0c2f8d6e7a10", "name": "Your Agency" },  "role": "member",  "entitled": true,  "key": {    "id": "a1b2c3d4-5678-4abc-9def-123456789abc",    "name": "Reporting script",    "prefixHint": "fondaro_pk_Q",    "scopes": ["crm:read"],    "expiresAt": "2027-01-02T12:00:00.000Z"  }}

GET /v1/me needs no scope: any valid key with an owner can say who it is.

  1. List your five newest leads (needs crm:read):
bash
curl "https://api.fondaro.com/v1/leads?limit=5" \  -H "Authorization: Bearer $FONDARO_API_KEY"
  1. Create a lead (needs crm:write). Send an Idempotency-Key so a retry never creates a second lead:
bash
curl -X POST https://api.fondaro.com/v1/leads \  -H "Authorization: Bearer $FONDARO_API_KEY" \  -H "Idempotency-Key: 6f1c2d3e-0a4b-4c5d-8e9f-1a2b3c4d5e6f" \  -H "Content-Type: application/json" \  -d '{    "firstName": "Anna",    "lastName": "Berg",    "email": "anna@example.com",    "phoneNumber": "+46701234567",    "crmStatus": "lead"  }'

Every /v1 response carries an X-Request-Id header. Quote it if you contact support. See Errors and limits.

Choose a credential

Each part of the API takes its own credential. Authentication explains how to get and manage each one.

You want toCredentialHeader
Use the Fondaro API: CRM, listings, property search, brochures, documentsAPI key (fondaro_pk_…), acts as youAuthorization: Bearer <key>
Automate with n8n or Zapier (agency-wide, webhooks)Integration key (fdr_n8n_…)Authorization: Bearer <key>
Connect an AI clientMCP key (fdr_mcp_…) or browser sign-inSee MCP server
Call the routes the dashboard uses, as a signed-in memberSession tokenAuthorization: Bearer <session-token>

Find the area you need

AreaWhereScope
Leads, people, notes, tasks, calendar, deals, calls and emailsLeads, People, Notes, Tasks and calendar, Deals, Calls and conversationscrm:read, crm:write
Semantic search of your CRM and listing matchesSearchcrm:read
Viewings, open houses, collections and buyer requestsViewings and open houses, Networkproperties:read
Listings: search, create and updateSearch, Create and update listingsproperties:read, properties:write, media:write
Property search across your connected sourcesProperty sourcessources:read
BrochuresBrochuresbrochures:read, brochures:write (creating a brochure, adding or refreshing listings and renewing also need properties:read)
DocumentsDocuments (an active plan is required)documents:read, documents:write
Agency-wide automation and webhooksIntegration reportingIntegration key
AI clientsMCP server, Build with AIMCP key or sign-in
Dashboard featuresSetup, Inbox, Calling, Calendar, Teams and moreSession token

Listings and property search keep the paths they have always had, for example POST /properties/search. They now accept Authorization: Bearer too.

Browse the OpenAPI document

The whole Fondaro API describes itself in one OpenAPI 3 document at https://api.fondaro.com/openapi/fondaro.json. It is public. The listings and property search part alone stays at /openapi/properties.json for existing integrations. Every operation names the scope it needs in x-required-scopes. Browse it in the API reference, or point a code generator or AI assistant at it.

Read a response

A successful response is JSON: 200, 201 for a create, or 204 with no body for a delete. A single resource is the object itself. A list is wrapped in an object with data and hasMore:

json
{  "data": [{ "id": "c7d2…", "direction": "outbound" }],  "hasMore": true,  "nextOffset": 1}

Record ids are UUIDs, except leads (integers) and people (user ids such as user_2abcDEF). Times are ISO 8601 in UTC; date-only fields are YYYY-MM-DD. Errors and limits lists the error envelope, the paging styles, idempotency and rate limits.

Handle new versions

The /v1 routes only change by adding: new routes, new fields, new optional parameters. Build your client to ignore fields it does not know. A change that breaks a client would arrive as /v2, announced in the changelog, with /v1 still working.