Sometimes 429 (too many requests)

[jhonatasrm]

Description

429 - too many requests

Steps to Reproduce

1. In about:debugging#/runtime/this-firefox add the SUMO Live Helper on Load Temporary Add-on...
2. Open Inspect
3. See the console behavior when selecting locales and products

Expected behavior:

Optimize API requests by refraining from calling the API each time a product is selected, which results in multiple API calls. Instead, utilize a single call to retrieve product information. For example:

https://support.mozilla.org/api/2/question/?format=json&ordering=-id&is_solved=false&is_spam=false&is_locked=false&products=ios,firefox,thunderbird&is_taken=false&is_archived=false&locale=pt-BR&num_answers=0

Actual behavior:

The API is being called repeatedly for each selected product/locale.

System information

• Operating system: Windows 11 Pro
• Firefox version: 124.0.2 (64-bit)

Additional Information

Documentation to reference: https://mozilla.github.io/kitsune/api/#optional-arguments

[WesleyBranton]

If we do this (which sounds like a good idea) this would impose a 20 question limit overall because that's all the API returns. (See #154)

We definitely need a way to get multiple pages of results if we implement this ticket.

[dannycolin]

@WesleyBranton would you be open to have a broader discussion on refactoring the API? I was also thinking about refactoring our API implementation so we can support more features. Handling multiple pages of results is definitely on the list.

Plus, I wanted a better solution to track the "new" question status. For example, we could keep track of the last update and only fetch from that point when we use the polling mechanism. For older content, we could lazy pull it when needed (e.g. scrolling the list in the popup).

[WesleyBranton]

It makes sense to try and cover multiple issues if we need to refactor the API. Unfortunately, my schedule is too busy to do any actual coding for these changes though.