Angi pros for a service in a city
Home-service pros listed on Angi for a service in a US city: id, name, profile link, logo, description, overall rating with the six sub-ratings (quality, value, professionalism, punctuality, responsiveness), review count, recommended percentage, best review, years in business, service area, business address, emergency services, free estimates, warranties, veteran-owned, bilingual, small jobs and commercial flags, payment methods, service hours, contact options, services offered, awards, photos and the sponsored flag; plus the page's ZIP codes and the latest reviews in that city. total is the number of pros. 10 per page; pass next_page back as page; null on the last page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
service | string | Service slug as in Angi's directory, e.g. plumbing, electrical, roofing, house-cleaning, hvac, landscaping, painting, handyman-service. Example: plumbing |
state | string | Two-letter US state, e.g. tx, ca, ny. Example: tx |
city | string | City slug, e.g. austin, los-angeles, new-york. Example: austin |
url | string | An angi.com/companylist/us/<state>/<city>/<service>.htm page instead of service, state and city. |
page | integer | Page number (default 1). Example: 1 |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/angi/v1/pros?service=plumbing" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/angi/v1/pros",
params={"service": "plumbing"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/angi/v1/pros");
url.searchParams.set("service", "plumbing");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).