Get all employer tags in PayRun.IO
A documented PayRun.IO operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get all employer tags
- GETReads data · Tagging
api.test.payrun.io/Employers/Tags
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which PayRun.IO operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other PayRun.IO operations
- Post user objectPOST · changes data
- Create a new report definitionPOST · changes data
- Create a new Application secretPOST · changes data
- Create a new EmployerPOST · changes data
- Create a new transform definitionPOST · changes data
- Creates a new Journal Instruction templatePOST · changes data
- Create new CIS jobPOST · changes data
- Create new DPS jobPOST · changes data
Questions
- Can HumDay get all employer tags in PayRun.IO?
- Yes. This operation is published in PayRun.IO's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my PayRun.IO account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in PayRun.IO.
- 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 PayRun.IO account.
Where this came from
Read from a published API description for PayRun.IO at api.test.payrun.io/swagger/json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.