Multilogin X API

## **Multilogin X API Documentation** Welcome to the Multilogin X API documentation. This documentation serves to explain how to automate Multilogin X API endpoints by using scripts, bots and automation in general. Our API enables users and developers to programmatically manage browser profiles, perform actions such as creating, modifying, or deleting profiles, and retrieve data related to profile usage, activity etc. ## **Authentication** Most of the API requests must be authenticated using Bearer Token. You can generate Bearer Token by signing in or refreshing it when needed. The regular token has 30 minutes of lifetime. Upon expiration, you may refresh it with `POST /user/refresh_token` to obtain a new one. To have higher rate limits and a longer token lifetime, it is recommended to get the [automation token](https://documenter.getpostman.com/view/28533318/2s946h9Cv9#918a9c42-cb0f-497f-9bdd-a44d9d760be5). ## **Endpoints Overview** The Multilogin X API provides endpoints for various actions divided into the following categories: - **Base URL**: api.multilogin.com - **Launcher:** Start, stop, get basic infomation about browser profiles. - **Profile Management:** Create, update, delete, browser profiles. - **Profile Access Management**: Sign in, manage your password and token, get basic information on workspaces. - **Browser Profile Data:** Unlock browser profiles. ## **Request and Response Format** The API accepts JSON-formatted requests and returns responses in JSON format. ## **Error Handling** The API follows standard HTTP status codes to indicate the success or failure of requests. Error responses include error messages to assist in troubleshooting. Errors are categorized into the following groups: 1. **Client Errors (4xx):** These errors occur when there is an issue with the client's request, such as invalid parameters or unauthorized access. - **400 Bad Request:** The request was invalid or malformed. Check the request parameters and try again. This type typically relates to wrong or invalid data being sent. - **401 Unauthorized:** Authentication credentials are missing or invalid. Ensure you are using valid credentials and tokens. - **403 Forbidden:** The user does not have permission to access the requested resource. - **429 Too Many Request:** The error indicates that the user has sent too many requests in a given amount of time exceeding the rate limit. 2. **Server Errors (5xx):** These errors occur when there is an issue on the server side, such as internal server errors or service unavailable. - **500 Internal Server Error:** An unexpected error occurred on the server side. This may happen when the server cannot process your request due to multiple technical reasons. Wrong payloads or inconsistent data sent can also raise this error. Contact support if the issue persists. For more information on using the Multilogin X API, please refer to the API documentation with code examples or navigate to our [support page](https://help.multilogin.com/en_US/multilogin-x). Have feedback to share? Take a minute to fiil in this quick [survey](https://tally.so/r/nWABkk).

Updated: 2026-04-05 | Source category: Quick solutions with Developer Tools | This page is an original SaaSVerdict rewrite from internal reference material.