HCM and Payroll Marketplaces (ADP, Workday, UKG, Paylocity)

Where this market publishes its structure

• ADP Marketplace (apps.adp.com, AppDirect listing JSON) machine-readable, 200; 725 listings; edges owned by sweep-hr-stores.py (hr-payroll), consumed; detail fetched for 250 only -- a full pass would link 31 more (27 in-market)
• Workday Marketplace (marketplace.workday.com) machine-readable, 301 -> /home, listing JSON 200; 896 listings; consumed from hr-stores; a full detail pass would link 64 more (36 in-market)
• UKG Marketplace (marketplace.ukg.com) machine-readable, 301 -> /home, listing JSON 200; 334 listings; consumed from hr-stores; full detail pass +2 (1 in-market)
• Paylocity Marketplace listing URLs (www.paylocity.com/sitemap.xml) machine-readable, 435 listing names; builder not stated (direction unknown); 96 linked after hand review
• Paylocity Marketplace listing pages not machine-readable: marketplace.paylocity.com does not resolve; www.paylocity.com listing pages answer a Cloudflare JavaScript challenge; not bypassed

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 85 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

What apps actually use from application blueprints

Apps in 12 application categories integrate providers in this market. 16 of the 85 cohort providers appear in an app. The providers below are used by apps but sit outside the cohort. They are listed beside it, not ranked in it.

Derived 2026-11-03: blueprint stack rows (declared/observed) whose capability id falls under this market; providers outside the cohort integrated by apps in >= 3 app categories, max 10.

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 4 · other companies invest to build on it

builds-on 54 · publishes apps on other platforms' stores

regulated 8 · named in a regulator's register or partners' contracts

standard 3 · listed by a voluntary standard's own directory

core 2 · builds the connectors its customers need

mixed 2 · no single mode dominates

long-tail 2 · reached only through iPaaS bridges

undeclared 10 · declares nothing we can read: no number

Top workflows by market votes

Workflows (Arazzo) and their phrasing are generated by API Evangelist, ranked by market votes (integration edges in the graph, weighted by channel).

In-market workflows only: a step on the market provider's side maps to this market's business capabilities (BC-300), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology. In-market: 2; bridges: 14 (8 not yet mapped to a capability).