API call pattern?

Other Halo API Support
1

I’am trying to apply to get a higher API rate limit. And for one of the requirements to send in a email to 343, it says: API call pattern:

What does that mean?
I tried to google it, but cant find anything specific.

2

I’m not 100% sure either.

I just described some typical usage. For example; are you requesting games/events on client-demand or perhaps you’re scraping thousands of gamers service records at a time for database storage, etc.

3

I got asked about caching also.

4

They’re basically asking about your API call logic in your code. When I submitted my request, I basically laid out all the scenarios where I’d being hitting their servers. For example,

  1. On first launch/install of the app, four requests are made to seed meta data (CSR, Medals, Playlist, Weapons). Once the data is retrieved it is cached for reuse.
  2. Player added to app. Entering a player’s gamer tag makes a request to the Halo API service for the player’s arena stats data. If valid data is returned two additional calls are made; 1 for player portrait and 1 for their emblem.

Of course yours is probably different but you get what I’m saying…

5

Hey AudioSaturn2,

This is a really good question and I’m happy to clarify.
In general, and as mentioned in this thread, what we’re looking for in the call pattern is how you’re calling the APIs and how you’re caching your data.
Specifically, here’s some questions that we’re looking for answers for:

  • Which endpoints are you calling, how are you making the calls and how often? - Are you caching any data? Specifically, we recommend caching match and event details as well as metadata as those rarely change - How often do you refresh your cache? - Are you using any databases? What information are you storing there? - How are you securing your API key? If you’re building a mobile app, are you using a service to manage your API calls?
    Let us know if you have any additional questions