Before you can start coding your first client application, there are a few things you need to do, if you haven't done them already.
Get a Google Account
You need a Google Account in order to create a project in the Chrome Device Token API. If you already have an account, then you're all set.
You may also want a separate Google Account for testing purposes.
Create a project for your client
Before you can send requests to Chrome Device Token API, you need to tell Google about your client and activate access to the API. You do this by using the Chrome Device Token API to create a project, which is a named collection of settings and API access information, and register your application.
To get started using Chrome Device Token API, you need to first use the setup tool, which guides you through creating a project in the Google API Console, enabling the API, and creating credentials.
If you haven't done so already, create your application's API key by clicking Create credentials > API key. Next, look for your API key in the API keys section.
Learn REST basics
REST in the Chrome Device Token API
The Chrome Device Token API operations map directly to REST HTTP verbs.
The specific formats for Chrome Device Token API URIs are:
https://chromedevicetoken.googleapis.com/v1/resourcePath?parameters
The full set of URIs used for each supported operation in the API is summarized in the Chrome Device Token API Reference document.
Learn JSON basics
The Chrome Device Token API returns data in JSON format.
JSON (JavaScript Object Notation) is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see json.org.