Delete Earning by Earning Code and Start Date in Paylocity

What this operation does

Delete Earning by Earning Code and Start Date

• DELETEChanges data · Earningsapi.paylocity.com/v2/companies/{companyId}/employees/{employeeId}/earnings/{earningCode}/{startDate}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Paylocity operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Paylocity operations

• Add new employeePOST · changes data
• Obtain new client secretPOST · changes data
• Add new employee to Web LinkPOST · changes data
• Add new local taxPOST · changes data
• Add/update emergency contactsPUT · changes data
• Add/Update EarningPUT · changes data
• Add/update employee's benefit setupPUT · changes data
• Add/update sensitive dataPUT · changes data

All 30 Paylocity operations

Questions

Can HumDay delete earning by earning code and start date in Paylocity?

Yes. This operation is published in Paylocity's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Paylocity data?

Yes — this is a DELETE operation, so it changes something in Paylocity. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Paylocity account.

Where this came from

Read from a published API description for Paylocity at api.paylocity.com/api/v2/openapi. The description above is the provider’s own wording, not ours. Last published 2023-03-06.