PlanHub API Overview

 1. Core Functionality & Available Data

The API provides curated, fresh construction opportunities posted by General Contractors and early stage projects discovered by PlanHub researchers. PlanHub offers three primary endpoints:

• Projects Endpoint

• • Provides: Details on active construction opportunities posted by general contractors open for bidding.
  • Key Data Included: Project names, start and end dates, bid due dates, estimated financial values, project stages, physical locations (address, city, state), and General Contractor company and primary contact details.
• SC Connect Endpoint:
  • Provides: High-intent subcontractor contact information based on actual user engagement with project files.
  • Key Data Included: Verified subcontractor company details, company locations, trades/sub-trades, and direct contact information for individuals who have downloaded project files (a strong signal of bidding intent).
• Lead Finder Endpoint
  • Provides: Data on projects that are likely to hit the market.
  • Key Data Included: Owner, architect, and developer information, location, key dates, stage, trades and subtrades, and scope of work when available.

2. Endpoint Details

To build effective sales and outreach workflows, it is important to understand how the three endpoints relate to one another:

• The Difference
  
  • The Projects Endpoint is your starting point for discovering construction jobs open for Subs and GC’s to bid, their location, project scopes, relevant dates, and trades required among other information.
  • The SC Connect Endpoint is specialized for downstream outreach, focusing exclusively on identifying which subcontractors are actively evaluating and downloading the plans for a specific project.
  • The Lead Finder Endpoint contains early stage projects. These records contain project level information such as name, location, associated companies, similar to the Projects Endpoint. The difference is they are early stage projects still in the planning stage.

• The Dependency:
• SC Connect relies directly on the Projects Endpoint. SC Connect requires a specific project identifier to retrieve subcontractor data, after you identify a project through the Projects endpoint (obtaining its unique project ID) then you query SC Connect for that project's active subcontractors.

• Are General Contractor contacts available? Yes. Every project record includes the General Contractor's company name and the primary contact (such as the project manager or estimator).
• Are Subcontractor contacts available? Yes, via the SC Connect endpoint, allowing you to target subcontractors actively engaging with project files.
• Are project documents (PDFs, blueprints, drawings) available through the API? No. The API provides structured metadata and business intelligence rather than heavy document files. However, every project record includes a direct web link (projectDetailsUrl) that takes your team straight to the full documents within the PlanHub platform. (An active subscription to Planhub Application is required to access these documents).
  
  

Data Access and usage limits are automatically enforced based on your organization's purchased tier (Explorer, Growth, or Professional):

• Daily Request Limits: Ranges from 10 to 15 requests per day depending on tier.
• Monthly Record Caps: Supports maximum monthly record limits ranging from 300 up to 4,500 records.
• Filters: Advanced filtering (such as by state, city, project value, and trade categories) helps ensure your systems ingest only high-relevance leads.
• Contact PlanHub to learn more about specific filters and limits that are available within each tier.

• API Key Delivery: Keys are issued securely via 1Password following license finalization to ensure enterprise-grade security.
• Production Environment: All keys operate live in production, eliminating the need for sandbox configuration and allowing immediate integration with your CRM or ERP systems.
• Technical References: All API customers receive access to PlanHub’s full API Readme document. This document contains example cURL commands, filter options for each endpoint, trade mapping, full lists of all metadata available within each endpoint

• Technical Resource Skills: Your team will need a technical resource capable of integrating API endpoints into your internal systems. This includes sending automated web requests via command line tools (like cURL) or setting up no-code/low-code workflow automation platforms such as n8n or Make to process and route data automatically.

Contact planHub to learn more about our API

• Contact an API Representative