handy website screenshot

handy

Handy is a home-services marketplace, now part of Angi (ANGI Homeservices), that connects customers with pre-screened independent professionals for house cleaning, handyman work, furniture assembly, and in-home installations. Handy's Partner API lets retailers offer fixed-price installation and service bookings at eCommerce or in-store checkout: partners create and manage orders, products, and line items, retrieve bookings and their assigned providers, and receive booking-lifecycle webhooks. Requests are authenticated with a custom RSA-SHA256 signed-request scheme.

handy publishes 4 APIs on the APIs.io network, including Bookings API, Order Products API, Orders API, and 1 more. Tagged areas include Company, Home Services, Marketplace, Cleaning, and Handyman.

The handy catalog on APIs.io includes 1 event-driven AsyncAPI specification.

handy’s developer surface includes documentation, API reference, support, authentication, sandbox, and 22 more developer resources.

39.4/100 developing ▬ flat Agent 35/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyHome ServicesMarketplaceCleaningHandymanInstallationsOn-DemandGig EconomyOrderWebhookRetailAngi

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/handy: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

handy Bookings API

The Bookings API from handy — 1 operation(s) for bookings.

handy Order Products API

The Order Products API from handy — 2 operation(s) for order products.

handy Orders API

The Orders API from handy — 2 operation(s) for orders.

handy Testing API

The Testing API from handy — 1 operation(s) for testing.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Handy Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Handy Authentication

signed-request · 1 scheme

SECURITY

Handy Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Handy Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Handy Agentic Access

10 operations · 6 acting

10 operations · 6 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: handy
name: handy
description: 'Handy is a home-services marketplace, now part of Angi (ANGI Homeservices), that connects customers with pre-screened
  independent professionals for house cleaning, handyman work, furniture assembly, and in-home installations. Handy''s Partner
  API lets retailers offer fixed-price installation and service bookings at eCommerce or in-store checkout: partners create
  and manage orders, products, and line items, retrieve bookings and their assigned providers, and receive booking-lifecycle
  webhooks. Requests are authenticated with a custom RSA-SHA256 signed-request scheme.'
url: https://raw.githubusercontent.com/api-evangelist/handy/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- slow-ventures
x-tier: active
x-tier-reason: partner-api-enriched
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.handy.com/favicon.ico
tags:
- Company
- Home Services
- Marketplace
- Cleaning
- Handyman
- Installations
- On-Demand
- Gig Economy
- Order
- Webhook
- Retail
- Angi
tags_raw:
- Company
- Home Services
- Marketplace
- Cleaning
- Handyman
- Installations
- On-Demand
- Gig Economy
- Orders
- Webhooks
- Retail
- Angi
apis:
- aid: handy:handy-bookings-api
  name: handy Bookings API
  description: The Bookings API from handy — 1 operation(s) for bookings.
  humanURL: https://partners.services.handy.com/docs/orders_api
  baseURL: https://partners.services.handy.com/api/v1
  tags:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/handy-bookings-api-openapi.yml
  - type: APIReference
    url: https://partners.services.handy.com/docs/orders_api
  - type: Documentation
    url: https://partners.services.handy.com/docs/orders_api
  - type: Webhooks
    url: asyncapi/handy-webhooks.yml
- aid: handy:handy-order-products-api
  name: handy Order Products API
  description: The Order Products API from handy — 2 operation(s) for order products.
  humanURL: https://partners.services.handy.com/docs/orders_api
  baseURL: https://partners.services.handy.com/api/v1
  tags:
  - Order Products
  properties:
  - type: OpenAPI
    url: openapi/handy-order-products-api-openapi.yml
  - type: APIReference
    url: https://partners.services.handy.com/docs/orders_api
  - type: Documentation
    url: https://partners.services.handy.com/docs/orders_api
  - type: Webhooks
    url: asyncapi/handy-webhooks.yml
- aid: handy:handy-orders-api
  name: handy Orders API
  description: The Orders API from handy — 2 operation(s) for orders.
  humanURL: https://partners.services.handy.com/docs/orders_api
  baseURL: https://partners.services.handy.com/api/v1
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/handy-orders-api-openapi.yml
  - type: APIReference
    url: https://partners.services.handy.com/docs/orders_api
  - type: Documentation
    url: https://partners.services.handy.com/docs/orders_api
  - type: Webhooks
    url: asyncapi/handy-webhooks.yml
- aid: handy:handy-testing-api
  name: handy Testing API
  description: The Testing API from handy — 1 operation(s) for testing.
  humanURL: https://partners.services.handy.com/docs/orders_api
  baseURL: https://partners.services.handy.com/api/v1
  tags:
  - Testing
  properties:
  - type: OpenAPI
    url: openapi/handy-testing-api-openapi.yml
  - type: APIReference
    url: https://partners.services.handy.com/docs/orders_api
  - type: Documentation
    url: https://partners.services.handy.com/docs/orders_api
  - type: Webhooks
    url: asyncapi/handy-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/handy-capability-edges.yml
  name: handy Business Capability Map
- type: AgenticAccess
  url: agentic-access/handy-agentic-access.yml
- type: DeveloperPortal
  url: https://partners.services.handy.com/docs/orders_api
- type: Documentation
  url: https://partners.services.handy.com/docs/orders_api
- type: APIReference
  url: https://partners.services.handy.com/docs/orders_api
- type: GitHubOrganization
  url: https://github.com/Handybook
- type: Support
  url: https://help.handy.com/
- type: TermsOfService
  url: https://www.handy.com/terms
- type: PrivacyPolicy
  url: https://www.handy.com/privacy
- type: Authentication
  url: authentication/handy-authentication.yml
- type: Conventions
  url: conventions/handy-conventions.yml
- type: ErrorCatalog
  url: errors/handy-problem-types.yml
- type: Lifecycle
  url: lifecycle/handy-lifecycle.yml
- type: DataModel
  url: data-model/handy-data-model.yml
- type: Conformance
  url: conformance/handy-conformance.yml
- type: Sandbox
  url: sandbox/handy-sandbox.yml
- type: Webhooks
  url: asyncapi/handy-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/handy-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/handy-llms.txt
- type: Overlay
  url: overlays/handy-orders-overlay.yaml
- type: WellKnown
  url: well-known/handy-well-known.yml
- type: SecurityTxt
  url: well-known/handy-security.txt
- type: Security
  url: https://www.handy.com/.well-known/security.txt
- type: VulnerabilityDisclosure
  url: security/handy-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/handy-domain-security.yml
- type: Website
  url: https://handy.com
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/handy"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/handy/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/handy/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.