Extension Guider

Cashback extension

While powerful in their own right, including further functionality and additional features is proven to boost user engagement. Each of these popular features can be included with all of our developed extensions:

After extension installation, extension
button will be added to user browser
User can open extension menu
by pressing on the extension button
Live cashback notifications reminds your users
that they will get cashback at the exact time
they visit the merchant website
Your icon will be displayed next to relevant listings on major search engines such as Google.
This immediately alerts the user that they can get cashback from you for purchasing on these sites.

What is API

In terms of definition, APIs connect pieces of software together. They ‘glue’ together any required information components around a system and are often ‘released’ to third-party programmers who will want to connect application elements and services together.

For browsers extension development - API is a way to communicate between extension and customer's server - e.g get information about deals, stores and offers or send any kind of statistics

store

Array request

Some methods should have the same response for all users (logged or not)
accessibility

User info

Some method's answers should depend on user's auth state
subdirectory_arrow_right

User login

You need to set a special cookie on your site when user is logged (without HTTPOnly and secure flags). Then extension will use this cookie in API requests.
exit_to_app

User logout

When user is logout, you can just remove this cookie from user's browser.

Updating

If you want to update extension in any store, use your developer dashboard:

Distribution on your own

Firefox and Chrome extensions can be distributed using inline installation.

It is more convenient for users to install extension directly from your site without redirect to store.

If you are going to use inline instalization for Firefox, you need to create two instances on you server: 1) Update-file URL - it's location where you are going to store update-file (e.g http://www.example.com/path/update.firefox.xml); 2)Build URL - path to fresh build of your extension (e.g you can store it on your server - http://example.com/path/to/build/extension.xpi or you can submit your extension to the Mozilla Addons and set link like this https://addons.mozilla.org/firefox/downloads/latest/{addon-name}/{addon_id}-latest.xpi);

In case inline instalization for Chrome you still need to submit your extension to Chrome Web Store, but you can choose to not list it and use inline instalization insted. Just set next inputs in Developer Dashboard: Websites - to your site url, Inline install to "This item uses inline install" and Visibility options to "Unlisted".