ptero-notes
ptero-notes copied to clipboard
devnote-dev
Markdown files documenting Pterodactyl and Wings APIs & internals
With the new guidelines being merged, all of the documents for the Pterodactyl API (and a few of the Wings API documents) need updating to the specification: Application: - [x]...
A section (probably in the main README) defining the appropriate terminology for the Pterodactyl and Wings APIs, as well as clarifications for incorrect or misinterpreted terms.
Most of the endpoints for the application API has been covered with a few notable ones missing, like servers (for example). Ideally this should be covered entirely.
Full coverage of the client API is the goal here, there have been attempts [here](https://api.ptero.sh) and from [the original documentation](https://dashflo.net/docs/api/pterodactyl/v1/) but ideally this repo should have full coverage of all...
Having a detailed specification for JWT token generation and the usage in the different APIs (this is partially documented already via the claims sections). This is primarily for the Wings...
The panel has an interesting locales endpoint which returns an object containing the localization/translation strings for the frontend. It's currently only used for activity logs but I believe its usage...
Documentation should be provided for the `/auth` endpoints which are responsible for user authentication in the panel. It is not part of any specific API and is not classed as...
This is used in the application API documentation already, but having example JSON models for the applicable endpoints that can be used as references for people using the API, similarly...
Metadata
Owner
Metadata
Markdown files documenting Pterodactyl and Wings APIs & internals