Insert user tag in PayRun.IO
A documented PayRun.IO operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Insert user tag
- PUTChanges data · Tagging
api.test.payrun.io/User/{UserId}/Tag/{TagId}
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. Because this one changes data, it cannot run until you have explicitly granted it.
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 insert user tag 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.
- Will this change my PayRun.IO data?
- Yes — this is a PUT operation, so it changes something in PayRun.IO. 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 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.