Docs

Microsoft Edge Add-ons ​

Edge submissions go through the Partner Center API v1.1. The flow is upload a draft, poll the operation, then submit the draft for review. The platform runs it with the project's stored credentials; trigger it from the console's Stores tab, from an agent with extension_submit, or with POST /api/cli/stores/submit. See Publishing.

Credentials ​

Requests authenticate with two headers: Authorization: ApiKey <key> and X-ClientID.

ValueSecretNotes
Client IDSTORE_EDGE_CLIENT_IDPartner Center API settings, sent as X-ClientID
API keySTORE_EDGE_CLIENT_SECRETPartner Center API settings, sent as ApiKey

Add them from Stores, New, Edge in the console.

Submitting ​

Submit from the Stores tab, or over the API:

bash
curl -s -X POST https://www.extension.dev/api/cli/stores/submit \
  -H "Authorization: Bearer $EXTENSION_DEV_TOKEN" \
  -d '{"browsers":["edge"],"buildSha":"<sha>","channel":"stable"}'

Edge accepts the same Manifest V3 package as Chrome, so a project usually submits one Chromium build to both.

Upload without publishing ​

Draft-only safe mode uploads the package to the Edge draft and leaves it there: no review submission happens. It is a per-store setting, and agents default to safe.

Certification notes ​

Edge certification notes are read from STORE.md in the project root and submitted automatically. See Publishing.

Watching ​

The Stores tab follows the submission to a terminal state: in_review, processing, published, rejected, failed. The same status returns from GET /api/projects/{id}/stores/status. Edge tracks by the operation id the upload returns, not a version id.

When it fails ​

  • The upload operation is asynchronous. A failed operation reports its errors when polled; the submit step never ran.
  • Authentication failures mean the header pair, not the package. Confirm the client ID and API key both come from the same Partner Center account.
  • The preflight, dryRun on the submit call, reports credential health per store and the console page that fixes a blocked one.
  • A submission sitting in processing is still on Microsoft's side. Give it time before assuming failure.

Last verified against Partner Center API v1.1 on 2026-07-27. Submission outcomes are subject to Microsoft Edge Add-ons review and policy.

Next ​