BakApiTokenRequest

Refreshes the key for Ankama's in-client shop back end. Carries nothing.

THE TRIGGER IS TOKEN LIFECYCLE, NEVER USER ACTION, and the client's state machine has three parts worth reproducing:

in-flight latch    one request at a time. The send routine sets a latch and
                   will not send a second while one is outstanding.
5,000 ms retry     when it cannot send yet - the connection is not up - it
                   re-arms on a 5 second delay and tries again. A real
                   repeating cadence during bring-up.
3,600,000 ms       after a successful answer, EXACTLY ONE HOUR before the
                   next refresh. A long session re-sends this hourly,
                   indefinitely.

Both constants are read straight out of the client, one in the send routine and one in the receive routine.

IT APPEARS DURING BRING-UP ALONGSIDE THE SOCIAL BURST, AND IT IS NOT PART OF IT. A capture shows it in the same handful of milliseconds as ContextCreationRequest and the four-request burst described under FriendListRequest - but it comes from a different service on a different trigger. Do not fold it into that sequence.

Nothing in gameplay depends on having the key.