Venues, landmarks, regions, these are all places to search in LotaData
A documented LotaData 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
Venues, landmarks, regions, these are all places to search.
- GETReads data · Places
api2.lotadata.com/places
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 LotaData 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 LotaData operations
Questions
- Can HumDay venues, landmarks, regions, these are all places to search in LotaData?
- Yes. This operation is published in LotaData'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 LotaData account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in LotaData.
- 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 LotaData account.
Where this came from
Read from a published API description for LotaData at developers.lotadata.com/swagger/spec/apiv2.json. The description above is the provider’s own wording, not ours. Last published 2017-09-04.