Our biggest data product launch since ReZone joins the platform: Decisions — the rezonings, variances, and planning votes that set a project in motion long before a permit is filed — is now available in beta. This release also adds 3.5M new permits, 259 newly covered jurisdictions, and a new window_door project tag backfilled across history.
Decisions (Beta)Zoning and land-use decisions — approvals, rezonings, and variances from city council and planning meetings — are now available in beta across 600+ cities and roughly 200K records, about half the jurisdictions where we already track permits and growing weekly. Each decision is tied to its property and the people on it, and threads through to permits and jurisdictions. Available on every plan, including the free trial, and via Enterprise Data License.New window_door Project TagA window_door tag was backfilled across the full permit history — 3,494,250 permits now carry it. It sits alongside the tags you already use (electrical, solar, HVAC, roofing…) and changes nothing else.
Decisions is now in the API in beta — a new zoning and land-use data product — alongside a new GET /v2/meta/coverage endpoint, the additive window_door tag, and a faster, more resilient API. Several behavior and data changes need a look before they trip up your integration; review the Action Required sections first.
This release includes breaking changes to auth status codes, rate limiting, input validation, a permit status reclassification, and ~141K re-keyed permit IDs. Review the Action Required sections below.
Auth errors now return 401 (was 403)A missing or invalid X-API-Key now returns 401. We’ve kept 403 for a valid key that lacks admin access. If your client branches on status codes, point the auth case at 401.Rate limiting is live — 429Per-key rate limiting starts at 120 requests per 60 seconds, per key — well above normal use. Exceed it and you’ll get a 429 with a Retry-After header indicating how many seconds to wait. Make sure your client honors it and backs off. If that limit is too tight for your use case, contact support.contractor_name now requires at least 3 charactersOn GET /v2/contractors/search, a name under 3 characters now returns 422 instead of running a slow scan. Those names are still reachable by id, license, or geo.
141,793 permit IDs changed (~0.1%)These are the same permits — same jurisdiction, state, and permit_number — but their file_date shifted upstream, which moves the id. An old_id → new_id changelog is available; contact support to receive it. Most affected jurisdictions:
TX / Temple: 48,203
FL / Seminole County: 41,899
FL / Escambia County: 16,539
CA / Bakersfield: 10,838
Some address_id links moved
Newly linked to an address: 165,427 (0.11%)
Address link removed: 241,031 (0.17%)
Re-matched to a different address: 119,534 (0.08%)
When a re-scraped permit no longer carries a published address, we drop the link; our matching also tightened. If you cache address_id joins, re-sync the affected permits.“Approved” permits now map to IN_REVIEWA bare “Approved” means plans cleared review but fees aren’t paid yet — that’s pre-issuance, so it now maps to IN_REVIEW rather than ACTIVE. Only APPROVED FOR CONSTRUCTION stays ACTIVE. Adjust any status-based filtering to match.
GET /v2/decisions/search · GET /v2/decisionsThe approvals, rezonings, and variances that come out of city council and planning meetings — the decisions that set a project in motion long before a permit exists.
Coverage:600+ cities and roughly 200K decision records today — about half the jurisdictions where we already have permits, and growing weekly.
Record shape: each decision is tied to its property (address, coordinates, geo IDs) and to the people on it — applicants, owners, developers, architects, engineers — and threads through to permits and jurisdictions.
Access & price: on every plan, including the free trial, and via Enterprise Data License. During beta it’s 1 credit per decision; we’ll notify you before that changes.
Usage: works like /v2/permits/search — date range + geo_id required, cursor pagination, filters (asset class / category / subcategory / property type / project value / full-text), CSV export (≤1,000 rows), and batch-by-id at /v2/decisions.
Note: the source has no ZIP, so ZIP-level geo_id filters return 422.
GET /v2/meta/coveragePer-field fill rates for any state, county, city, ZIP, or jurisdiction, bucketed into tiers (under 10%, partial, over 80%). It saves you from filtering on a field in a place where we don’t ingest it and wondering why results look thin.
A window_door tag was backfilled across the full permit history — 3,494,250 permits now carry it. It works in permit_tags right away and changes nothing else.
New coverage command (under cities, counties, jurisdictions, states, zipcodes) wraps the new coverage endpoint, with date-window flags. It’s credit-exempt.
A decisions command is coming right behind this release.
The new Decisions dataset — zoning and land-use approvals, rezonings, and variances across 600+ cities and roughly 200K records — is available via Enterprise Data License, tied through to properties, people, permits, and jurisdictions.
Plenty of fresh coverage this release. We’ve added 7.5M new permits and 32 newly covered jurisdictions — Portland (OR), Orlando (FL), and a strong cluster of Twin Cities suburbs lead the way. +131K contractors were added too. Total permits grow by +7.19M (+5.4%).
Contractor Exports Return Full Result SetWhen exporting contractors from the Shovels Online web app, the resulting CSV was previously capped at the on-screen page size (50 rows). Exports now include all matching contractors up to 1,000 rows. No action required.
As part of routine pipeline updates, 280,010 permits (0.28%) had their id regenerated this release. The underlying permits are unchanged — same jurisdiction, state, and permit_number — but small shifts in file_date regenerate the id. Largest impacted: TN / Nashville (207K), FL / Seminole County (43K). Reply to your release notes email if you need the old_id → new_id changelog.
✅ No breaking changes. All existing integrations continue to work unchanged.
As part of routine pipeline updates, 280,010 permits (0.28%) had their id regenerated this release. The underlying permits are unchanged — same jurisdiction, state, and permit_number — but small shifts in file_date regenerate the id. Largest impacted: TN / Nashville (207K), FL / Seminole County (43K). Contact your account team if you need the old_id → new_id changelog.
This release marks a major milestone: Shovels is now powered entirely by our own data pipeline. We’ve transitioned away from our third-party permit data provider, giving us full end-to-end ownership over permit and contractor data quality, enrichment, and refresh cycles. While the total permit count is lower, the data is significantly richer — with improved field coverage across the board, a powerful new description_derived field on 81M permits, and better contractor intelligence. This is a one-time transition and a stronger foundation for everything going forward.
🔄 Fully Shovels-Owned Pipeline100% Shovels-Owned Data — faster iteration, better enrichment, consistent data provenance.All third-party provider data has been removed. This gives us full control over data quality and allows us to iterate faster on enrichments without vendor dependencies. Each future release will continue as a full snapshot, growing as we expand our coverage.
63.5% (+20%) — up from 43%, significantly richer licensing data on 2.5M contractors
Phone number coverage: 57.7% (+7%)
Email address coverage: 30.2% (+6%)
3 New State Licensing Boards AddedMassachusetts plumbing (~120K plumbers), North Carolina plumbing & electrical, and Iowa plumbing. CSL dataset grew to 3.14M records (+4%).
This release includes breaking changes. Please review carefully.Contractor IDs have been regenerated — if you’ve stored contractor IDs, they will need to be updated. We’ve prepared a contractor ID changelog mapping old IDs to new ones — 81.8% of new contractors are mapped. Download below:
For background on how contractor IDs work, see Why Contractor IDs Can Change.Permit count decreased — from 216M to 130M. 98M older permits sourced from a third-party provider were removed. The 118.3M permits that remain kept their original IDs — no action needed for those records.Contractor count decreased — from 3.9M to 2.5M. This reflects the removal of duplicates and low-quality records. The remaining 2.5M contractors are cleaner and more richly attributed.Some jurisdictions have reduced coverage — DC was dropped entirely. VT, RI, MA, CT, DE, WI, and NM lost >80% of permits due to the removal of third-party data. Coverage will grow as we expand our own data collection.first_seen_date has been reset — all values now fall between 2025-05-19 and 2026-03-28. Going forward, this field will accumulate normally with each biweekly release.Employee and resident records reduced — Employees: 38.1M → 12.8M. Residents: 45.9M → 27.6M.
This release transitions Shovels to a fully owned data pipeline, with richer field coverage, a new description_derived field on 81M permits, and better contractor intelligence.
⚠️ This release includes breaking changes. Contractor IDs have been regenerated and permit/contractor counts have changed significantly. See the Important Changes section below.
🔄 Fully Shovels-Owned Pipeline100% Shovels-Owned Data — faster iteration, better enrichment, consistent data provenance. All third-party provider data has been removed, giving us full control over data quality and enrichment without vendor dependencies.
Contractor IDs have been regenerated — if you’ve stored contractor IDs, they will need to be updated. We’ve prepared a contractor ID changelog mapping old IDs to new ones — 81.8% of new contractors are mapped. Download below:
For background on how contractor IDs work, see Why Contractor IDs Can Change.Permit count decreased — from 216M to 130M. 98M older third-party permits removed. The 118.3M permits that remain kept their original IDs.Contractor count decreased — from 3.9M to 2.5M, reflecting removal of duplicates and low-quality third-party records.Some jurisdictions have reduced coverage — DC dropped entirely. VT, RI, MA, CT, DE, WI, and NM lost >80% of permits.Field coverage changes — geocoding: 72% → 67%, inspection data: 15% → 3%, address ID: 78% → 74% (improving in upcoming releases).first_seen_date has been reset — all values now fall between 2025-05-19 and 2026-03-28.
This release transitions Shovels to a fully owned data pipeline, with richer field coverage, a new description_derived field on 81M permits, and improved contractor intelligence. Please review the Important Changes section for breaking changes.
Contractor IDs have been regenerated — if you’ve stored contractor IDs, they will need to be updated. We’ve prepared a contractor ID changelog mapping old IDs to new ones — 81.8% of new contractors are mapped. Download below:
For background on how contractor IDs work, see Why Contractor IDs Can Change.Permit count decreased — from 216M to 130M. 98M older third-party permits removed. The 118.3M permits that remain kept their original IDs.Contractor count decreased — from 3.9M to 2.5M, reflecting removal of duplicates and low-quality records.Some jurisdictions have reduced coverage — DC dropped entirely. VT, RI, MA, CT, DE, WI, and NM lost >80% of permits.Field coverage changes — geocoding: 72% → 67%, inspection data: 15% → 3%, address ID: 78% → 74% (improving in upcoming releases).first_seen_date has been reset — all values now fall between 2025-05-19 and 2026-03-28.Employee and resident records reduced — Employees: 38.1M → 12.8M. Residents: 45.9M → 27.6M.
Big month. We’re launching Shovels CLI — a new way to query permits, contractors, and addresses from the command line (or let your AI agent do it). On the data side, we added 1.8M new permits and geocoded another 1.4M records. Let’s get into it.
>_ Introducing Shovels CLIYour AI agent’s gateway to U.S. construction dataOne binary. Zero config. Pure JSON.Search permits, query contractors, resolve addresses — all from your terminalInstall in seconds
curl -LsSf https://shovels.ai/install.sh | sh
Built for automation
JSON-only output to stdout, errors to stderr
Auto-pagination with --limit all
Auto-retry with backoff on rate limits
Help text optimized for LLM comprehension
Works on macOS, Linux, and Windows. Learn more at shovels.ai/cli
Big month. We’re launching Shovels CLI — a new way to query permits, contractors, and addresses from the command line (or let your AI agent do it). The API gained result counts on every paginated endpoint, an improved usage dashboard, and more accurate contractor metrics. On the data side, we added 1.8M new permits and geocoded another 1.4M records.
>_ Introducing Shovels CLIYour AI agent’s gateway to U.S. construction dataOne binary. Zero config. Pure JSON.Search permits, query contractors, resolve addresses — all from your terminalInstall in seconds
curl -LsSf https://shovels.ai/install.sh | sh
Built for automation
JSON-only output to stdout, errors to stderr
Auto-pagination with --limit all
Auto-retry with backoff on rate limits
Help text optimized for LLM comprehension
Works on macOS, Linux, and Windows. Learn more at shovels.ai/cli
Returns {value, relation} shape — exact count or “10,000+” for large sets
Supported on:
/v2/permits/search
/v2/contractors/search
/v2/contractors/{id}/permits
All 4geo_permits endpoints
Enhanced Usage DashboardGET /v2/usage now includes:
Daily breakdown
is_over_limit flag
available_at projection so you always know your credit status
Over-limit users can still access usage data
Improved Contractor Metrics AccuracyFixed permit_count and total_job_value inflation for tag=all queries. Average metrics now use permit-count-weighted calculations for mathematical precision.
5M IDs UpdatedIDs were updated to correct issues arising from data collected across multiple platforms, as well as changes in administrative jurisdictions.
Most affected areas: Oregon, Douglas County, Omaha
For any missing IDs, you can still match using permit number or address fields. Or reach out for assistance.
What is Charlie?Charlie is your AI research agent for building permits and contractors. Ask questions in plain English—no SQL, no filters—and get answers instantly.January 2026 Updates:
Automatic error recovery – Charlie now automatically reconnects when the backend restarts. No more persistent errors requiring page refreshes.
Clickable profile links – When Charlie returns contractor or permit results, you now get direct links to their profile pages.
Improved county queries – Fixed an issue where county-based queries were failing due to formatting mismatches.
5M IDs UpdatedIDs were updated to correct issues arising from data collected across multiple platforms, as well as changes in administrative jurisdictions.
Most affected areas: Oregon, Douglas County, Omaha
For any missing IDs, you can still match using permit number or address fields. Or reach out for assistance.
✅ No breaking changes. All existing integrations continue to work unchanged.
5M IDs UpdatedIDs were updated to correct issues arising from data collected across multiple platforms, as well as changes in administrative jurisdictions.
Most affected areas: Oregon, Douglas County, Omaha
For any missing IDs, you can still match using permit number or address fields. Or reach out for assistance.
Happy New Year! We’re starting 2026 with 5.5M new permits, 4.7M additional geocoded records, and 171K new contractors. On the API side, we’ve added negative query filters and dynamic tallies, plus performance improvements for contractor and text search. Here’s everything new this month.
Happy New Year! We’re starting 2026 with 5.5M new permits, 4.7M additional geocoded records, and 171K new contractors. On the API side, we’ve added negative query filters and dynamic tallies, plus performance improvements for contractor and text search. Here’s everything new this month.
Negative Query FiltersExclude specific tags and classifications using a dash prefix:
# Exclude HVAC permitspermit_tags=-hvac# Mixed: solar permits excluding roofingpermit_tags=solar&permit_tags=-roofing
Note: Pure negative queries at state-level are limited to 365 days. Add a positive filter or use a more specific geo_id to expand the range.
Dynamic Tallies in Contractor SearchUse include_tallies=true to get tag_tally and status_tally per contractor. Tallies are scoped to your search filters (date range, geo, tags).Clarified Contractor Search SemanticsFilters work independently: permit_tags for capability/expertise, permit_from/to for activity period, and tag_tally for work breakdown within that period.
Happy New Year! We’re starting 2026 with 5.5M new permits, 4.7M additional geocoded records, and 171K new contractors. On the API side, we’ve added negative query filters and dynamic tallies, plus performance improvements for contractor and text search. Here’s everything new this month.
This month brings substantial improvements across data quality, coverage, and enrichment. We’ve significantly expanded our permits dataset with better field coverage, added 160 new jurisdictions, and continued strengthening our contractor intelligence with enhanced parsing and enrichment.
This month brings substantial improvements across data quality, coverage, and enrichment. We’ve significantly expanded our permits dataset with better field coverage, added 160 new jurisdictions, and continued strengthening our contractor intelligence with enhanced parsing and enrichment.
This month brings substantial improvements across data quality, coverage, and enrichment. We’ve significantly expanded our permits dataset with better field coverage, added 160 new jurisdictions, and continued strengthening our contractor intelligence with enhanced parsing and enrichment.
This month’s release brings significant intelligence improvements across our platform. We’ve enhanced our data classification capabilities, expanded geographic coverage, and continued growing both our permits and contractor datasets with better enrichment quality.
🧠 Data Intelligence BreakthroughProperty Type Classification Enhanced
20M+ Permits Reclassified
4M additional addresses now correctly labeled as commercial or residential
Our enhanced data pipeline now analyzes permit descriptions—the most reliable source of regulatory context—to automatically infer property types. This means more accurate market segmentation and better targeting capabilities for your use cases.
This month’s release brings significant intelligence improvements across our platform. We’ve enhanced our data classification capabilities, expanded geographic coverage, and continued growing both our permits and contractor datasets with better enrichment quality.
🔌 API ImprovementsNew Contractor Classification Parameter
contractor_classification_derived - Human-readable categories with nationwide coverage
We’ve introduced a new query parameter that replaces state-specific license codes with standardized, human-readable categories like “electrical”, “hvac”, and “plumbing”. This works consistently across all states, making it easier to filter and discover contractors without domain expertise.
Legacy contractor_classifications parameter status:DeprecatedThe old parameter continues to work for backward compatibility, but we recommend migrating to the new standardized taxonomy for better user experience and broader coverage.
This month’s release brings significant intelligence improvements across our platform. We’ve enhanced our data classification capabilities, expanded geographic coverage, and continued growing both our permits and contractor datasets with better enrichment quality.
🧠 Data Intelligence BreakthroughProperty Type Classification Enhanced
20M+ Permits Reclassified
4M additional addresses now correctly labeled as commercial or residential
Our enhanced data pipeline now analyzes permit descriptions—the most reliable source of regulatory context—to automatically infer property types. This means more accurate market segmentation and better targeting capabilities for your use cases.
This month marks a pivotal moment in our mission: we’ve begun bridging the gap between online and offline permit data. For the first time, we’re bringing dark data into the light, accessing jurisdictions that have never made their records digitally available. Combined with significant growth across our platform, October’s release represents our most comprehensive coverage to date.
Bridging the Digital Divide: Offline Jurisdictions Brought Online
500K+ Records
First-ever offline permit acquisition from Cook County, IL and Oak Ridge North, TX
Many jurisdictions still operate without public-facing digital portals. We’re now bringing this offline data online, giving you comprehensive coverage without the manual work. This is just the beginning of connecting America’s fragmented permit landscape into one unified, accessible platform.
This month marks a pivotal moment in our mission: we’ve begun bridging the gap between online and offline permit data. For the first time, we’re bringing dark data into the light, accessing jurisdictions that have never made their records digitally available. Combined with significant growth across our platform, October’s release represents our most comprehensive coverage to date.
Bridging the Digital Divide: Offline Jurisdictions Brought Online
500K+ Records
First-ever offline permit acquisition from Cook County, IL and Oak Ridge North, TX
Many jurisdictions still operate without public-facing digital portals. We’re now bringing this offline data online, giving you comprehensive coverage without the manual work. This is just the beginning of connecting America’s fragmented permit landscape into one unified, accessible platform.
This month marks a pivotal moment in our mission: we’ve begun bridging the gap between online and offline permit data. For the first time, we’re bringing dark data into the light, accessing jurisdictions that have never made their records digitally available. Combined with significant growth across our platform, October’s release represents our most comprehensive coverage to date.
Bridging the Digital Divide: Offline Jurisdictions Brought Online
500K+ Records
First-ever offline permit acquisition from Cook County, IL and Oak Ridge North, TX
Many jurisdictions still operate without public-facing digital portals. We’re now bringing this offline data online, giving you comprehensive coverage without the manual work. This is just the beginning of connecting America’s fragmented permit landscape into one unified, accessible platform.
Continued improving contractor classification standardization. As a result, more contractors now have a Shovels-standard classification assigned to the license_class field.
Continued improving contractor classification standardization. As a result, more contractors now have a Shovels-standard classification assigned to the license_class field.
Token-based pagination is fully live. Page-based pagination will be removed on August 1, 2025. Update any calls that still rely on the deprecated page parameter.
Continued improving contractor classification standardization. As a result, more contractors now have a Shovels-standard classification assigned to the license_class field.
Token-based pagination has been operational for the past two months. Since page-based pagination will be discontinued at the start of August, this is your final month to update your integrations.
Added cursor-based pagination for all endpoints, which substantially improves deep search pagination.
This replaces the former page parameter for pagination. This old method will be supported for an additional three months, at which point it will be deprecated.
Approximately 2 million duplicate permits from legacy system migrations were removed. The most affected states are Florida and Texas.
~6% of permits now have new IDs. Attributes such as permit_number and address remain unchanged.
If you query by cached id and encounter missing results (404), use permit_number, address, or other metadata to re-fetch the permit. If you still encounter issues, reach out—we’ll help map old IDs to new ones.
~170,000 contractors have new IDs that have been regenerated based on improved data quality.
All contractors remain searchable by:
Areas of work
Permit projects
Business names
If you cache contractor IDs on your end and you encounter not-found responses, use other record attributes to update IDs on your end. If ID changes affect your workflow in a more substantial way, contact us directly and we’ll assist.
Added cursor-based pagination for all endpoints, which substantially improves deep search pagination.
This replaces the former page parameter for pagination. This old method will be supported for an additional three months, at which point it will be deprecated.
All contractors with a license now have the classification_derived field as well. This field maps state-specific classifications into standardized categories.
If a contractor has multiple license classifications, they are concatenated using the pipe (”|”) character.
A new table, CSL, is added to our production database. It contains data from 26 states files, and has a total of 1.8 M contractors.
Around 200K contractors are linked to our Contractors table while the others are new. As part of this new dataset, we have around 700K new contractors phone numbers and 200K new emails.
There were in total almost 3000 different classifications categories across different state files. We standardized this to the following categories:
concrete_and_paving, demolition_and_excavation, electrical, fencing_and_glazing, framing_and_carpentry, general_building_contractor, general_engineering_contractor, hvac, landscaping_and_outdoor_work, plumbing, roofing, specialty_trades
this represents the date when the the permit itself was first retrieved for the Shovels platform
This is different than the first_seen_date column in the contractors table, which by contrast represents the date the contractor was first seen in our platform and assigned an id.
Fixed issue where Geography Profiles (City, Jurisdiction, County, etc) filters for Property Type and Permit Category weren’t updating counts correctly.
Fixed issue where address object’s latitude and longitude coordinates were occasionally reversed, and built in anomaly detection and correction for future processing.
This fix continues downstream to API and Online records.
Breaking Changes Policies
In order to ensure smooth transitions between updates, we’ve settled on a few short term policies.
We will do our best to give as much advance warning on breaking changes as possible.
Some recent breaking changes are delayed updates to the schema that should have been part of the V2 launch. We do not plan on making breaking changes this often.
Where sensible and possible, we will provide backward compatibility for new endpoints, parameters, and schemas.
Address Coordinate Errors
As described under EDL changes above, we found that there were rare cases where the latitude and longitude coordinates were reversed. Affected records have been corrected.We’ve also beefed up our address-geospatial processing to find and fix these errors going forward.
Casing standardizations (in addition to the changes outlined in the API Section previously).
property_owner_type values are now snake_case, eg individual or company_owned.
owner_name, owner_street, owner_city values are now upper case, eg JANE DOE, MAIN ST, or AGAWAM.
applicant_name, applicant_street, applicant_city values are now upper case, just like owner_$ above.
(PLANNED) Replacement of permits_ids with address_id in the residents table (please update your pipelines that use this foreign key value.)
This change will go into effect January 2025.
Schema Updates
We made a number of additions to our datasets, including new columns. For breaking changes to casing, see “API” above.
New columns in the 'residents' table:
personal_emails_validation_status (string): The validation status of the associated personal email. ‘Valid’ indicates a validated email; null means unknown.
personal_emails_last_seen (date): The date of the last validation or verification attempt for the personal email. Null if unknown.
business_email (string): The primary business email observed for this person.
business_email_validation_status (string): Validation status of the business email. ‘Valid’ means the email was validated; null means unknown. May contain values like ‘Valid-ESP’ (validated by email service provider) or ‘Valid-Digital’ (validated by cookie/digital tag).
business_email_last_seen (date): The date of the last known validation or verification attempt of the business email. Null if unknown.
linkedin_url (string): URL of the person’s LinkedIn profile.
homeowner (string): Reports if the person in this record is a homeowner. Y and N are observed values, P represents that they are likely a homeowner, based on probabilistic modeling, and null values represent ‘unknown’.
gender (string): The person’s gender.
age_range (string): The person’s age mapped to standard demographic ranges.
is_married (boolean): Indicates if the person is married.
has_children (boolean): Indicates if the person has children.
income_range (string): The person’s income range.
net_worth (string): The person’s net worth, mapped to standard demographic ranges. Null if unknown.
job_title (string): The person’s job title.
seniority_level (string): The seniority level of the person’s role.
department (string): The department in which the person works.
job_title_last_updated (date): The last date the person’s job title was updated.
last_updated (date): The last date any value in this record was updated.
work_history (string, JSON): A JSON-formatted history of the person’s work experiences (e.g., company name, * position, duration, start/end time, job description, location, social_url).
education_history (string): The person’s education background.
social_connections (string): The number of social media connections the person has, provided in ranges (e.g., 1-9, 10-49, etc.).
company_name (string): The name of the company where the person works.
company_domain (string): The company’s domain.
company_phone (string): The company’s contact phone number.
company_sic (string): The Standard Industrial Classification (SIC) code(s) of the company, separated by semicolons if multiple.
company_street_no (string): The street number of the company’s address.
company_street (string): The street name of the company’s address.
company_city (string): The city in which the company is located.
company_zip (string): The company’s 5-digit ZIP code.
company_state (string): The uppercase state abbreviation for the company’s address.
company_linkedin_url (string): The URL of the company’s LinkedIn profile.
company_revenue (string): The company’s revenue, expressed in standard ranges.
company_employee_count (string): The number of observed US enterprise employees at the company, provided in * standard firmographic ranges.
company_primary_industry (string): The primary industry in which the company operates.
company_description (string): A description of the company’s business activities.
company_naics (string): The company’s North American Industry Classification System (NAICS) code(s).
New 'employees' table (connected to 'contractors'):
contractor_id (string)
person_id (string)
name (string)
street_no (string)
street (string)
city (string)
zipcode (string)
zipcode_ext (string)
state (string)
phone (string)
email (string)
email_validation_status (string)
email_last_seen (date)
business_email (string)
business_email_validation_status (string)
business_email_last_seen (date)
linkedin_url (string)
homeowner (string)
gender (string)
age_range (string)
is_married (boolean)
has_children (boolean)
income_range (string)
net_worth (string)
job_title (string)
seniority_level (string)
department (string)
job_title_last_updated (date)
work_history (string, JSON formatted)
education_history (string)
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
