Skip to main content

FAQ: sign-in and limits

This is one text for all causes. What to check in the cabinet:
  1. the adapter account exists in the right system and is active;
  2. the login matches what the client sends: case does not matter, spaces do;
  3. the password has not been changed recently — the previous one stops working within a minute.
After a series of wrong passwords, sign-in is temporarily blocked: first for a minute, at most for 15 minutes. If everything is in order but the rejection persists, engineers will see the exact cause in the logs — they also show if adapter sign-in is not configured on the environment.
The limit is 66 requests per sliding minute per login and 112 per sender address. If all clients come through a single proxy that does not forward their addresses, the per-address limit becomes shared by everyone; engineers can see this in the logs.
This is replay protection: the same request body within 10 minutes gets the stored response. To add rows to the same campaign, the client must send a different body — different numbers or field values.
See also: Sign-in and limits.