Overview
Pre-built tooling
✅ Authorization
✅ Authorization
✅ Read & write data
✅ Read & write data
| Tools | Status |
|---|---|
| Pre-built integrations | ✅ |
| 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 | ✅ |
Users
Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| Paylocity API Access | ✅ | You must be an existing Paylocity customer or have a customer sponsor. |
| Paylocity Sandbox Access | ✅ | Required for testing API calls. |
| Approval from Paylocity | ✅ | Required before going live. |
Setup guide
No setup guide yet.Contribute improvements to the setup guide by editing this page
Useful links
Contribute useful links by editing this page
API gotchas
- Paylocity uses OAuth 2.0 Client Credentials Flow (
client_id&client_secret). - Access tokens are short-lived and expire every 1 hour.
- Tokens must be refreshed before expiry to avoid
401 Unauthorizederrors. - Secret Rotation: Paylocity requires API secrets to be rotated every 365 days.
- Paylocity APIs do not require OAuth scopes—they are managed internally.
Contribute API gotchas by editing this page
Going further
Connect to Paylocity
Guide to connect to Paylocity using Nango Connect.