LollyMap

Useful public data, with clear boundaries.

This page explains what automated systems can discover on LollyMap, which interface is documented, and what responsible reuse requires.

What can be accessed

LollyMap allows crawling of its public routes. The site’s robots policy excludes private, administrative, backup, test and operational areas.

Public listings can be discovered through the main sitemap and specialised sitemaps for service and Lost & Found pages. Some page types also expose Schema.org metadata.

Lost & Found JSON API

The confirmed public API endpoint is:

GET https://lollymap.com/api/lostfound.php

Use type=lost or type=found. The optional city parameter filters by city; limit defaults to 5 and is capped at 100 records.

https://lollymap.com/api/lostfound.php?type=lost&city=Milano&limit=5
Open the live sandbox Read the API documentation

Responsible reuse

Public availability does not remove privacy, database, copyright or data-protection obligations. In particular, Lost & Found reports may contain user-submitted details intended to help reunite an animal with its owner.

  • Use only the data needed for a clear, legitimate purpose.
  • Do not build contact lists or republish personal details out of context.
  • Respect deletion, correction and expiry signals.
  • Identify LollyMap as the source and link to the relevant public page when republishing.
  • Contact LollyMap before large-scale or commercial reuse.

No blanket open-data licence is granted by this page. If your project requires bulk access, guaranteed availability or contractual reuse rights, contact us first.

Accuracy and verification

Public records may come from several sources and can become incomplete or outdated. A public listing is not automatically a verified listing. See the data trust page for the distinction and the available correction paths.

Read the data trust guide Discuss an integration