Bizapedia APIbizapedia.com ↗
Access Bizapedia company profiles via API. Get filing details, registered agents, principal addresses, and contacts for US businesses by state and slug.
What is the Bizapedia API?
The Bizapedia API exposes 2 endpoints that return structured business profile data sourced from Bizapedia's public company pages. Using get_company_details, you can retrieve 8+ fields per company — including file number, filing date, filing status, registered agent, principal address, and contacts — by supplying a two-letter state code and the company's URL slug. A second endpoint, get_predefined_companies, supports bulk retrieval across Georgia and Tennessee without requiring individual slug lookups.
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'
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. The slug is the URL path component for the company on Bizapedia (e.g. 'genuine-parts-company'). A 410/404 means the company page no longer exists.
| Param | Type | Description |
|---|---|---|
| slugrequired | string | The company's URL slug as it appears in the Bizapedia URL path (e.g. 'genuine-parts-company', 'five-oaks-farm-of-georgia-llc'). |
| staterequired | string | Two-letter US state code, lowercase (e.g. 'ga', 'tn'). |
{
"type": "object",
"fields": {
"url": "string, full URL of the company page",
"contacts": "array of objects with 'name' (string) and 'role' (string or null) 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": "John Doe",
"role": null
},
{
"name": "Jane Doe",
"role": null
},
{
"name": "John Doe",
"role": null
}
],
"file_number": "J505042",
"filing_date": "1928-05-07",
"filing_state": "GA",
"business_name": "Genuine Parts Company",
"filing_status": "Active/Owes Current Year AR",
"registered_agent": {
"name": "CT CORPORATION",
"address": "106 Colony Park Drive Ste. 800-B, Cumming, GA, 30040"
},
"principal_address": "2999 Wildwood Parkway, Atlanta, GA, 30339"
},
"status": "success"
}
}About the Bizapedia API
What the API Returns
The get_company_details endpoint accepts two required parameters: state (a lowercase two-letter US state code, e.g. ga) and slug (the URL path component identifying the company on Bizapedia, e.g. genuine-parts-company). The response includes the company's official business_name, state file_number, filing_date (YYYY-MM-DD), filing_status, and filing_state. It also returns principal_address as a formatted string, a registered_agent object containing both name and address, and a contacts array where each entry has a name and an optional role.
Bulk Retrieval
The get_predefined_companies endpoint requires no inputs and returns an array of company detail objects for a fixed set of companies across Georgia and Tennessee. This is useful when you want to pull a batch of profiles without constructing individual slug/state pairs. For companies whose Bizapedia pages have been removed or are unavailable, the endpoint returns an error object in place of the profile — so callers should handle mixed result arrays.
Coverage and Scope
Coverage is limited to companies that have a public profile page on Bizapedia. The data reflects state-level business registry information: formation filings, registered agent designations, and publicly listed contact names with roles. Fields like file_number and filing_date are sourced from the state filing record displayed on each profile. Not every company on Bizapedia will have a complete contacts array — availability depends on what is listed on the public page.
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.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Verify a company's current filing status and state file number before entering a business relationship.
- Identify the registered agent name and address for service-of-process or compliance research.
- Build a contact list with names and roles pulled from the
contactsarray on company profiles. - Cross-reference
filing_dateandprincipal_addresswhen researching newly formed entities. - Bulk-retrieve business profiles for Georgia and Tennessee companies using the predefined endpoint.
- Enrich a CRM with official business names and formation dates sourced from state filing records.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 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.
Does Bizapedia offer an official developer API?+
What does the `contacts` field in `get_company_details` actually contain?+
contacts field is an array of objects, each with a name (string) and a role (string or null). Role reflects the title or capacity listed alongside the contact on the profile page — it may be null if no role is shown. The number of contacts varies by company.Does the API cover states other than Georgia and Tennessee?+
get_company_details accepts any two-letter US state code as the state parameter, so lookups are not restricted to Georgia and Tennessee — you just need the correct slug for the company in that state. The get_predefined_companies endpoint, however, only covers a fixed set of companies in Georgia and Tennessee. You can fork this API on Parse and revise it to expand the predefined list or add a search-by-name endpoint for additional states.Can I search for companies by name or industry rather than by slug?+
What happens when a company's page is no longer available on Bizapedia?+
get_company_details, an error will be returned rather than a profile object. In get_predefined_companies, the results array may contain error objects in place of company profiles for any companies whose pages have been removed. Callers should check each array item for error shape before attempting to read profile fields.