Create a new app in Ritc
A documented Ritc 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 a new app
- POSTChanges data · Apps
api.ritc.io/apps
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. Because this one changes data, it cannot run until you have explicitly granted it.
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 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
- Create a channel functionPOST · changes data
Questions
- Can HumDay create a new app 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.
- Will this change my Ritc data?
- Yes — this is a POST operation, so it changes something in Ritc. 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 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.