Ghost/core/server/web/api
Fabien O'Carroll 2e922808e8 ♻ Updated naming for Content API specific middleware
no-issue

This is because the Content API will eventually be accessed not just
from Content API keys. The addition of a Content API specific
authorization middleware is because:
1. content api should not authorize based on req.user
2. content api will need separate authorization than admin api
2018-11-08 13:34:29 +07:00
..
v0.1 Optimised web/ debug logs 2018-10-04 17:43:08 +02:00
v2 ♻ Updated naming for Content API specific middleware 2018-11-08 13:34:29 +07:00
README.md Added v2 api endpoints (#9874) 2018-09-18 15:59:06 +02:00

Ghost APIs

Ghost is moving towards providing more robust APIs in the future. A plan and decisions can be found here.

WARNING!

The v2 API (/ghost/api/v2/* endpoints) is to be considered under active development until this message is removed. Please use with caution and don't rely too heavy on it just yet :)