Does LeetCode's GraphQL endpoint apply different throttling to mutations when using a test‑generated token versus a production token?

Answer

There is no public evidence that LeetCode’s GraphQL endpoint applies a different mutation throttling policy to test‑generated tokens compared to production tokens. Both token types authenticate against the same service layer, and the rate‑limit is enforced per account/IP rather than per token provenance.

Likely Explanation

LeetCode’s undocumented GraphQL API is a shared endpoint. Rate limits are typically implemented as a global quota (e.g., X requests per minute) that is applied to the authenticated user or the originating IP address. Test tokens are issued for debugging or educational use but still tie to a real user account, so they inherit the same quota. If you observe a higher error rate for one token, it is more likely due to account‑level restrictions (such as a free vs. paid plan) than the token type itself.

How to Verify the Limits

1. Choose a simple mutation that is safe to repeat (e.g., submitting a solution or updating a profile field).
2. Generate two sets of headers:

   Authorization: Bearer <test-token>
   Authorization: Bearer <prod-token>

3. Send a burst of identical requests from each token, incrementing the rate until you receive a throttling response (commonly HTTP 429 or a custom error message such as “Rate limit exceeded”).

   curl -X POST https://leetcode.com/graphql \
        -H "Content-Type: application/json" \
        -H "Authorization: Bearer <token>" \
        -d '{ "query": "mutation { submitSolution(...) { success } }" }'

4. Record the request count at which the error occurs for each token.
5. Compare the thresholds. If they match, the throttling policy is identical. If one token hits the limit earlier, that indicates a difference.
6. Optionally, inspect the X-RateLimit-Remaining header (if present) to see per‑token remaining quota during the test.

Missing Diagnostic Detail

To refine this recommendation, please let us know whether the test and production tokens belong to the same user account or to distinct accounts. Account‑level settings (e.g., a free vs. paid subscription) can influence the effective rate limit even if the token type is identical.