Your payroll and HR data is already in APS OnLine. The APS Developer API lets your own software reach it directly, on your schedule, so the information you need shows up in your accounting system, your reporting tools, or your employee portal without anyone exporting a file first.
There’s also Alli Direct. The AI assistant already built into APS OnLine can connect to the AI assistant your team uses elsewhere, so a payroll or system administrator can ask about your company’s data in plain language instead of building against an API. It only reads. It can’t create, change, or delete anything in APS. Ask your APS contact to turn it on for your administrators.
What it changes for your team
- The manual export goes away. Data moves between systems automatically instead of someone running a report, saving a file, and passing it along.
- Your systems stay current. New hires, transfers, terminations, hours worked, and pay results reach your other systems without a lag or a rekeying step.
- Your team self-serves its own reporting. Your analysts slice payroll and workforce data in the tools they already use, at whatever cut they need, whenever they need it.
- Your close gets faster. Payroll journal entries arrive in your accounting system already grouped and dated the way your finance team wants them.
What you can pull, and what it enables
| What you can pull | What it enables |
| Company and department lists | Keeps your org structure aligned between APS and your own systems, so reporting rolls up the same way in both places. |
| Employee records | Feeds your HR system, directory, or access-provisioning tool automatically. Includes employment status, key dates, title, department, location, pay rates, and scheduled earnings. |
| Hours worked, including breaks and additional earnings | Labor cost and overtime analysis in your own reporting tools, across any date range, without waiting on a report. |
| Pay statements and pay history | Mirrors pay detail into your portal or compensation analysis, including incomes, taxes, deductions, accruals, and direct deposit detail. |
| Payroll batches and pay groups | Shows what has already run and what is scheduled, including completed and projected pay periods. |
| General ledger journal entries | Posts payroll into your accounting system automatically, grouped by department or memo and dated to your check date or pay period end. |
| Time off requests | Absence and coverage dashboards for your managers, filtered by date range and status. |
| Employee data upload (EIP) | Sends employee demographic files into APS from another system. |
| Service status check | Confirms the connection is healthy, so your team can monitor the integration. |
Also available: the APS Enterprise Integration Platform (EIP). EIP is a separate APS offering for sending employee data into APS from your own system. Your system posts XML files on whatever schedule you choose, covering both new hires and updates to existing records. Nothing reaches production until it passes validation and your team approves it. Ask your account manager about EIP alongside the API, or see Enterprise Integration Platform for details.
What to know before you build
Access is all-or-nothing. Any token that can read a record can read every field on it, including sensitive employee fields such as bank account detail. There is no setting that hides individual fields or restricts a token to part of the data, so plan your own handling and storage controls accordingly.
- It is a read service today. Employee demographic upload is the one path that sends data into APS. Other create and update capabilities are on the roadmap and are not available yet.
- One company per request. If you run multiple companies in APS, your integration pulls them one at a time rather than combining them in a single call.
- It is built for a technical resource. You will need a technical resource on your team or through your software vendor to consume it. Full endpoint documentation lives on the API Reference page.
Getting started
| Step | What happens |
| 1. Request access | Submit the access request form on the Request Access page. |
| 2. Receive credentials | APS provisions your token against the APS Demo company and delivers credentials securely to a contact your account administrator approves. |
| 3. Prove it out at no cost | Your technical resource validates against the demo company that the available data covers what you are building, before any commitment. |
| 4. Go live | Once your agreement is in place and you acknowledge the access model above, your live company codes are added to your token. |
Our APIs and integrations are designed to serve specific types of users:
APS Customers
Direct customers of APS who have their own software engineering resources to successfully implement integrations may leverage the APS APIs and integrations for their own usage, in the form of private applications used within their organization.
Vendors
Vendors who resell APS’s services, and partners with an established relationship with APS, may implement integrations between their other applications and APS, to increase the breadth of their own solutions offerings to their end customers.
Ready to start? Talk with your APS account manager, or visit Request Access to submit your token request, or review the full API Reference.