Swagger Documentation for /v1/contenttype Endpoints

[jdcmsd]

Task

Update Content Type REST API resource with Swagger documentation.

Proposed Objective

Documentation

Proposed Priority

Priority 2 - Show Stopper

Acceptance Criteria

Content Type REST API endpoints on the API Playground should contain all necessary information to comfortably begin to use them, including:

• Tags
• Descriptions
• Parameter details
• Request body explanations
• Sample values where appropriate
• Return schema

[jdcmsd]

Redone, new and improved! No refactoring, all swagger!

[gavriella-dotcms]

Looks good! All of the documentation is shown on my API playground.

[bryanboza]

Hey @jdcmsd , this looks better now. However, I have a question about the responses section. I'm not sure if we should list all the possible response codes handled by the endpoint or if it should just be a basic summary of the happy path. Should we include responses like 400 or 401 as well?

[bryanboza]

We can close this for now, a new discussion opened for the next L10 meeting