API Reference

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.


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 CodeNameDescription
200OKRequest fulfilled
201CreatedNew resource created
400Bad RequestRequest not understood
401UnauthorizedInvalid API token
403ForbiddenRequest not allowed
404Not FoundResource unavailable
405Method Not AllowedIncorrect request method
410GoneOld resource permanently unavailable
415Unsupported Media TypeFeature is not enabled
429Too Many RequestsRate limit has been exceeded
500Internal Server ErrorGeneric 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!