> This page is for version Latest Version (default).
> For other versions, use one of these documentation indexes:
> - Latest Version (default): https://paylocity-develop.ferndocs.com/payroll/latest-version/llms.txt
> - v2026-02-17: https://paylocity-develop.ferndocs.com/payroll/v-2026-02-17/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://paylocity-develop.ferndocs.com/payroll/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://paylocity-develop.ferndocs.com/payroll/_mcp/server.

## Guide content enhancements

* [StackOne](https://www.stackone.com/demo) has been added to the list of [Integration Platforms](https://developer.paylocity.com/integrations/docs/integration-platforms). They enable you to connect with Paylocity (and hundreds of other platforms) for rich, real-time, bi-directional AI agentic integrations.
* [Employee Transfers](https://developer.paylocity.com/integrations/docs/employee-transfers) has been added to the list of [Paylocity Key Concepts](https://developer.paylocity.com/integrations/docs/paylocity-key-concepts). The page explains the concept of employee transfers in Payroll & HR, and how to properly handle them in your integration.

## API reference enhancements

LMS API has had several documentation improvements for clarity and consistency. These changes have no impact to their URI or functionality. This is strictly a documentation update.

* Renamed get endpoint to [Create Training Content \[Single\]](https://developer.paylocity.com/integrations/reference/post_apihub-learningmanagementsystem-v1-companies-companyid-content).

Punch Details API has had several documentation improvements for clarity and consistency. These changes have no impact to their URI or functionality. This is strictly a documentation update.

* [Punch Import Overview](https://developer.paylocity.com/integrations/reference/punch-import-overview) documentation has been updated for improved clarity based on user feedback.

Scheduling API has had several documentation improvements for clarity and consistency. These changes have no impact to their URI or functionality. This is strictly a documentation update.

* Endpoints have been renamed to align with the standard naming schema.
* Corrected formatting issues with body parameter definitions.