Overview
Pre-built tooling
✅ Authorization
✅ Authorization
✅ Read & write data
✅ Read & write data
Tools | Status |
---|---|
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 | ✅ |
✅ Observability & data quality
✅ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ Customization
✅ Customization
Tools | Status |
---|---|
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-Requisites | Status | Comment |
---|---|---|
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
Useful links
- Authentication docs
- How to Add the Web Services Role Feature
- Token-Based Authentication
- How to Determine the best URL to use
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 thecompanyId
from your connection configuration to retrieve theServiceUri
, 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.