Phila Gov Polling Places API

Name: Polling Places API
Brand: Polling Places API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationPlaces Searchnone1 EndpointsREST

For Agents

Look up polling place locations in Philadelphia by ward/division, accessibility features, or building type. Returns addresses and facility details for voter assignment.

Install Jentic One Beta

Connect the Polling Places API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Polling Places API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Polling Places API.

Look up polling places by ward and division number for voter assignment

Filter polling locations by ADA accessibility rating

Retrieve building addresses and facility types for each polling place

GET STARTED

Start building with Polling Places API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Polling Places API for, with concrete tasks.

★ Voter Polling Place Lookup

Help Philadelphia voters find their assigned polling place based on ward and division numbers. The API returns the specific address and building name for each ward/division combination, enabling civic apps and chatbots to direct voters to the correct location on election day. The dataset is maintained by the City of Philadelphia and updated before each election cycle.

Query the Polling Places API for ward 5, division 12 and return the polling place address and building name

Accessibility Planning for Elections

Identify polling places by their accessibility rating to ensure ADA compliance and plan accessibility accommodations. Election administrators use this data to prioritize upgrades, assign accessible machines, and route voters with mobility needs to appropriate locations. The accessibility field indicates the building's wheelchair accessibility status.

Retrieve all polling places and filter for locations with full wheelchair accessibility ratings

AI Agent Civic Data Integration via Jentic

AI agents serving Philadelphia residents can look up polling locations through Jentic to answer voter questions during election season. The agent searches for polling place operations, loads the endpoint schema, and queries by ward/division to provide accurate location information without managing API credentials or endpoints directly.

Search Jentic for 'find polling place in Philadelphia', load the Polling Places API schema, and query for the polling location assigned to ward 22 division 3

Key Endpoints

1 endpoints — the philadelphia polling places api provides access to the official list of polling locations in the city of philadelphia.

METHOD

PATH

DESCRIPTION

GET

Query polling places with optional ward, division, accessibility, and building type filters

GET

Query polling places with optional ward, division, accessibility, and building type filters

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Polling Places API requires no authentication. Jentic still provides value through structured discovery — agents find the API by intent without needing to know the endpoint URL or parameter format.

Intent-based discovery

Agents search by intent (e.g., 'find polling place in Philadelphia') and Jentic returns the Polling Places API operation with its query parameter schema, so the agent can construct the correct request without browsing city documentation.

Time to first call

Direct integration: under 1 day (no auth, simple GET). Through Jentic: under 15 minutes — search, load schema, execute. Jentic's value here is discovery and schema standardization rather than credential management.

FAQs

Specific to using Polling Places API through Jentic.

What authentication does the Polling Places API use?

The Philadelphia Polling Places API requires no authentication. It is a public open-data endpoint accessible without API keys or tokens. Through Jentic, the API is still discoverable via intent search so agents can find and call it without knowing the base URL.

Can I look up a specific polling place by ward and division number?

Yes. The GET / endpoint accepts ward and division as query parameters. Each ward/division combination maps to exactly one polling place, so you receive the specific address, building name, and accessibility rating for that location.

How often is the polling places data updated?

The City of Philadelphia updates the polling places dataset before each election cycle. Changes reflect new building assignments, accessibility upgrades, and ward redistricting. The data is considered authoritative for the current election period.

Does the API include accessibility information for each polling place?

Yes. Each polling place record includes an accessibility rating field that indicates the building's wheelchair accessibility status. You can also filter the query to return only locations that meet a specific accessibility threshold.

How do I query Philadelphia polling places through Jentic?

Search Jentic for 'find polling place in Philadelphia' to discover the Polling Places API. Load the operation schema to see available query parameters (ward, division, accessibility, building type), then execute the call. Since this API has no auth, Jentic handles only the discovery and schema aspects.