API functionality can assist you in programmatically performing essential tasks such as quickly creating, starting, and closing browser profiles. Additionally, it enables browser automation with the supported automation frameworks like Selenium and Puppeteer that utilised WebDriver.
- Get MoreLogin API interface;
- Open MoreLogin to ensure you are logged in;
- "Browser profile" -> "API" View the API interface success status
- If you need to use the WebDriver mode, please make sure to enable the "Debug Port" switch in the "Settings" - "Local Settings" menu.
- MoreLogin API Interface List
Browser profile management
Start browser profile
Detect browser profile status
close browser profile
Quickly create browser profile
Modifying browser profile information
delete browser profile
Get profile list
Get group list
Get roxy list
- The interface has a request limit, with a maximum of 60 requests per minute for each interface
- API adopts HTTP mode connection, which updated continuously
- The browser profile started by the API needs to call the "detect browser profile status" interface for detection. Skipping this step may result in unexpected network issues. If you encounter issues with your automation code, it is recommended to first check the browser profile status and ensure it is functioning properly before running the browser automation code. You can refer to our practical examples for more details.
- When users encounter the issue of mismatched Chrome driver versions while using Selenium, here's how to handle it:
When you encounter the aforementioned problem, it means that the current browser kernel is not compatible with the installed Chrome driver version. You need to upgrade Selenium and delete the previously downloaded Chrome driver.
1.Open the command prompt and enter the following command: "pip install -U selenium." After running the command, check the Selenium version to ensure that it is version 4.10.0 or higher.
2.Add the following code to your automation script:
logger = logging.getLogger("selenium")
After running the code, locate the line in the output logs that says "Using driver at:". The file path that follows is the path to the incorrect version of the driver. Open the file manager and delete that file.