# API Access Request Review for Payroll Reporting Integration

**March 04, 2026 at 08:59 AM** · 18m 56s

### Bottom Line
Speaker A (JD) and Speaker B (Kara) reviewed an API access request for integrating Paylocity payroll data into an internal reporting tool. The goal is to automate payroll cost accruals and gain real-time insights into project-based labor costs, moving away from manual Excel processes.

### Key Takeaways
- **API Access Purpose:** The API will be used to pull payroll and time data for internal reporting, specifically to automate month-end accruals and analyze project-based overtime.
- **Endpoint Selection:** Kara recommended adjusting the requested endpoints, suggesting removal of POST/PATCH functions (like Pantry API) not needed for read-only reporting and evaluating batch vs. single-pull options.
- **Two Credential Sets:** The integration will likely require two sets of API credentials—one for the legacy "Web Link" API and one for the newer "Next Gen" API—due to differing endpoint capabilities.
- **Ongoing Support:** Kara will remain the point of contact during setup, and ongoing support will be available through a web services team after the project closes.

### Decisions Made
- Remove Pantry API and Punch Import endpoints — *decided by Kara (Speaker B) with JD's (Speaker A) agreement*
- Proceed with initial endpoint selection as adjusted by Kara — *decided by JD (Speaker A)*

### Action Items
- [ ] Send JD the existing API request form and an updated version reflecting the discussed endpoint changes (removing Pantry/Punch Import, suggesting batch options). — @Speaker B `high`
- [ ] Review the updated API request form and provide approval or requested changes to Kara. — @Speaker A `high`
- [ ] Provision the approved API access credentials for production (since sandbox is not required). — @Speaker B `high`
- [ ] Test the provided API credentials and explore the developer portal links to begin integration development. — @Speaker A `medium`
- [ ] Schedule a follow-up if endpoint adjustments are needed after initial testing of the API data. — @Speaker A `low`

### Topics
API Access Request, Endpoint Selection, Production vs Sandbox, Legacy vs Next Gen API, Payroll Reporting Use Case, Ongoing Support Process

**Sentiment:** positive

---
*Generated by Call Assistant on 2026-04-09 10:06*