{
 "categories": [
  "hcm",
  "hr",
  "payroll"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-11",
   "fact": "homepage",
   "note": "Dayforce presents a commercial AI-powered people platform for HR, payroll, workforce management, talent, planning, and analytics, claiming 7 million users and payroll in more than 200 countries.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "vendor",
   "note": "The site identifies the company and product as Dayforce, not Ceridian.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "name",
   "note": "The developer portal copyright line reads Dayforce and markets Dayforce web services APIs. Older Ceridian branding is not used on the opened pages.",
   "source": "https://developers.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "deployment",
   "note": "Dayforce is marketed as a single cloud people platform, not as customer-installed on-premises software.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "license",
   "note": "The homepage markets Dayforce as commercial enterprise HCM SaaS with analyst-report and ROI calls to action.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "platforms",
   "note": "The opened homepage presents a browser-delivered suite. A first-party native client was not established on that page.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "status",
   "note": "Dayforce publishes Web Services Introduction Guide version R2026.1.0, last edition 2026-05-01, visible to all.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.exists",
   "note": "The Dayforce Developer Network states Dayforce's web services API makes multiple resources available for applications and integrations, with an API explorer and documentation.",
   "source": "https://developers.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.kinds[0]",
   "note": "RESTful URLs use https://, a domain such as www.dayforcehcm.com, the API service, a client namespace, version V1, and a resource such as Employees, for example https://www.dayforcehcm.com/api/CompanyName/V1/Employees.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.kinds[1]",
   "note": "The opened Introduction Guide table of contents includes Dayforce Web Services Compared: SOAP and RESTful and a SOAP Web Services path alongside the REST chapters.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.auth[0]",
   "note": "The R2026.1.0 REST guide documents token-based authentication. POST grant_type=password, companyId, username, password, and client_id=Dayforce.HCMAnywhere.Client to https://dfid.dayforcehcm.com/connect/token. The response is a Bearer JWT with expires_in 3600. API calls send Authorization: Bearer and do not resend the password.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.auth[1]",
   "note": "The same REST developer guide states each request must include credentials that can be authenticated, that the user account must have the Web Services feature on its default role, and that Dayforce REST services use HTTP basic authentication for passing those credentials. Token auth is documented as the recommended alternative so the password is not sent on every call.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.coverage",
   "note": "The R2026.1.0 Introduction Guide lists REST retrieve and add/update chapters for employees, org units, departments, jobs, positions, HR admin, documents, availability, raw clock entries, WFM, labor metrics, projects, balances, pay, job-step rates, retro data, and reports. Access is still role-gated, so coverage is partial.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.api.docs",
   "note": "Opened as the current Dayforce RESTful Web Services Developer Guide authentication chapter used as this record's API docs URL.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.mcp.first_party",
   "note": "The opened Dayforce homepage does not declare a first-party MCP server. developers.dayforce.com likewise does not declare MCP. Registry silence is not used as proof of absence, so first_party stays unknown.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.data_access.export[0]",
   "note": "RESTful retrieve chapters return JSON for employees, org units, departments, jobs, positions, WFM, and related resources.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.data_access.import[0]",
   "note": "The same guide lists RESTful add and update chapters for employee HR data, org units, departments, jobs, and positions.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "modalities.rpa.ui_stack[0]",
   "note": "Dayforce is presented as a browser-delivered people platform, so the interactive UI stack in scope is web DOM.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "verdict.scores.api",
   "note": "Documented REST with OpenAPI, Bearer tokens from the Dayforce identity server, and HTTP basic as a fallback, plus a listed SOAP guide. Web Services role access, client namespaces, 60-minute tokens, and member-gated developer-network detail keep the path at 7.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current R2026.1.0 Dayforce RESTful Web Services Developer Guide token-authentication chapter (last edition 2026-05-01).",
   "source": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current R2026.1.0 Dayforce Web Services Introduction Guide REST URL and resource catalog.",
   "source": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Dayforce Developer Network home, including API Explorer and member documentation.",
   "source": "https://developers.dayforce.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-11",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current Dayforce product homepage.",
   "source": "https://www.dayforce.com/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-11",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw"
   },
   {
    "type": "docs",
    "url": "https://help.dayforce.com/r/documents/Dayforce-Web-Services-Introduction-Guide/The-RESTful-URL?contentId=wNmMpgMKxp2w8ixXq9iWMw"
   },
   {
    "type": "docs",
    "url": "https://developers.dayforce.com/"
   },
   {
    "type": "docs",
    "url": "https://www.dayforce.com/"
   }
  ]
 },
 "homepage": "https://www.dayforce.com/",
 "id": "dayforce",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "bearer-token",
    "http-basic"
   ],
   "coverage": "partial",
   "docs": "https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/Token-Based-Authentication?contentId=F42stqJi6IIdJEkO2J16iw",
   "exists": true,
   "kinds": [
    "rest",
    "soap"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": [
    "json"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Dayforce RESTful and SOAP Web Services are the documented machine paths. This record is Dayforce HCM, formerly marketed as Ceridian Dayforce. It is not Workday, SAP SuccessFactors, HiBob, or Personio.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Dayforce",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "workday",
   "sap-successfactors",
   "hibob",
   "personio"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Dayforce",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 7,
   "rpa": null
  },
  "summary": "Dayforce is automatable today through Dayforce Web Services, not through a first-party MCP server established on opened pages. The RESTful services use HTTPS JSON at https://www.dayforcehcm.com/api/{clientName}/v1 and publish an OpenAPI document at /api/{clientName}/swagger/docs/v1. The R2026.1.0 Introduction Guide, last edition 2026-05-01, documents retrieve and write resources for employees, org units, departments, jobs, positions, HR admin data, documents, availability, clock entries, WFM, labor metrics, projects, balances, pay, job-step rates, retro pay, and report metadata. Token-based authentication posts grant_type=password, companyId, username, password, and client_id=Dayforce.HCMAnywhere.Client to https://dfid.dayforcehcm.com/connect/token (test host dfidtst.np.dayforcehcm.com). The identity server returns a Bearer JWT that expires in 3,600 seconds. Subsequent calls send Authorization: Bearer and do not resend the password. The same REST guide still documents HTTP basic authentication with Web Services credentials on the user's default role. The Introduction Guide lists a parallel SOAP Web Services guide and comparison. The Dayforce Developer Network at developers.dayforce.com provides an API explorer; detailed configuration docs are gated to network members. Role feature access and client namespace are material gates. iPaaS catalogs were not opened. Computer-use viability is unassessed. API scores 7.\n"
 }
}