No public API. The only programmatic surface is a one-way outbound XML webhook that posts matched leads from the CraftJack pipeline to a contractor-supplied URL. There is no way to pull lead history, billing, or dispute data.
ImproveNet scores F on the API Report Card. No public API. The only programmatic surface is a one-way outbound XML webhook that posts matched leads from the CraftJack pipeline to a contractor-supplied URL. There is no way to pull lead history, billing, or dispute data.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
ImproveNet is a consumer-facing home-improvement marketplace that matches U.S. homeowners with local pre-screened contractors across roofing, siding, windows, HVAC, kitchen/bath remodels, flooring, plumbing, electrical, painting, landscaping, and similar trades.
Construction / home services lead generation. A homeowner answers a series of questions about their project (type of work, ZIP code, timeline, budget, contact info) and is matched with up to ~4 vetted contractors who then call/email them.
Low-to-medium and declining.
For homeowners: project intake details (project type, scope, timeline, budget hints), ZIP and contact info, and the resulting contractor match set.
Mature and dated. Founded 1996, acquired by HomeAdvisor in 2005, now operated by CraftJack.
No public REST/GraphQL API or developer portal for ImproveNet/CraftJack, integration is limited to a one-way outbound XML webhook and a small set of pre-built CRM connectors. XML-only default payload feels dated for modern CRM and automation stacks; teams must hand-roll a custom payload template per integration target. Full sourced list under Sources below.
Common alternatives include Angi (Angie's List), HomeAdvisor, Thumbtack, Houzz Pro, Porch, Networx. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.