Get Background Check in Truora Checks
A documented Truora Checks 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 Background Check
- GETReads data · checks
api.truora.com/v1/checks/{check_id}
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. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Truora Checks operations
- Creates a hook subscriptionPOST · changes data
- Create a background checkPOST · changes data
- Create Score ConfigurationsPOST · 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
Questions
- Can HumDay get background check 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.
- Does this change anything in my Truora Checks account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Truora Checks.
- 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.