Returns a set of playable locations
A documented Google Playable Locations 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
Returns a set of playable locations that lie within a specified area, that satisfy optional filter criteria.
- POSTChanges data · v3
playablelocations.googleapis.com/v3:samplePlayableLocations
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 Google Playable Locations 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 Google Playable Locations operations
Questions
- Can HumDay returns a set of playable locations in Google Playable Locations?
- Yes. This operation is published in Google Playable Locations'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 Google Playable Locations data?
- Yes — this is a POST operation, so it changes something in Google Playable Locations. 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 Google Playable Locations account.
Where this came from
Read from a published API description for Google Playable Locations at playablelocations.googleapis.com/$discovery/rest?version=v3. The description above is the provider’s own wording, not ours. Last published 2021-06-21.