Home/ Questions/Q 8791351
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T22:49:50+00:00

This is a somewhat simple question, but sadly I have not been able to

  • 0

This is a somewhat simple question, but sadly I have not been able to find a concrete answer thus far.

We are constructing an API (we’re not in production yet) which returns a large amount of data after user authentication, etc. The API system tracks the user’s usage on a per second and per hour basis. When the user exceeds either of those limitations, the server returns no content and some http error code.

Presently, I’m using 406 Not Acceptable, but I don’t believe that’s the best code to use. Its been suggested that 509 Bandwidth Limit Exceeded would be a good one, but I wonder if there is a code which would be considered best practice for my situation. Thank you in advance for your help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Status code 429 comes to mind:

    RFC 6585, section 4: 429 Too Many Requests

    The 429 status code indicates that the user has sent too many
    requests in a given amount of time ("rate limiting").

    The response representations SHOULD include details explaining the
    condition, and MAY include a Retry-After header indicating how long
    to wait before making a new request.

    • 0