How to control core updates via API

Managing browser core updates is essential for maintaining compatibility and security in your Multilogin profiles. With the Multilogin API, you can control whether profiles automatically update to the latest core version or remain on a specific version. This guide explains how to use the auto_update_core parameter across relevant API endpoints to manage core updates effectively.

Overview

The auto_update_core parameter allows you to enable or disable automatic core updates when creating or updating browser profiles. This parameter is supported in the following API endpoints:

• Start Quick Profile: Create a profile with quick setup.
• Profile Create: Create a new profile with detailed configuration.
• Profile Update: Modify an existing profile’s settings.

By configuring auto_update_core, you can ensure profiles either stay up-to-date with the latest core version or remain on a specific version for compatibility or testing purposes.

---

Configuring Core Updates

Enable Automatic Core Updates

To ensure your profiles always use the latest browser core version, set auto_update_core to true. This is the default setting for new profiles.

{
  "auto_update_core": true
}

Why Use Automatic Updates?

Automatic updates keep your profiles aligned with the latest browser core versions, ensuring compatibility with modern websites and reducing the risk of detection due to outdated cores.

Disable Automatic Core Updates

To maintain a specific core version, set auto_update_core to false and specify the desired core_version. This is useful for testing or when a specific version is required.

{
  "core_version": 130,
  "auto_update_core": false
}

Important Note

When disabling automatic updates, you must manually monitor and update the core_version as needed. Multilogin is not responsible for bans or detection issues caused by outdated core versions.

---

Using the API Endpoints

Below are examples of how to configure core updates in the supported API endpoints.

Start Quick Profile

Create a profile with automatic core updates enabled:

{
  "auto_update_core": true
}

Or disable updates and specify a core version:

{
  "core_version": 130,
  "auto_update_core": false
}

Profile Create

Create a new profile with automatic updates disabled:

{
  "name": "MyProfile",
  "core_version": 130,
  "auto_update_core": false
}

Profile Update

Update an existing profile to enable automatic updates:

{
  "profile_id": "12345",
  "auto_update_core": true
}

Or keep a specific core version:

{
  "profile_id": "12345",
  "core_version": 130,
  "auto_update_core": false
}

---

Key Considerations

To ensure smooth operation when managing core updates, keep the following in mind:

Consideration	Details
Default Behavior	If auto_update_core is unspecified in the Profile Update endpoint, it resets to true, enabling automatic updates.
Maintaining Core Version	To prevent automatic updates, explicitly set auto_update_core to false when updating a profile.
Core Version Limitations	Changing the core_version to anything other than the latest version is not supported during profile updates.
Risks of Outdated Cores	Using outdated core versions may lead to detection or bans. Multilogin recommends enabling automatic updates for optimal performance.

Stay Updated

We strongly recommend using the default setting (auto_update_core: true) to keep your browser cores up-to-date. This minimizes compatibility issues and enhances profile security.