Public ArcGIS FeatureServer endpoint for Philadelphia County parcel data. URL, supported fields, and a working sample query — copy it, or open it directly in the UrbanKit parcel lookup tool.
https://services.arcgis.com/fLeGjb7u4uXqeF9q/arcgis/rest/services/PWD_PARCELS/FeatureServer/0/query?where=UPPER(owner1) LIKE UPPER('%SMITH%')&outFields=parcelid,owner1,address,brt_id&returnGeometry=false&f=json&resultRecordCount=10Open this URL in a browser tab to see the raw ArcGIS JSON response.
| Field name | Label | Searchable |
|---|---|---|
| parcelid | Parcel ID | YES |
| brt_id | BRT Account Number (OPA identifier) | YES |
| owner1 | Owner Name (Primary) | YES |
| owner2 | Owner Name 2 | YES |
| address | Street Address | YES |
| bldg_code | Building Code | NO |
| bldg_desc | Building Description | NO |
| gross_area | Gross Area (sq ft) | NO |
15 fields confirmed including parcelid, owner1, owner2, address, brt_id (BRT = Board of Revision of Taxes, now OPA = Office of Property Assessment), bldg_code, bldg_desc, gross_area, pin, tencode. Owner query tested and confirmed. The parcelid here is an integer OBJECTID; the brt_id (9-digit string, e.g. '171006315') is the stable OPA/BRT account number used in the assessor system. For deeper property assessment data (market value, sale price, exemptions, zoning), the OPA Properties dataset at opendataphilly.org/datasets/opa-properties-public has 78+ fields but is distributed as a CSV/API download rather than a REST FeatureServer with geometry. Philadelphia parcels are city-county unified (Philadelphia City = Philadelphia County).
City of Philadelphia — Office of Innovation and Technology (OIT) CityGeo / Philadelphia Water Department — https://data-phl.opendata.arcgis.com/
/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.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?
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.
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.
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.