Google

Playable Locations API

Playable Locations API endpoints from Google

Developer tools#openapi#analytics#media

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Playable Locations API endpoints from Google

Endpoints 3

v3

  • POSTplayablelocations.logImpressions/v3:logImpressions?$.xgafv=1&access_token=string&alt=json&callback=string&fields=string&key=string&oauth_token=string&prettyPrint=true&quotaUser=string&upload_protocol=string&uploadType=stringLogs new events when playable locations are displayed, and when they are interacted with. Impressions are not partially saved; either all impressions are…
  • POSTplayablelocations.logPlayerReports/v3:logPlayerReports?$.xgafv=1&access_token=string&alt=json&callback=string&fields=string&key=string&oauth_token=string&prettyPrint=true&quotaUser=string&upload_protocol=string&uploadType=stringLogs bad playable location reports submitted by players. Reports are not partially saved; either all reports are saved and this request succeeds, or no…
  • POSTplayablelocations.samplePlayableLocations/v3:samplePlayableLocations?$.xgafv=1&access_token=string&alt=json&callback=string&fields=string&key=string&oauth_token=string&prettyPrint=true&quotaUser=string&upload_protocol=string&uploadType=stringReturns a set of playable locations that lie within a specified area, that satisfy optional filter criteria. Note: Identical SamplePlayableLocations requests…

API details

Base URL
https://playablelocations.googleapis.com
Authentication
None declared in the description
Operations
3 operations on 3 pathsPOST 3
Main resources
v3 3
Response formats
application/json
Description format
OpenAPI 3.0.0, API version v3
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the Playable Locations API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Playable Locations API collection, without the publisher's secrets.
  3. Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
  4. Send a requestPick an endpoint, for example “playablelocations.logImpressions” (POST /v3:logImpressions?$.xgafv=1&access_token=string&alt=json&callback=string&fields=string&key=string&oauth_token=string&prettyPrint=true&quotaUser=string&upload_protocol=string&uploadType=string), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Playable Locations API?

Playable Locations API endpoints from Google It is listed under Developer tools and has 3 endpoints.

Who publishes the Playable Locations API?

It is listed from Google's public API description (an OpenAPI document), not published by Google on Swastik Codes. Anyone who controls googleapis.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Playable Locations API?

Requests go to https://playablelocations.googleapis.com. Endpoint paths are added to this base URL.

How do I authenticate with the Playable Locations API?

Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.

How many endpoints does the Playable Locations API have?

3 operations on 3 paths (3 POST). The largest groups are v3.

Is forking the Playable Locations API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.