manifest.json for Chrome, Edge, Firefox, and Safari, and stops at the package that extension build --zip produces, so the values below feed your own submission tooling.
Automated Chrome Web Store submissions need two identifiers and one credential set:
You need either the OAuth trio or the service account, not both. When both are configured, the service account wins.
extension.dev,
the sponsor of Extension.js, handles publishing, store submission, and sharing
from the same project. Its docs cover the steps after
extension build.Prerequisites
- Register a developer account at the Chrome Web Store Developer Dashboard. Registration has a one-time $5 fee.
- Turn on 2-step verification for your Google Account. Google requires it to publish or update an extension.
- Build a store zip (
npx extension build --browser chrome --zip). - Upload that zip manually in the dashboard to create the item.
- Copy the extension ID from the item’s dashboard URL.
- Copy the publisher ID from Publisher > Settings in the Developer
Dashboard. If you belong to more than one publisher, switch to the right
one first. The same UUID is in your dev console URL,
chrome.google.com/webstore/devconsole/<UUID>.
Two routes mint the refresh token, and each one needs its own client type. A
Web application client goes with the Google OAuth Playground. A Desktop app
client goes with a loopback consent flow. The error
redirect_uri_mismatch
means that the client type and the minting route were mixed.Create the OAuth client
- Create or choose a project in the Google Cloud Console.
- Enable the Chrome Web Store API for that project.
Route 1: a Web application client and the OAuth Playground
This is the route in Google’s guide, Use the Chrome Web Store API.- On the credentials page, create an OAuth client ID with application type Web application.
- Add
https://developers.google.com/oauthplaygroundto the Authorized redirect URIs. - Copy the client ID and the client secret.
- Open the OAuth 2.0 Playground.
- Open the settings and choose Use your own OAuth credentials.
- Enter your client ID and client secret.
- Enter
https://www.googleapis.com/auth/chromewebstorein Input your own scopes. - Click Authorize APIs.
- Sign in with the Google Account that owns the store items.
- Click Exchange authorization code for tokens.
- Copy the refresh token.
Route 2: a Desktop app client and a loopback flow
- On the credentials page, create an OAuth client ID with application type Desktop app.
- Copy the client ID and the client secret.
- Mint a refresh token for that client with a loopback consent flow on
127.0.0.1, which is the redirect a Desktop app client accepts. The token must authorize thehttps://www.googleapis.com/auth/chromewebstorescope.
redirect_uri_mismatch has two causes. A Desktop app client was taken to the
Playground, or a Web application client lacks the Playground redirect URI.
Alternative: a service account
A Google Cloud service account avoids OAuth consent entirely and is the most stable choice for CI:- In the Google Cloud Console, create a service account in the same project that has the Chrome Web Store API enabled.
- Create a JSON key for it and download the file.
- In the Chrome Web Store dev console, open Account and add the service account’s email address to your publisher. One service account per publisher.

