Skip to main content
Upload a Chrome extension once, then load it into any browser session you open. Uploads, lists, reads and deletes are free. The extension runs in the session, so you pay only for the session.

Upload an extension

Get an API key in the Quickstart. Send the extension as a zip with manifest.json at its root, in a multipart form field named file. It must be Manifest V3. This small extension marks example.com pages.
content.js holds one line, document.documentElement.dataset.markedBy = "mark-page";. Zip the two files, then upload them.
The answer has status 201.
name and version come from manifest.json. Keep id. There is no update: upload again for a new id.

Load it into a session

Send the ids in extensionIds when you open a session, up to 3. They load before the first page opens and cannot change while the session runs.
The session answer lists them in extensions, in the order you sent, with the id Chrome gave each one. Use runtimeId in chrome-extension://{runtimeId}/ addresses.
To check that it ran, execute code that reads the mark.
The real result was mark-page. Leave extensionIds out for a plain browser: an extension changes what sites can see, so only sessions opened with one have it.

List, read and delete

A delete answers { "success": true }. After it, reading the id returns 404 notFound with No extension with that id.

Options

Limits and errors

  • Manifest V3 only. You can keep 100 extensions.
  • A manifest.json with a key field, or with the debugger, proxy, processes, dns, experimental or enterprise.* permission, returns 400 prohibitedPermission. A real answer for debugger: The debugger permission is not allowed.
  • An id that does not exist, or was deleted, returns 404 notFound.
  • More than 3 ids, or the same id twice, in extensionIds returns 400 invalidRequest.