Automate KumpeApps
HumDay reads KumpeApps’s own published API description and derives 26 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What KumpeApps is
KKid API. Due to security concerns all calls to this API requires authentication. If you have access then you may use your KumpeApps username/password to authenticate. To gain access please use the contact developer link below.
API host: restapi.kumpeapps.com
What HumDay can do in KumpeApps
18 documented operations change something in KumpeApps.
- POSTadds new child user
/kkid/userlist - POSTadds new master user account
/kkid/masteruser - POSTAdd item to kid's wishlist
/kkid/wishlist - POSTadds new allowance transaction to kidUserID
/kkid/allowance - POSTadds chore for given user
/kkid/chorelist - DELETEdeletes user
/kkid/userlist - PUTupdates user
/kkid/userlist - DELETEDelete item from wishlist
/kkid/wishlist - PUTUpdate item on kid's wishlist
/kkid/wishlist - POSTRequest auth key for user (login user)
/authentication/authkey - POSTsubscribes/unsubscribes/registers for apns push notifications
/kkid/apns - DELETEdeletes chore for given chore id
/kkid/chorelist - PUTupdates chore for given chore id
/kkid/chorelist - PATCHCompromise app key
/authentication/appkey - POSTRequest app key
/authentication/appkey - PUTDeactivate app key
/authentication/appkey - PATCHCompromise auth key
/authentication/authkey - PUTDeactivate auth key (logout)
/authentication/authkey
What HumDay can read from KumpeApps
These are the operations a schedule or a trigger can watch.
- GETCreate Share Link
/kkid/share - GETreturns list of users
/kkid/userlist - GETGet list of wishlist items
/kkid/wishlist - GETreturns list of chores for given user
/kkid/chorelist - GETGets user info
/kkid/user - GETRequest auth key for user (login user)
/authentication/authkey - GETVerifies YubiKey OTP for authenticated user
/authentication/verifyotp - GETreturns allowance balance and allowance transactions
/kkid/allowance
How automating KumpeApps works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live KumpeApps account.
- Grant access, then go live. You approve the specific KumpeApps operations it may use — and only those.
Questions about KumpeApps automation
- Can HumDay connect to KumpeApps?
- Yes. HumDay reads KumpeApps's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 26 operations are documented.
- Do I need to write code to automate KumpeApps?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your KumpeApps account.
- What can HumDay do in KumpeApps?
- 18 of the 26 documented operations change something in KumpeApps, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my KumpeApps account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to KumpeApps is held behind that approval.
Where this came from
The operations above are read from a published API description for KumpeApps at api.kumpeapps.com/python/swagger/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.