Want to back up specific parts of your browser profile, like cookies or extensions? Object Storage features will help you out with that. By uploading segments of browser data, you will protect them from getting lost. 

You will learn which API endpoints you can use for your profile objects.

The endpoints are split into categories for your convenience. All of them are available in “Object Storage” folder, “Multilogin API” collection.

List of object types

It might be the first API request, which is recommended to do in advance. GET List of object types provides various categories, which are used for object classification. The types include various categories, such as extensions, cookies, profile templates, passwords, automation scripts, and launch parameter templates.

Bearer (or automation) token is enough for executing the request.

Object upload, download, and deletion

How to upload the object 

POST Upload Object allows you to upload an object to the storage. You need to set the object type ID (which can be received from the following request: GET List of object types), object path (directory where you set your object), and storage type (cloud or local). There are also optional values, such as object meta (description of the object) and encryption. 

How to create and upload the object

POST Create and Upload Object can help with the upload of the file as well, but it also provides an option to make a new file inside the API request itself. For example, it can be useful if you exported cookies via API. It has the same parameters as POST Upload Object, but it also has object_name parameter for file name and object_extension for file extension.

How to download the object

If you need to download the object from the cloud, you can use GET Download Object for that. You need to know the ID of the object (you receive it as a response during the object upload, or you can find it via GET Objects Meta endpoint). Replace <id_upload> in the endpoint bar with it.

How to delete the object

You can use GET Delete Object for removing objects from storage. You need to state the ID of the object (you receive it as a response during the object upload, or you can find it via GET Objects Meta endpoint). There is also a parameter called permanently, which defines whether the object goes to the trash bin or not. Its value is set as false by default.

How to restore the object

If you removed the object and sent it to the trash bin (refer to the Object deletion chapter for that), you can recover the object. You need to know ID of the object (you receive it as a response during the object upload, or you can find it via GET List of object types endpoint). Replace :id in the endpoint bar with it.

Object statistics related endpoints

How to detect which profiles use the object

GET Object Profile Usages can be used for that purpose. Set your object ID (you receive it as a response during the object upload, or you can find it via GET List of object types endpoint) and replace Object ID in the endpoint bar.

How to get statistics for objects

GET Statistics for Objects provides info about the objects: how much space do they take, if they are available to the user, etc. Bearer/automation token is enough for running that API request.

How to receive meta info about objects

This endpoint displays various info related to profiles, such as ID, creation date, name, etc. It has various sorting parameters, which can help out to search necessary objects. Keep in mind that limit and offset values need to be set. You can add and adjust values of the parameters in the “Params” tab.

How to receive meta info about specific profile

If you need the info about one specific object – you can use this endpoint instead of GET Object Meta. You need to set the object ID for the request (you receive it as a response during the object upload, or you can find it via GET Objects Meta endpoint). Replace :id value with it.

How to print the list of objects used in the profile

Similar use case to GET Object Profile Usages, but it provides the list of objects used in the specific profile. You need to state the profile ID in the profile_id parameter (here is how you can get it: How to copy profile IDs in Multilogin). 

Storage type conversion

How to convert cloud object to local one

This endpoint is used to transfer a local object to cloud storage. You need to set the object_id value for it (you can receive it via GET Objects Meta). 

How to convert local object to cloud one

Endpoint: Local to Cloud

 

This endpoint is used to transfer an object from local storage to cloud storage. You need to set the directory of the object in object_path parameter and set object_id (you can get it via GET Objects Meta).

Extension management

Related to the extension manager feature, which is mentioned in the following article: How to install browser extensions in Multilogin (Extension manager method).

How to create extension object

Endpoint: Create Extension

 

POST Create Extension creates an object from the extension link. Set the browser_type (Mimic or Stealthfox), storage_type (cloud or local), and url values for the extension (from Chrome Web Store for Mimic and Firefox Add-ons for Stealthfox). 

If you have extension locally on your storage device, refer to the following endpoint: POST Upload Object.

 

How to enable and disable extension

Endpoints: 

• Enable Extension
• Disable Extension

 

You can use those endpoints for making extensions available for profiles or the opposite. The structure for both of them is similar: set the extension object ID (you can receive it via POST Upload Object, POST Create Extension or GET Objects Meta) in the endpoint bar and profile IDs (here is how you can get them: How to copy profile IDs in Multilogin) in the Body tab.