Request & Response Format

All Multilogin X API endpoints accept and return JSON.

Request Headers

Every authenticated request must include:

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
Accept: application/json

Some endpoints also accept:

Header	Type	Description
X-Strict-Mode	boolean	Enable strict parameter validation (default: false)

Standard Response Structure

Every API response follows this structure:

{
  "status": {
    "error_code": "",
    "http_code": 200,
    "message": "Success"
  },
  "data": {
    // Response payload (object, array, or null)
  }
}

Status Object

Field	Type	Description
error_code	string	Empty string on success, error identifier on failure
http_code	number	HTTP status code
message	string	Human-readable message

Data Object

The data field varies per endpoint:

• Object for single-entity responses (profile details, token)
• Array for list responses (profile lists, folder contents)
• null for action-only responses (delete, update confirmations)

Pagination

List endpoints support pagination via query parameters:

Parameter	Type	Default	Description
limit	number	20	Number of items to return (max varies)
offset	number	0	Number of items to skip
sort_by	string	varies	Field to sort by
sort_order	string	asc	Sort direction: asc or desc

Filtering

Many list endpoints accept filter parameters:

# Filter profiles by name
curl "https://api.multilogin.com/workspace/profiles?search=my-profile&limit=10&offset=0" \
  -H "Authorization: Bearer YOUR_TOKEN"

Error Response Example

{
  "status": {
    "error_code": "INVALID_TOKEN",
    "http_code": 401,
    "message": "Token is expired or invalid"
  },
  "data": null
}

See Error Codes for the full list.