FAQ: sign-in and limits
The client gets «Authentication failed» on every request
The client gets «Authentication failed» on every request
This is one text for all causes. What to check in the cabinet:
- the adapter account exists in the right system and is active;
- the login matches what the client sends: case does not matter, spaces do;
- the password has not been changed recently — the previous one stops working within a minute.
«Too many requests, try again later»
«Too many requests, try again later»
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.
The client repeated a request and got the same response with the same identifiers; no rows were added
The client repeated a request and got the same response with the same identifiers; no rows were added
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.