UrbanKit Studio — Free GIS & Mailing Tools for Planners

    URBANKIT/STUDIO
    FREE · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY · OPEN SOURCE
    ATLAS · COUNTY·FL·FIPS 12086

    Miami-Dade County, FL
    parcel REST API.

    Public ArcGIS MapServer endpoint for Miami-Dade County parcel data. URL, supported fields, and a working sample query — copy it, or open it directly in the UrbanKit parcel lookup tool.

    MapServer · LAYER 26 · PARCELS @ PAPARCEL
    https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/26
    License
    Public records (terms)
    Last verified
    2026-05-11
    Status
    Live
    — Sample query
    https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/26/query?where=UPPER(TRUE_OWNER1) LIKE UPPER('%SMITH%')&outFields=FOLIO,TRUE_OWNER1,TRUE_SITE_ADDR,TRUE_SITE_CITY&returnGeometry=false&f=json&resultRecordCount=10

    Open this URL in a browser tab to see the raw ArcGIS JSON response.

    — Searchable fields
    Searchable fields for Parcels @ PaParcel
    Field nameLabelSearchable
    FOLIOFolio Number YES
    TRUE_OWNER1Owner Name (Primary) YES
    TRUE_OWNER2Owner Name 2 YES
    TRUE_OWNER3Owner Name 3 YES
    TRUE_SITE_ADDRSite Address YES
    TRUE_SITE_CITYSite City YES
    TRUE_SITE_ZIP_CODESite ZIP YES
    TRUE_MAILING_ADDR1Mailing Address YES
    — Notes

    44 fields confirmed. Layer 26 is within the 80-layer MD_LandInformation MapServer. Fields include TRUE_OWNER1/2/3, TRUE_SITE_ADDR, TRUE_MAILING_ADDR1-3, DOR_CODE_CUR, DOR_DESC, PRIMARY_ZONE, SUBDIVISION, BEDROOM_COUNT, BATHROOM_COUNT, YEAR_BUILT, LAND_VAL_CUR, BUILDING_VAL_CUR, TOTAL_VAL_CUR, SALE_DATE, SALE_PRICE, LOT_SIZE. Owner search works via UPPER() LIKE on TRUE_OWNER1. Folio number is the Miami-Dade parcel identifier (13 digits). Also in this service: Property @ PaGis (layer 24) — point layer, fewer fields.

    — Source

    Miami-Dade County Information Technology Department GIS — https://gis-mdc.opendata.arcgis.com/

    How to use this REST endpoint

    Two paths from URL to result

    1. Open in Parcel Lookup — click the button on the endpoint card. The lookup tool loads the layer, auto-detects fields, and gives you a search box. No code, no API keys, just a browser.
    2. Query directly — append /query?where=…&outFields=*&f=jsonto the URL. The sample query above is a working example you can paste into a browser tab to see the raw JSON response.

    Why field names vary by county

    Counties publish parcel data through their own ArcGIS Server installations, each with its own schema. One county uses APN, another uses PIN, a third uses PARCEL_ID. Some expose owner names; others keep them on a separate assessor's portal. The searchable fields list above reflects what this county actually publishes — not what you might expect from a national standard (there isn't one).

    For background, see What is an APN?

    What to do with the results

    • Generate a public-notice mailing list — pipe the parcel layer URL into Radius Notice to buffer around an address and select neighboring owners.
    • Print Avery 5160 labels — export the result CSV and drop it into CSV → Labels.
    • Pull individual parcel records — use Parcel Lookup directly to grab zoning, assessed value, and ownership for one property at a time.

    Quick FAQs

    This URL gives me a CORS error in my own app — what now?

    Many county servers allow public reads but block browser cross-origin requests. The UrbanKit parcel lookup tool fetches directly from your browser; if it works there, the layer is technically public. For your own integration, you may need a same-origin proxy or server-side fetch.

    The endpoint loaded last week and now returns 404. Did the URL change?

    Possibly — counties move services without warning. We re-verify entries weekly and flag stale ones. If you're seeing a fresh 404, please let us know and we'll update the listing.

    Are these endpoints free to query at scale?

    Most are. Public ArcGIS layers don't typically rate-limit individual reads, but heavy programmatic use can trigger throttling at the host level. Be respectful — query what you need.

    View all FAQs →

    — Continue