API Reference
The Full Stack Developer API is organized around REST. The API has predictable resource-oriented URLs, returns JSON-encoded responses, and uses standard HTTP response codes and verbs.
Caching
The API utilizes Cache-First approach. In this approach, when a user requests data from the server, the server first checks if the requested data is available in the cache. If the data is available in the cache, the server returns it immediately to the user without making any additional requests to the database.
HTTP status codes
Here's a list of the status codes used in the API:
| Status Code | Name | Description |
|---|---|---|
| 200 | OK | Request fulfilled |
| 201 | Created | New resource created |
| 400 | Bad Request | Request not understood |
| 401 | Unauthorized | Invalid API token |
| 403 | Forbidden | Request not allowed |
| 404 | Not Found | Resource unavailable |
| 405 | Method Not Allowed | Incorrect request method |
| 410 | Gone | Old resource permanently unavailable |
| 415 | Unsupported Media Type | Feature is not enabled |
| 429 | Too Many Requests | Rate limit has been exceeded |
| 500 | Internal Server Error | Generic server error |
Did we miss something?
Do you have a particular request you’d like to see added to the API? Please let us know!