Automate PayRun.IO

What PayRun.IO is

Open, scableable, transparent payroll API.

API host: api.test.payrun.io

What HumDay can do in PayRun.IO

145 documented operations change something in PayRun.IO. The 57 most useful are listed here.

• POSTPost user object/Users
• POSTCreate a new report definition/Reports
• POSTCreate a new Application secret/Secrets
• POSTCreate a new Employer/Employers
• POSTCreate a new transform definition/Transforms
• POSTCreates a new Journal Instruction template/JournalInstructions
• POSTCreate new CIS job/Jobs/Cis
• POSTCreate new DPS job/Jobs/Dps
• POSTCreate new RTI job/Jobs/Rti
• POSTCreate a new pay schedule/Employer/{EmployerId}/PaySchedules
• POSTCreate new Batch job/Jobs/Batch
• POSTCreate new PayRun job/Jobs/PayRuns
• POSTCreate new Third Party job/Jobs/ThirdParty
• PUTCreate a new Application secret/Secret/{SecretId}
• POSTGet the query result/Query
• POSTCreate a new employer secret/Employer/{EmployerId}/Secrets
• POSTCreate a new pay code/Employer/{EmployerId}/PayCodes
• POSTCreate a new Pension/Employer/{EmployerId}/Pensions
• POSTCreate a new Employee/Employer/{EmployerId}/Employees
• POSTCreate a new CIS line type/Employer/{EmployerId}/CisLineTypes
• POSTCreate a new holiday scheme/Employer/{EmployerId}/HolidaySchemes
• POSTCreate a new sub contractor/Employer/{EmployerId}/SubContractors
• POSTCreates a new Journal Instruction/Employer/{EmployerId}/JournalInstructions
• POSTCreates a new Reporting Instruction/Employer/{EmployerId}/ReportingInstructions
• DELETEDeletes the user object/User/{UserId}
• PATCHPatch user object/User/{UserId}
• PUTPuts user object/User/{UserId}
• PUTCreate a new employer secret/Employer/{EmployerId}/Secret/{SecretId}
• POSTPosta the DPS message/Employer/{EmployerId}/DpsMessages
• POSTCreate a new employee secret/Employer/{EmployerId}/Employee/{EmployeeId}/Secrets
• POSTCreates a new Pay Instruction/Employer/{EmployerId}/Employee/{EmployeeId}/PayInstructions
• DELETEDeletes Application secret/Secret/{SecretId}
• DELETEDelete user tag/User/{UserId}/Tag/{TagId}
• PUTInsert user tag/User/{UserId}/Tag/{TagId}
• DELETEDelete an Employer/Employer/{EmployerId}
• PATCHPatches the employer/Employer/{EmployerId}
• PUTUpdates the Employer/Employer/{EmployerId}
• POSTCreate a new CIS instruction/Employer/{EmployerId}/SubContractor/{SubContractorId}/CisInstructions
• DELETEDeletes a report definition/Report/{ReportDefinitionId}
• PUTUpdates a report definition/Report/{ReportDefinitionId}
• DELETEDeletes a transform definition/Transform/{TransformDefinitionId}
• PUTUpdates a transform definition/Transform/{TransformDefinitionId}
• DELETEDelete the CIS job/Jobs/Cis/{JobId}
• DELETEDelete the DPS job/Jobs/Dps/{JobId}
• DELETEDelete the RTI job/Jobs/Rti/{JobId}
• DELETEDelete the Batch job/Jobs/Batch/{JobId}
• DELETEDelete the pay run job/Jobs/PayRuns/{JobId}
• DELETEDeletes a Journal instruction template/JournalInstruction/{JournalInstructionId}
• PUTUpdate a Journal Instruction template/JournalInstruction/{JournalInstructionId}
• DELETEDeletes the DPS message/Employer/{EmployerId}/DpsMessage/{DpsMessageId}
• PATCHPatches the DPS message/Employer/{EmployerId}/DpsMessage/{DpsMessageId}
• PUTPuts the DPS message/Employer/{EmployerId}/DpsMessage/{DpsMessageId}
• DELETEDelete the Third Party job/Jobs/ThirdParty/{JobId}
• DELETEDeletes a pay schedule/Employer/{EmployerId}/PaySchedule/{PayScheduleId}
• PUTUpdates a pay schedule/Employer/{EmployerId}/PaySchedule/{PayScheduleId}
• PUTCreate a new employee secret/Employer/{EmployerId}/Employee/{EmployeeId}/Secret/{SecretId}
• POSTInsert nominal code/Employer/{EmployerId}/NominalCodes

