In Multilogin, API rate limits tell you how many requests you can send per minute, while response codes show whether your request worked or what went wrong. 

➡️ In Postman, open the “Multilogin API” collection → choose a request → click “Send” → check the response status and body.

For regular API automation, use an automation token. It lasts longer and allows more requests per minute than a regular API token, which expires after 30 minutes.

What's the difference between API token types?

Multilogin uses three types of tokens for different authentication tasks.

• Automation token: generate it using “Workspace Automation Token” — recommended for regular automation, with a custom expiration period and your plan's RPM limits
• Regular API token: copy it from “Info” → “API token” in Multilogin, or get it through “User Sign In” – expires after 30 minutes and has lower rate limits
• Refresh token: returned by “User Sign In” — use it with “User Refresh Token (Switch Workspace)” to get a new regular API token without signing in again

A refresh token is only for getting a new regular API token. You can't use it to send API requests or renew an automation token. 

If your automation token expires, use a valid regular API token to generate a new one.

How many API requests can I send?

Multilogin measures API limits in RPM (requests per minute). Each API request counts toward your limit, whether you're managing Android cloud phones, browser profiles, or other Multilogin resources.

Here are the limits for automation tokens:

• Pro 10: 50 RPM
• Pro 20: 75 RPM
• Pro 50: 100 RPM
• Business: 100 RPM for standard plans – higher Business plans may have custom limits

You can check the current limits on the Multilogin pricing page.

Do team members share the same API limit?

Yes. Everyone in the same workspace shares one RPM limit, even if they're using different automation scripts or tokens.

For example, if you're on Pro 20, your workspace can send up to 75 requests per minute. If two team members send 40 requests each during the same minute, they could exceed that limit.

What happens if I reach my API limit?

Multilogin returns 429 – Too Many Requests when you exceed your RPM limit.

Wait for the limit to reset before sending more requests. If this happens often, try spreading out your requests instead of running them all at once.

Need more requests per minute? Check the available plans or contact Multilogin support to discuss your options.

What do API response codes mean?

Every Multilogin API request returns an HTTP status code. It tells you whether the request worked or if something needs your attention.

Here are the most common codes:

• 200 – OK: your request worked
• 201 – Created: something was created successfully
• 400 – Bad Request: something in your request is missing or incorrect – check the required parameters and values
• 401 – Unauthorized: your token may be missing, incorrect, or expired – check “Authorization” → “Bearer Token”
• 403 – Forbidden: you don't have permission to perform the action – check your workspace role
• 404 – Not Found: the requested resource wasn't found – check the documented endpoint and any IDs in your request
• 429 – Too Many Requests: you've reached your API rate limit – wait for the limit to reset
• 500 – Internal Server Error: something went wrong on the server – try again later or contact support if the issue continues

You can compare your request with the required parameters and formats in the Multilogin API documentation.

What does download_browser_profile_metadata with 200 mean?

It means Multilogin successfully fetched browser profile data from the server for later use.

This is normal, not an error. You don't need to fix anything.