Paylocity: API authentication
Sandbox and production are separate credentials against separate Paylocity systems. Use the client ID/secret from your sandbox access grant while testing, and the production pair once you’re ready to go live — pasting the wrong one simply fails to connect, it does not cross over.
Connect it
1
Request access
Settings → Connectors → Paylocity → Request access. That asks Rivvi to set the connection up with you. Paylocity still has to grant NextGen API access for your company first.
2
If you already have credentials
Use Already have Paylocity API credentials? Connect. Paste the client ID, client secret, and company ID from the password-protected file Paylocity sent. Sandbox and production are separate credentials. The wrong pair fails to connect. It does not read the other system.
Employee directory reads can include names, work email/phone, and position — no SSN or pay rate. Reads are Always allow by default; an admin can tighten this — see Permissions.
What Rivvi can do with Paylocity
Read (allowed by default)- Find an employee by name, email, title, or location — this searches your whole directory, not just the first page, so it works regardless of how many employees you have.
- List or look up employee directory records — name, work email/phone, position, status, hire date.
- List cost center / labor level codes and names.
- SSN, pay rate, or any other Sensitive Data fields.
- Payroll, onboarding, time punches, or any write to Paylocity.
Paylocity returns employees in pages of 20 at a time — a plain “list employees” only shows the first page. Ask Rivvi to find someone by name instead of listing and scrolling; that search checks your whole directory.