Skip to content

The following commit adds a comprehensive OpenAPI specification (open… #32841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jtviolet
Copy link

…api.yaml):

This commit introduces an OpenAPI 3.0.0 specification file (openapi.yaml) that documents the Discourse API.

The specification includes:

  • Paths and operations derived from core application routes and plugins (Automation, Chat, Narrative Bot, Styleguide).
  • Reusable schemas for common data structures (User, Post, Topic, Category, Group, etc.) in the components section.
  • API metadata including title, version, description, and contact information.
  • Definitions for request and response bodies, referencing the reusable schemas.
  • A global API key security scheme.

This initial version provides a broad overview of the API surface. Further refinements to request/response schema details and more specific security configurations can be made in subsequent iterations.

…api.yaml):

This commit introduces an OpenAPI 3.0.0 specification file (openapi.yaml) that documents the Discourse API.

The specification includes:
- Paths and operations derived from core application routes and plugins (Automation, Chat, Narrative Bot, Styleguide).
- Reusable schemas for common data structures (User, Post, Topic, Category, Group, etc.) in the components section.
- API metadata including title, version, description, and contact information.
- Definitions for request and response bodies, referencing the reusable schemas.
- A global API key security scheme.

This initial version provides a broad overview of the API surface. Further refinements to request/response schema details and more specific security configurations can be made in subsequent iterations.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Author

@jtviolet jtviolet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants