Response code 429 but no p-ticket or p-time

If we get a response code of 429 on a WebSocket connection, but it does not contain a p-ticket or p-time field, how can we know when the next request will be allowed?

I don’t use the API, but I would make sure that you are reusing the same connection and not creating a new one. If you are using only the one connection, then maybe something is causing the connection to close and the client might attempt to reconnect causing the issue.

Thank you, but I should have been more clear. I was intentionally causing the 429’s to make sure my code could handle the response – but the response was missing any p-ticket or p-time fields – so I was wondering if that is by design or if there is another way to know how long the API will lock you out in the scenario.