chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension must request
accessibilityFeatures.read permission. For modifying feature state, the extension needs
accessibilityFeatures.modify permission. Note that
accessibilityFeatures.modify does not imply
Use actions to put icons in the main Google Chrome toolbar, to the right of the address bar. Actions can be set to take action on all pages (default_state: enabled) or only the current page (default_state: disabled). If an action is default disabled, the action appears grayed out when inactive. In addition to its icon, an action can also have a tooltip, a badge, and a popup.
chrome.alarms API to schedule code to run periodically or at a specified time in the future.
chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. Also see Override Pages, which you can use to create a custom Bookmark Manager page.
Use browser actions to put icons in the main Google Chrome toolbar, to the right of the address bar. In addition to its icon, a browser action can have a tooltip, a badge, and a popup.
chrome.browsingData API to remove browsing data from a user's local profile.
Use this API to expose certificates to the platform which can use these certificates for TLS authentications.
Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension.
chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages.
chrome.cookies API to query and modify cookies, and to be notified when they change.
chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol. Use
tabId to target tabs with sendCommand and route events by
tabId from onEvent callbacks.
chrome.declarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content.
chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy.
Desktop Capture API that can be used to capture content of screen, individual windows or tabs.
chrome.devtools.inspectedWindow API to interact with the inspected window: obtain the tab ID for the inspected page, evaluate the code in the context of the inspected window, reload the page, or obtain the list of resources within the page.
chrome.devtools.network API to retrieve the information about network requests displayed by the Developer Tools in the Network panel.
chrome.devtools.panels API to integrate your extension into Developer Tools window UI: create your own panels, access existing panels, and add sidebars.
chrome.documentScan API to discover and retrieve images from attached paper document scanners.
chrome.downloads API to programmatically initiate, monitor, manipulate, and search for downloads.
chrome.enterprise.deviceAttributes API to read device attributes. Note: This API is only available to extensions force-installed by enterprise policy.
chrome.enterprise.hardwarePlatform API to get the manufacturer and model of the hardware platform where the browser runs. Note: This API is only available to extensions installed by enterprise policy.
chrome.enterprise.networkingAttributes API to read information about your current network. Note: This API is only available to extensions force-installed by enterprise policy.
chrome.enterprise.platformKeys API to generate hardware-backed keys and to install certificates for these keys. The certificates will be managed by the platform and can be used for TLS authentication, network access or by other extension through chrome.platformKeys.
chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens.
chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing.
chrome.extensionTypes API contains type declarations for Chrome extensions.
chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website.
chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS.
chrome.fontSettings API to manage Chrome's font settings.
chrome.gcm to enable apps and extensions to send and receive messages through the Google Cloud Messaging Service.
chrome.history API to interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history. To override the history page with your own version, see Override Pages.
chrome.i18n infrastructure to implement internationalization across your whole app or extension.
chrome.identity API to get OAuth2 access tokens.
chrome.idle API to detect when the machine's idle state changes.
chrome.input.ime API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window.
chrome.instanceID to access the Instance ID service.
chrome.loginState API to read and monitor the login state.
chrome.management API provides ways to manage the list of extensions/apps that are installed and running. It is particularly useful for extensions that override the built-in New Tab page.
chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray.
The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox.
chrome.pageAction API to put icons in the main Google Chrome toolbar, to the right of the address bar. Page actions represent actions that can be taken on the current page, but that aren't applicable to all pages. Page actions appear grayed out when inactive.
chrome.pageCapture API to save a tab as MHTML.
chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary.
chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform managed certificates in third party VPNs (see chrome.vpnProvider).
chrome.power API to override the system's power management features.
chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers.
chrome.printing API to send print jobs to printers installed on Chromebook.
chrome.printingMetrics API to fetch data about printing usage.
chrome.privacy API to control usage of the features in Chrome that can affect a user's privacy. This API relies on the ChromeSetting prototype of the type API for getting and setting Chrome's configuration.
chrome.proxy API to manage Chrome's proxy settings. This API relies on the ChromeSetting prototype of the type API for getting and setting the proxy configuration.
chrome.runtime API to retrieve the background page, return details about the manifest, and listen for and respond to events in the app or extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.
chrome.scripting API to execute script in different contexts.
chrome.search API to search via the default provider.
chrome.sessions API to query and restore tabs and windows from a browsing session.
chrome.storage API to store, retrieve, and track changes to user data.
system.cpu API to query CPU metadata.
system.display API to query display metadata.
chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached.
chrome.tabCapture API to interact with tab media streams.
chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser.
chrome.topSites API to access the top sites (i.e. most visited sites) that are displayed on the new tab page. These do not include shortcuts customized by the user.
chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine.
chrome.ttsEngine API to implement a text-to-speech(TTS) engine using an extension. If your extension registers using this API, it will receive events containing an utterance to be spoken and other parameters when any extension or Chrome App uses the tts API to generate speech. Your extension can then use any available web technology to synthesize and output the speech, and send events back to the calling function to report the status.
chrome.types API contains type declarations for Chrome.
chrome.vpnProvider API to implement a VPN client.
chrome.wallpaper API to change the ChromeOS wallpaper.
chrome.webNavigation API to receive notifications about the status of navigation requests in-flight.
chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight.
chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser.