Get org information in Ritc
A documented Ritc 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 org information
- GETReads data · Orgs
api.ritc.io/orgs/me
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 Ritc 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 Ritc operations
- Create a new App UserPOST · changes data
- Create a channelPOST · changes data
- Assign a channel to a userPOST · changes data
- Create a new appPOST · changes data
- Create a new rulePOST · changes data
- Create a new actionPOST · changes data
- Remove a user channel assignmentDELETE · changes data
- Create a new trigger in an appPOST · changes data
Questions
- Can HumDay get org information in Ritc?
- Yes. This operation is published in Ritc'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 Ritc account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Ritc.
- 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 Ritc account.
Where this came from
Read from a published API description for Ritc at www.ritc.io/openapi/ritc.swagger.json. The description above is the provider’s own wording, not ours. Last published 2017-04-04.