Admin apis

[cbrinicombe13]

No description provided.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
trophy	🟢 Ready	View Preview	Apr 21, 2026, 8:06 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[jasontlouro]

currently all admin APIs are limited to 10 req/sec not 100, including GETs, should I change that in the gateway so that GETs are 100 req/sec and the rest are 10 to match these docs?

[jasontlouro]

The order here is weird, both the high-level order (why metrics then attributes then streaks then points?) and the order of endpoints within a section (why are the post/patch/delete sandwiched between the two GETs?)

[cbrinicombe13]

The order here is weird, both the high-level order (why metrics then attributes then streaks then points?) and the order of endpoints within a section (why are the post/patch/delete sandwiched between the two GETs?)

Went in order of how things are shown in the rest of the docs, generally low level concepts first then composed things like points/leaderboards that use the other concepts later:

What order do you think is best?

I can make the get endpoints first in each section if you think that's better?

[jasontlouro]

I think for the endpoints what makes sense is GETs then PATCH then POST then DELETE but idk if there is a standard order that we should follow

Regarding the high-level concepts I guess that makes sense, I think I was expecting alphabetical but just checked Knock and Stripe and neither do alphabetical so I guess whatever order feels right works haha

[cbrinicombe13]

currently all admin APIs are limited to 10 req/sec not 100, including GETs, should I change that in the gateway so that GETs are 100 req/sec and the rest are 10 to match these docs?

It's fine i'll keep everything admin as tier 1