Create Score Configurations in Truora Checks
A documented Truora Checks 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
Create Score Configurations
- POSTChanges data · custom-type
api.truora.com/v1/config
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 Truora Checks 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 Truora Checks operations
- Creates a hook subscriptionPOST · changes data
- Create a background checkPOST · changes data
- Create ReportPOST · changes data
- Creates a continuous checkPOST · changes data
- Delete Custom TypeDELETE · changes data
- Update Custom TypePUT · changes data
- Report BehaviorPOST · changes data
- Batch UploadPOST · changes data
Questions
- Can HumDay create score configurations in Truora Checks?
- Yes. This operation is published in Truora Checks'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 Truora Checks data?
- Yes — this is a POST operation, so it changes something in Truora Checks. 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 Truora Checks account.
Where this came from
Read from a published API description for Truora Checks at docs.truora.com/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-08-16.