Handy publishes a Partner Orders API (HTTPS/JSON) that lets retailers attach in-home services to product orders, with webhooks across the booking lifecycle. The program is partner-onboarded rather than self-serve; documented users are large retailers such as Walmart, Wayfair, and eBay.
Handy scores B on the API Report Card. Handy publishes a Partner Orders API (HTTPS/JSON) that lets retailers attach in-home services to product orders, with webhooks across the booking lifecycle. The program is partner-onboarded rather than self-serve; documented users are large retailers such as Walmart, Wayfair, and eBay.
Handy has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Handy is a US home-services marketplace that connects consumers and businesses with vetted independent professionals for cleaning, handyman work, furniture assembly, TV mounting, light installation, painting, and other home tasks at pre-set, fixed prices.
Handy is bimodal. Consumer flow: a customer picks a service (e.g., '2 hours of handyman' or 'standard home cleaning'), selects a date and time window, enters address and access details, and pays a fixed quoted price; Handy assigns a pro from its pool, sends arrival notifications, and handles post-job payment and reviews.
Moderate as a consumer brand, narrow as a developer integration surface. Handy reports roughly 80,000 to 250,000 vetted pros across the broader Angi network, hundreds of thousands of app downloads, and a presence in most US metros.
Founded 2012 (as Handybook), rebranded 2014, HQ in New York City. Acquired by ANGI Homeservices (now Angi Inc., NASDAQ: ANGI; ~84-87% owned by IAC) on October 19, 2018 in an all-stock deal valuing Handy in the roughly $165M range per press coverage.
Founded in 2012 as Handybook, rebranded to Handy in 2014. Raised roughly $110M in venture funding from General Catalyst, Highland, Revolution, TPG, and others before being acquired by ANGI Homeservices in October 2018 in an all-stock deal.
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.