Prerequisites
Stay organized with collections
Save and categorize content based on your preferences.
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.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eYou need a Google Account to create a project and utilize the Chrome Device Token API, potentially using a separate account for testing.\u003c/p\u003e\n"],["\u003cp\u003eBefore sending API requests, create a project in the Google API Console to register your application and enable access to the Chrome Device Token API.\u003c/p\u003e\n"],["\u003cp\u003eThe Chrome Device Token API leverages REST HTTP verbs and utilizes specific URIs for various operations, detailed in the API Reference documentation.\u003c/p\u003e\n"],["\u003cp\u003eUnderstanding REST and JSON basics is essential for working with the API, as it maps operations to REST verbs and returns data in JSON format.\u003c/p\u003e\n"]]],[],null,["Before you can start coding your first client application, there are a few\nthings you need to do, if you haven't done them already.\n\nGet a Google Account\n\nYou need a [Google Account](https://www.google.com/accounts/NewAccount) in order to [create a project](#project) in the Chrome Device Token API. If you already have an account, then you're all set.\n\nYou may also want a separate Google Account for testing purposes.\n\nCreate a project for your client\n\nBefore 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.\n\nTo get started using Chrome Device Token API, you need to first\n[use\nthe setup tool](https://console.cloud.google.com/start/api?id=chromedevicetoken&credential=client_key), which guides you through creating a project in the\nGoogle API Console, enabling the API, and creating credentials.\n\nIf you haven't done so already, create your application's API key by clicking\n**Create credentials \\\u003e API key** . Next, look for your API key in the **API\nkeys** section.\n\nLearn REST basics\n\nREST in the Chrome Device Token API\n\nThe Chrome Device Token API operations map directly to REST HTTP verbs.\n\nThe specific formats for Chrome Device Token API URIs are: \n\n```\nhttps://chromedevicetoken.googleapis.com/v1/resourcePath?parameters\n```\n\nThe full set of URIs used for each supported operation in the API is summarized in the [Chrome Device Token API Reference](/chrome/chrome-device-token/rest/v1) document.\n\nLearn JSON basics\n\nThe Chrome Device Token API returns data in JSON format.\n\n\n[JSON](http://en.wikipedia.org/wiki/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](http://www.json.org/).\n\n\u003cbr /\u003e"]]
