Developers

API & endpoints.

The directory is available as read-only JSON. All endpoints are CORS-open, cacheable, and versioned via the schema field.

Endpoints

GET/api/listings.json Full directory of live listings, ordered as they appear in the source registry. Includes promoted flag per entry.

GET/api/promoted.json Promoted listings only — a convenience feed if you only want the featured set.

GET/api/listings/<slug>.json Per-listing detail. Same object as the full catalog, wrapped in { host, listing, schema }.

Sample response shape

Every listing object looks like this. Fields marked null may be present or omitted.

{
  "slug": "exteriorglow",
  "name": "Exterior Glow Landscaping",
  "tagline": "Full-service residential landscaping in the Treasure Valley.",
  "description": "…",
  "industry": "Landscaping",
  "category": ["home services", "outdoor", "residential"],
  "tags": ["landscaping", "lawn care", "boise", "treasure valley", "residential"],
  "status": "live",
  "promoted": true,
  "live_url": "https://exteriorglowlandscaping.com/",
  "showcase_url": "/business/exteriorglow/",
  "primary_image": "/assets/biz-exteriorglow-logo.jpg",
  "features": ["Front-yard transformations", "…"],
  "service_area": ["Boise", "Eagle", "Meridian", "Boise foothills"],
  "contact": { "phone": null, "email": null },
  "locality": { "city": "Boise", "region": "ID" }
}

Conventions

Status: live = public. Demos and inactive entries never appear in the API.
URLs: showcase_url is portal-relative (/business/<slug>/); live_url is the business's own site (absolute URL); primary_image is portal-relative (/assets/...).
Caching: JSON endpoints have a short public cache (~5 min). Safe to poll every few minutes.
Schema versioning: the top-level object carries a schema field. If we change the shape, the schema id bumps.

Try it

curl https://boisebusinessportal.com/api/listings.json | jq '.listings[] | .name'

curl https://boisebusinessportal.com/api/listings/edgyroot.json | jq '.listing.features'