Discover/Bizapedia API
live

Bizapedia APIbizapedia.com ↗

Access Bizapedia company profiles via API. Retrieve filing details, registered agents, principal addresses, and contacts for US businesses by state and slug.

Endpoint health
verified 13h ago
get_company_details
search_companies_by_address
get_predefined_companies
search_companies_by_name
4/4 passing latest checkself-healing
Endpoints
4
Updated
13h ago

What is the Bizapedia API?

The Bizapedia API exposes 4 endpoints that return structured company profile data from Bizapedia's public business directory. Use get_company_details to fetch a single company's state filing number, filing date, filing status, principal address, registered agent name and address, and a list of principals with their roles. Search endpoints let you find companies by name or street address across all US states or filtered to one.

This call costs1 credit / call— charged only on success
Try it
The company's URL slug as it appears in the Bizapedia URL path (e.g. 'genuine-parts-company', 'five-oaks-farm-of-georgia-llc'); also emitted as search_companies_by_name.results[*].slug.
Two-letter US state code, lowercase (e.g. 'ga', 'tn').
→ api.parse.bot/scraper/f1f62669-60b8-4b29-aa56-ebe8fe77d53f/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/f1f62669-60b8-4b29-aa56-ebe8fe77d53f/get_company_details?slug=genuine-parts-company&state=ga' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 4 totalmissing one? ·

Fetch detailed business information for a specific company by state and URL slug. Returns filing details, principal address, registered agent, and contacts extracted from the company's public profile page. Each contact's role is the title Bizapedia shows in the profile's Principals block (e.g. 'Chief Executive Officer', 'Organizer', 'Secretary'); it is null only when the site lists the person without a title. The slug is the URL path component for the company on Bizapedia (e.g. 'genuine-parts-company') and can be resolved from a name with search_companies_by_name. The call costs two upstream requests (page and a verification handshake). A 410/404 means the company page no longer exists.

Input
ParamTypeDescription
slugrequiredstringThe company's URL slug as it appears in the Bizapedia URL path (e.g. 'genuine-parts-company', 'five-oaks-farm-of-georgia-llc'); also emitted as search_companies_by_name.results[*].slug.
staterequiredstringTwo-letter US state code, lowercase (e.g. 'ga', 'tn').
Response
{
  "type": "object",
  "fields": {
    "url": "string, full URL of the company page",
    "contacts": "array of objects with 'name' (string) and 'role' (string title from the Principals block, or null when the site shows no title) fields",
    "file_number": "string, state filing number",
    "filing_date": "string, date of filing in YYYY-MM-DD format",
    "filing_state": "string, two-letter state code",
    "business_name": "string, official business name",
    "filing_status": "string, current filing status",
    "registered_agent": "object with 'name' (string) and 'address' (string) fields",
    "principal_address": "string, formatted principal business address"
  },
  "sample": {
    "data": {
      "url": "https://www.bizapedia.com/ga/genuine-parts-company.html",
      "contacts": [
        {
          "name": "HERBERT C. NAPIER",
          "role": "Chief Financial Officer"
        },
        {
          "name": "VACANT VACANT",
          "role": "Secretary"
        },
        {
          "name": "WILLIAM P. STENGEL",
          "role": "Chief Executive Officer"
        }
      ],
      "file_number": "J505042",
      "filing_date": "1928-05-07",
      "filing_state": "GA",
      "business_name": "Genuine Parts Company",
      "filing_status": "Active/Compliance",
      "registered_agent": {
        "name": "THE CORPORATION COMPANY",
        "address": "410 Peachtree Parkway Suite 4245, Cumming, GA, 30041"
      },
      "principal_address": "2999 Wildwood Parkway, Atlanta, GA, 30339"
    },
    "status": "success"
  }
}

About the Bizapedia API

Company Profile Data

get_company_details takes a two-letter lowercase state code and a slug (the company's URL path segment, e.g. genuine-parts-company) and returns a structured profile: business_name, file_number, filing_date (YYYY-MM-DD), filing_status, filing_state, principal_address, and a registered_agent object with name and address fields. The contacts array lists each principal with their name and role as Bizapedia shows it in the Principals block — role is null when the source shows no title for that contact.

Search by Name or Address

search_companies_by_name accepts a name string (minimum 5 characters) and an optional state filter. It returns up to 20 match objects, each carrying business_name, slug, state, entity_type, filing_date, and city. The truncated boolean signals when the source reports more matches than the 20 returned. The slug and state values from each result map directly to the required inputs of get_company_details, making it straightforward to chain a search into a profile fetch.

search_companies_by_address works the same way but searches by street address. Required inputs are address (minimum 5 characters) and city (minimum 3 characters); state and postal_code are optional narrowing filters. Each result includes an addresses array of the full location strings the site lists for that company, plus entity_type, filing_date, slug, and state.

Bulk Retrieval

get_predefined_companies takes no inputs and returns a batch of company profiles across Georgia and Tennessee. Results follow the same shape as get_company_details, with error objects included in the array for any companies whose pages are no longer available on Bizapedia. This is useful for recurring monitoring of a fixed company set without managing slugs individually.

Reliability & maintenanceVerified

The Bizapedia API is a managed, monitored endpoint for bizapedia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bizapedia.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official bizapedia.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
13h ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Verify a vendor's current filing status and registered agent before onboarding them as a supplier.
  • Build a contact list of principals for companies registered at a specific street address.
  • Disambiguate same-name businesses in different states using search_companies_by_name with a state filter.
  • Monitor a fixed set of companies for filing status changes using get_predefined_companies on a schedule.
  • Map all businesses filing from a shared address to identify related entities.
  • Collect entity type and filing date metadata for a batch of companies to support due diligence workflows.
  • Resolve a company's official legal name and state file number from a partial name string.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Bizapedia offer an official developer API?+
Bizapedia does not publish a documented public developer API for programmatic access to its business data.
What does the contacts array in get_company_details actually contain?+
It contains one object per person listed in the Principals section of the company's Bizapedia profile. Each object has a name string and a role string matching the title Bizapedia displays — for example 'Agent' or 'Manager'. When the profile shows a person with no title, role is returned as null rather than omitted.
Are search results paginated, and what happens when there are more than 20 matches?+
The search endpoints return at most 20 results per call. When the source reports additional matches beyond those 20, the truncated field in the response is set to true. There is no offset or page parameter to retrieve the next batch. To narrow a large result set, add or tighten the optional state filter in search_companies_by_name, or add postal_code or state in search_companies_by_address.
Does the API cover states beyond Georgia and Tennessee for get_predefined_companies?+
The predefined set in get_predefined_companies covers Georgia and Tennessee only. get_company_details and both search endpoints work across all US states that Bizapedia indexes — you supply the state parameter yourself. The predefined endpoint does not currently cover other states, but you can fork the API on Parse and revise the predefined list to include companies in additional states.
Does the API return phone numbers, email addresses, or other contact channels for principals?+
No contact channel data beyond name and role is currently exposed for principals. The contacts array contains name and role only — Bizapedia does not display phone or email for principals on public company pages. You can fork this API on Parse and revise it to pull in any additional fields Bizapedia surfaces on those pages.
Page content last updated . Spec covers 4 endpoints from bizapedia.com.
Related APIs in B2b DirectorySee all →