Create and update listings

These endpoints manage your agency's own listings. Writes need the properties:write scope, reads properties:read, and photo uploads media:write. Every write is scoped to the key's organization. Send the key as Authorization: Bearer <key>, as in every example here. X-API-Key: <key> is still accepted on these routes, and so is Authorization: ApiKey <key>.

Upload photos

POST /properties/media/upload

Uploads one image (multipart field file, at most 20 MB). Every photo, thumbnail and floor plan on a listing must be an image your organization owns, so upload first and use the returned URLs.

curl -X POST https://api.fondaro.com/properties/media/upload \  -H "Authorization: Bearer fondaro_pk_abc123" \  -F "file=@living-room.jpg"

{  "success": true,  "images": {    "fullSize": "https://…/properties/images/3f2a.jpg",    "thumbnail": "https://…/properties/thumbnails/3f2a.webp"  }}

Put fullSize in images[].url and thumbnail in thumbnails[].url. Photos uploaded in the dashboard, a URL the listing already has in the same field, and a thumbnail that repeats an images URL in the same request are accepted too; any other URL is a 400 naming the field.

Fondaro records each upload's pixel size and returns it as images[].width and height; you never need to send them. An upload that no listing uses within 7 days may be removed, so upload right before you create or update.

Create a listing

POST /properties

Creates a listing as pending with a generated reference (FDR- and eight letters and digits). See Own-listing lifecycle for statuses.

curl -X POST https://api.fondaro.com/properties \  -H "Authorization: Bearer fondaro_pk_abc123" \  -H "Content-Type: application/json" \  -d '{    "listingType": "sale",    "propertyCategory": "residential",    "propertyType": "house_detached",    "city": "Marbella",    "countryCode": "ES",    "currency": "EUR",    "price": 1250000,    "bedrooms": 4,    "bathrooms": 3,    "livingArea": 320,    "plotArea": 800,    "areaUnit": "sqm",    "features": ["pool", "sea_view"],    "images": [{ "url": "https://…/properties/images/3f2a.jpg", "order": 0, "isFeatured": true }]  }'

{  "id": "29a1e184-237a-40c8-a1fe-624b0bcbb2f4",  "referenceNumber": "FDR-7KQ2MX9A",  "status": "pending",  "listingType": "sale",  "propertyType": "house_detached",  "city": "Marbella",  "price": 1250000,  "currency": "EUR",  "features": ["pool", "sea_view"],  "hasPool": true,  "hasSeaView": true,  "createdAt": "2026-10-02T10:00:00.000Z"}

Listing fields

Required on create:

Optional:

propertyType must belong to propertyCategory; other fits every category.

Amenities and furnishing

features lists amenities as slugs: pool, sea_view, garage, terrace, garden, air_conditioning, lift, beachfront, frontline_golf, panoramic_views, gated_complex, storage_room, built_in_wardrobes, luxury. Furnishing is its own field, furnished (no, partly, fully).

The older booleans (hasPool, hasSeaView, hasGarage, hasTerrace, hasGarden, hasAirConditioning, hasLift, isFurnished) still work:

• With features, the list is stored and the booleans follow it; booleans sent beside it are ignored.
• With booleans only, each adds or removes its own amenity and leaves every other slug as it was.
• furnished wins over isFurnished. Sent alone, isFurnished: true stores fully and false clears furnished.

Responses always carry both features and the booleans.

Read a listing

GET /properties/:id

Returns your own listing in any status, or another agency's active listing. Anything else is a 404.

curl "https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4?includeBranding=true" \  -H "Authorization: Bearer fondaro_pk_abc123"

{  "id": "29a1e184-237a-40c8-a1fe-624b0bcbb2f4",  "referenceNumber": "FDR-7KQ2MX9A",  "status": "active",  "city": "Marbella",  "price": 1250000,  "currency": "EUR",  "sharedCommission": 2.5,  "sharedCommissionNotes": "Paid on completion.",  "agent": { "firstName": "Ana", "lastName": "Ruiz", "title": "Sales agent" },  "organizationBranding": { "name": "Costa Homes" }}

Another agency's listing omits only what is private to it: commission, viewingInstructions and import-only additionalFeatures keys. It keeps the street address, postcode, exact coordinates and the shared-commission offer. The agent's email and phone numbers appear only when that agent shares their contact with the network (the default).

Update a listing

PUT /properties/:id

Send only the fields to change; any field you leave out keeps its value. Every create field is accepted, plus status (sold, rented or deleted; see Own-listing lifecycle).

curl -X PUT https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4 \  -H "Authorization: Bearer fondaro_pk_abc123" \  -H "Content-Type: application/json" \  -d '{"price": 1150000, "commission": 4.5}'

Returns the updated listing. The required create fields and the lists features, floorPlans, videoUrls and virtualTourUrls cannot be cleared with null; send [] to empty a list. A changed type is checked against the category and a changed point against the country. referenceNumber never changes.

Delete a listing

DELETE /properties/:id

Sets the listing's status to deleted. It leaves search and portal feeds but its history is kept.

curl -X DELETE https://api.fondaro.com/properties/29a1e184-237a-40c8-a1fe-624b0bcbb2f4 \  -H "Authorization: Bearer fondaro_pk_abc123"

{ "success": true }

Errors

Nothing is saved when a request is refused.