> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hubtalk.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ: sign-in and limits

> Authentication failed on every request, Too many requests, a repeated request returns the same identifiers.

# FAQ: sign-in and limits

> [accordion] The client gets «Authentication failed» on every request
>
> 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.

> [accordion] «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.

> [accordion] 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.

See also: [Sign-in and limits](https://docs.hubtalk.ai/v4/compat-adapter/sign-in.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.