HumDay

Resets scores for the leaderboard with the given ID in Google Play Game Management

A documented Google Play Game Management operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Resets scores for the leaderboard with the given ID for the currently authenticated player.

  • POSTChanges data · scoresgamesmanagement.googleapis.com/games/v1management/leaderboards/{leaderboardId}/scores/reset

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Play Game Management operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Play Game Management operations

All 18 Google Play Game Management operations

Questions

Can HumDay resets scores for the leaderboard with the given id in Google Play Game Management?
Yes. This operation is published in Google Play Game Management'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 Play Game Management data?
Yes — this is a POST operation, so it changes something in Google Play Game Management. 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 Play Game Management account.

Where this came from

Read from a published API description for Google Play Game Management at gamesmanagement.googleapis.com/$discovery/rest?version=v1management. The description above is the provider’s own wording, not ours. Last published 2023-04-21.