customer links signed with a new key
the telegram_url returned for each child address and the url from GET /v1/alerts/telegram/customer-link carry a signature. that signature now uses a new key. a link you fetch from the api today is already the new one; nothing changes in how you call the api or in what your customer sees.
links generated before october 22 keep opening until november 22. after that date the old signature is no longer accepted and the customer sees the usual "this link is not valid" reply from the bot.
if your system caches these links, fetch them again before then: list your children with GET /v1/hotwallets/{network}/children or call customer-link again for each external_ref. customers who already pressed start keep receiving alerts and need nothing. details in the api reference.
fixes and improvements
- terms of use updated for the b2b api: transactional use, fees per network, support. the panel asks each account to read and accept them.