Blasts Kit Sample - settings

This sample shows "Sign in with the Blasts Deals app" inside an extension that has no backend and no secrets. Everything it needs is public: your partner id, and the extension id the browser sends as the request origin.

1. Your partner

Partner id (from the Blasts developer console; a sandbox id ends in -test) Your product's name (shown in the messages this sample prints)

Nothing here is a credential. Never put an API key or signing secret into an extension - the kit refuses them on purpose.

2. Register THIS extension's id with your partner

The server only answers an extension whose id you registered. This copy of the sample is running as:

...

In the developer console, open your partner's Extension sign-in card, paste the id above, and save. The id changes if you load the folder from a different path, so re-register after moving it.

3. Save

Then open the popup: click the puzzle-piece Extensions icon to the right of Chrome's address bar, then click Blasts Kit Sample in the list (click the pin icon there once and it becomes a one-click button). Sign in there. A sandbox partner rings only the phone of the console account that created it - request live keys when you are ready to serve other people.