Chrome Device Token API
Stay organized with collections
Save and categorize content based on your preferences.
Service: chromedevicetoken.googleapis.com
To call this service, we recommend that you use the Google-provided client libraries. If your application needs to use your own libraries to call this service, use the following information when you make the API requests.
Discovery document
A Discovery Document is a machine-readable specification for describing and consuming REST APIs. It is used to build client libraries, IDE plugins, and other tools that interact with Google APIs. One service may provide multiple discovery documents. This service provides the following discovery document:
Service endpoint
A service endpoint is a base URL that specifies the network address of an API service. One service might have multiple service endpoints. This service has the following service endpoint and all URIs below are relative to this service endpoint:
https://chromedevicetoken.googleapis.com
| Methods |
create |
POST /v1/tokens
Create a Device Token. |
list |
GET /v1/tokens
List valid Chrome Device Tokens owned by a user. |
verify |
GET /v1/tokens/{name}:verify
Verify a Chrome Device Token. |
| Methods |
invalidateToken |
POST /v1/users:invalidateToken
Invalidate a user's existing Chrome Device Token and create a new token. |
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 2024-10-16 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 2024-10-16 UTC."],[[["\u003cp\u003eThe Chrome Device Token service enables management of device tokens, allowing creation, listing, and verification.\u003c/p\u003e\n"],["\u003cp\u003eThe service provides a discovery document for generating client libraries and other tools for API interaction.\u003c/p\u003e\n"],["\u003cp\u003eThe service endpoint for making API requests is \u003ccode\u003ehttps://chromedevicetoken.googleapis.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can utilize the REST resources to create, list, verify, and invalidate Chrome Device Tokens.\u003c/p\u003e\n"]]],[],null,["# Chrome Device Token API\n\n- [REST Resource: v1.tokens](#v1.tokens)\n- [REST Resource: v1.users](#v1.users)\n\nService: chromedevicetoken.googleapis.com\n-----------------------------------------\n\nTo call this service, we recommend that you use the Google-provided [client libraries](https://cloud.google.com/apis/docs/client-libraries-explained). If your application needs to use your own libraries to call this service, use the following information when you make the API requests.\n\n### Discovery document\n\nA [Discovery Document](https://developers.google.com/discovery/v1/reference/apis) is a machine-readable specification for describing and consuming REST APIs. It is used to build client libraries, IDE plugins, and other tools that interact with Google APIs. One service may provide multiple discovery documents. This service provides the following discovery document:\n\n- \u003chttps://chromedevicetoken.googleapis.com/$discovery/rest?version=v1\u003e\n\n### Service endpoint\n\nA [service endpoint](https://cloud.google.com/apis/design/glossary#api_service_endpoint) is a base URL that specifies the network address of an API service. One service might have multiple service endpoints. This service has the following service endpoint and all URIs below are relative to this service endpoint:\n\n- `https://chromedevicetoken.googleapis.com`\n\nREST Resource: [v1.tokens](/chrome/chrome-device-token/rest/v1/tokens)\n----------------------------------------------------------------------\n\n| Methods ||\n|-------------------------------------------------------------|-------------------------------------------------------------------|\n| [create](/chrome/chrome-device-token/rest/v1/tokens/create) | `POST /v1/tokens` Create a Device Token. |\n| [list](/chrome/chrome-device-token/rest/v1/tokens/list) | `GET /v1/tokens` List valid Chrome Device Tokens owned by a user. |\n| [verify](/chrome/chrome-device-token/rest/v1/tokens/verify) | `GET /v1/tokens/{name}:verify` Verify a Chrome Device Token. |\n\nREST Resource: [v1.users](/chrome/chrome-device-token/rest/v1/users)\n--------------------------------------------------------------------\n\n| Methods ||\n|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|\n| [invalidateToken](/chrome/chrome-device-token/rest/v1/users/invalidateToken) | `POST /v1/users:invalidateToken` Invalidate a user's existing Chrome Device Token and create a new token. |"]]
