Rest API - Error Handling
You want to design a REST API rate limit error response that clearly informs clients about the wait time and reason. Which of the following is the best practice?
You want to design a REST API rate limit error response that clearly informs clients about the wait time and reason. Which of the following is the best practice?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Choose correct status code for rate limiting
Status 429 is the standard code for rate limit errors, signaling client to slow down.Step 2: Include Retry-After header and clear message
Retry-After header tells client how long to wait. JSON message improves clarity and user experience.Step 3: Evaluate other options
403 is forbidden, not rate limit. 200 means success, which is misleading. 500 is server error, not client rate limit.Final Answer:
Return status 429 with a Retry-After header and a JSON message explaining the limit -> Option CQuick Check:
429 + Retry-After + clear message = best practice [OK]
Quick Trick: Use 429 + Retry-After + clear JSON message for best rate limit response [OK]
Common Mistakes:
- Using wrong status codes like 403 or 500
- Returning 200 status for errors
- Omitting Retry-After header
Master "Error Handling" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes