Skip to main content

​
Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

​
Pre-built tooling

ToolsStatus
Pre-built authorization (Two Step)✅
Pre-built authorization UI✅
Custom authorization UI✅
End-user authorization guide✅
Expired credentials detection✅
ToolsStatus
Pre-built integrations🚫 (time to contribute: <48h)
API unification✅
2-way sync✅
Webhooks from Nango on data modifications✅
Real-time webhooks from 3rd-party API🚫 (time to contribute: <48h)
Proxy requests✅
ToolsStatus
HTTP request logging✅
End-to-type type safety✅
Data runtime validation✅
OpenTelemetry export✅
Slack alerts on errors✅
Integration status API✅
ToolsStatus
Create or customize use-cases✅
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling🚫 (time to contribute: <48h)
Per-customer configurations✅

​
Pre-built integrations

No pre-built integration yet (time to contribute: <48h)
Not seeing the integration you need? Build your own independently.

​
Access requirements

Pre-RequisitesStatusComment
Paid dev account❓
Paid test account❓
Partnership❓
App review❓
Security audit❓

​
Setup guide

No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Contribute useful links by editing this page

​
API gotchas

  • HTTP Redirects: Dayforce issues an HTTP redirect for every request to route it to the appropriate service. For high-volume integrations, you can avoid repeated redirects by making a REST request to /{companyId}/V1/ClientMetadata. Use the companyId from your connection configuration to retrieve the ServiceUri, and make subsequent API calls directly to that URI.
Contribute API gotchas by editing this page

Connect to Dayforce

Guide to connect to Dayforce using Nango Connect.