What HumDay can read from PayRun.IO

These are the operations a schedule or a trigger can watch.

• GETGets all user objects/Users
• GETGet all user tags/Users/Tags
• GETGet a list of all available schemas/Schemas
• GETGet a list of all available data object tempaltes/Templates
• GETGets the user object/User/{UserId}
• GETRuns the DPS message report/Report/DPSMSG/run
• GETGets all reports/Reports
• GETGet all Application secret links/Secrets
• GETGets all employers/Employers
• GETGets all transform definitions/Transforms
• GETGet health check status/Healthcheck
• GETGet links to tagged users/Users/Tag/{TagId}
• GETGet tags from user/User/{UserId}/Tags
• GETGets the Journal instructions templates for the application/JournalInstructions
• GETGets the DPS messages/Employer/{EmployerId}/DpsMessages
• GETGet all CIS jobs/Jobs/Cis
• GETGet all DPS jobs/Jobs/Dps
• GETGet all RTI jobs/Jobs/Rti
• GETGets the pay schedule from the specified employer/Employer/{EmployerId}/PaySchedules
• GETGet all Batch jobs/Jobs/Batch
• GETGet all PayRun jobs/Jobs/PayRuns
• GETGet all employer tags/Employers/Tags
• GETGet all Third Party jobs/Jobs/ThirdParty
• GETGet employer summaries./Employers/Summary
• GETGet Application secret/Secret/{SecretId}
• GETGet all pay schedule tags/Employer/{EmployerId}/PaySchedules/Tags
• GETRuns the P32 report/Report/P32/run
• GETRuns the P45 report/Report/P45/run
• GETRuns the P60 report/Report/P60/run
• GETRuns the PASS report/Report/PASS/run
• GETGet user tag/User/{UserId}/Tag/{TagId}
• GETGets the employer/Employer/{EmployerId}
• GETGet XSD schema/Schemas/{DtoDataType}
• GETRuns the employer summary report/Report/EMPSUM/run
• GETRuns the holiday balance report/Report/HOLBAL/run
• GETRuns the net pay report/Report/NETPAY/run
• GETRuns the P11 summary report/Report/P11SUM/run
• GETRuns the P32 summary report/Report/P32SUM/run
• GETRuns the PAPDIS report/Report/PAPDIS/run
• GETGet the object template/Template/{DtoDataType}
• GETRuns the gross to net report/Report/GRO2NET/run
• GETRuns the journal report/Report/JOURNAL/run
• GETRuns the verbose payslip report/Report/PAYSLIP3/run

How automating PayRun.IO works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live PayRun.IO account.
4. Grant access, then go live. You approve the specific PayRun.IO operations it may use — and only those.

Automate PayRun.IO with these

• Stripe442 operations
• Zuora Reference Billing428 operations
• bunq421 operations
• Sinao272 operations
• Xero Accounting224 operations
• The Plaid191 operations
• Biapi Budgea Documentation167 operations
• Naviplancentral Advicent.FactFinderService151 operations
• Bigredcloud Big Red Cloud111 operations
• Codat Accounting105 operations
• Portfoliooptimizer Portfolio Optimizer83 operations
• Tradematic Cloud67 operations

Categories

• Finance

Questions about PayRun.IO automation

Can HumDay connect to PayRun.IO?

Yes. HumDay reads PayRun.IO's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 389 operations are documented.

Do I need to write code to automate PayRun.IO?

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

What can HumDay do in PayRun.IO?

145 of the 389 documented operations change something in PayRun.IO, and 244 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my PayRun.IO account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to PayRun.IO is held behind that approval.

Where this came from

The operations above are read from a published API description for PayRun.IO at api.test.payrun.io/swagger/json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.