Use strict mode when you want Multilogin to validate that all required fields are explicitly included in a profile create or update request.

➡️ Add the header X-Strict-Mode: true to the API request. If you leave the header out, Multilogin uses non-strict mode and applies default values where supported.

If a required field is missing in strict mode, the API returns an error that lists the missing fields.

Strict mode vs. non-strict mode

Strict mode

With X-Strict-Mode: true, the API requires all fields needed by strict validation to be provided explicitly.

• Missing required fields return an error
• The response lists the fields you need to add
• Use this when you want full control over request values instead of relying on defaults

Non-strict mode

Non-strict mode is the default when X-Strict-Mode is not included.

• Supported omitted fields can use Multilogin default values
• Use this when you don’t need to define every supported parameter yourself

When should I use strict mode?

Use strict mode when:

• Your automation must send explicit values instead of relying on Multilogin defaults
• You want missing required fields reported in one validation response
• You need consistent request validation across automated workflows

How to use strict mode

In Postman, open “Headers” → add X-Strict-Mode as the key → enter true as the value. If you don’t specify this, the API will use the non-strict mode by default.