Hey everyone 
First off, I must say its awesome to see the developers amongst the Halo community getting creative with the API, can’t wait to see what we produce collectively.
This may be an odd question but I’m not sure why we get a secondary API access key? Perhaps a fallback if a primary access key hits the rate limit?
I just did a quick test, both the primary key and secondary key contribute to the same rate limit. If you go over your rate with the primary key, the secondary key will be no good either.
It might be just so you can give the secondary key to someone else for testing (and later to revoke) without interrupting the primary key.
I couldn’t see any analytics that separate primary from secondary, so I wouldn’t think they are meant for different areas of the same app etc.
> 2753093343646559;2:
> It might be just so you can give the secondary key to someone else for testing (and later to revoke) without interrupting the primary key.
This. Also if you have more than one development project and you want to revoke one without interfering the others, you can just hot-swap out the keys and revoke one.
At least I assumed that was the reason…
Ah ok, that makes sense. Thanks for clarifying furiousn00b & der flatulator6