[{
"name": "APIs.json Agent Agents Md Info",
"slug": "apis-json-agent-agents-md-info",
"description": "APIs should link an agents.md file so AI agents have documented instructions and conventions for working with the API. Declaring a property of type AgentsMd in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should link an agents.md file so AI agents have documented instructions and conventions for working with the API. Declaring a property of type AgentsMd in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Agents",
"image": "",
"tags": ["APIs.json","Agents","Default"]
},{
"name": "APIs.json Agent LLMs Txt Info",
"slug": "apis-json-agent-llms-txt-info",
"description": "APIs should link an llms.txt file so AI agents have a curated, machine-readable entry point describing the API and how to work with it. Declaring a property of type LLMsTxt in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should link an llms.txt file so AI agents have a curated, machine-readable entry point describing the API and how to work with it. Declaring a property of type LLMsTxt in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Agents",
"image": "",
"tags": ["APIs.json","Agents","Default"]
},{
"name": "APIs.json APIs AID Error",
"slug": "apis-json-apis-aid-error",
"description": "Every API should have a unique identifier, known as an AID (API Identifier). The APIs.json file, contract, or collection contains its own AID, which the API uses as part of its reference. Additionally, the API applies a slugified version of its name, resulting in a unique, human-readable identifier for the API.",
"scope": "",
"property": "",
"type": "Every API should have a unique identifier, known as an AID (API Identifier). The APIs.json file, contract, or collection contains its own AID, which the API uses as part of its reference. Additionally, the API applies a slugified version of its name, resulting in a unique, human-readable identifier for the API.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Identifiers"]
},{
"name": "APIs.json APIs AID Info",
"slug": "apis-json-apis-aid-info",
"description": "Every API should have a unique identifier, known as an AID (API Identifier). The APIs.json file, contract, or collection contains its own AID, which the API uses as part of its reference. Additionally, the API applies a slugified version of its name, resulting in a unique, human-readable identifier for the API.",
"scope": "",
"property": "",
"type": "Every API should have a unique identifier, known as an AID (API Identifier). The APIs.json file, contract, or collection contains its own AID, which the API uses as part of its reference. Additionally, the API applies a slugified version of its name, resulting in a unique, human-readable identifier for the API.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Identifiers"]
},{
"name": "APIs.json Apis Base URL Error",
"slug": "apis-json-apis-baseURL-error",
"description": "Each API defined within an APIs.json artifact can specify the base URL for the API. This URL serves as a reference point for developers during onboarding and when making API calls. Additionally, it helps identify the API and validate the domain it is associated with.",
"scope": "",
"property": "",
"type": "Each API defined within an APIs.json artifact can specify the base URL for the API. This URL serves as a reference point for developers during onboarding and when making API calls. Additionally, it helps identify the API and validate the domain it is associated with.",
"guidance": "APIs Base URL",
"image": "",
"tags": ["APIs.json","APIs","Metadata","URLs"]
},{
"name": "APIs.json Apis BaseURL Info",
"slug": "apis-json-apis-baseURL-info",
"description": "Each API defined within an APIs.json artifact can specify the base URL for the API. This URL serves as a reference point for developers during onboarding and when making API calls. Additionally, it helps identify the API and validate the domain it is associated with.",
"scope": "",
"property": "",
"type": "Each API defined within an APIs.json artifact can specify the base URL for the API. This URL serves as a reference point for developers during onboarding and when making API calls. Additionally, it helps identify the API and validate the domain it is associated with.",
"guidance": "APIs Base URL",
"image": "",
"tags": ["APIs.json","APIs","Metadata","URLs"]
},{
"name": "APIs.json Apis Contact Email Error",
"slug": "apis-json-apis-contact-email-error",
"description": "The contact object in an APIs.json file allows for referencing the email address of a person or group. This property provides a convenient way for users to seek support for an API, using email as the default method to reach the team managing the API in production.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file allows for referencing the email address of a person or group. This property provides a convenient way for users to seek support for an API, using email as the default method to reach the team managing the API in production.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Contacts"]
},{
"name": "APIs.json Apis Contact Email Info",
"slug": "apis-json-apis-contact-email-info",
"description": "The contact object in an APIs.json file allows for referencing the email address of a person or group. This property provides a convenient way for users to seek support for an API, using email as the default method to reach the team managing the API in production.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file allows for referencing the email address of a person or group. This property provides a convenient way for users to seek support for an API, using email as the default method to reach the team managing the API in production.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Contacts"]
},{
"name": "APIs.json Apis Contact Error",
"slug": "apis-json-apis-contact-error",
"description": "The contact object in an APIs.json file allows for associating a vCard that represents an individual or organizational entity. It includes common contact information such as a name, email, or other references, offering a standardized method for providing support for an API.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file allows for associating a vCard that represents an individual or organizational entity. It includes common contact information such as a name, email, or other references, offering a standardized method for providing support for an API.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Contacts"]
},{
"name": "APIs.json Apis Contact Fn Error",
"slug": "apis-json-apis-contact-fn-error",
"description": "The contact object in an APIs.json file includes a full name (FN) property, which specifies the formatted text corresponding to the contact name in the vCard for an API. This provides a quick and clear way to assign a person, group, or other point of contact to an API for addressing questions and providing support.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file includes a full name (FN) property, which specifies the formatted text corresponding to the contact name in the vCard for an API. This provides a quick and clear way to assign a person, group, or other point of contact to an API for addressing questions and providing support.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Contacts"]
},{
"name": "APIs.json Apis Contact Fn Info",
"slug": "apis-json-apis-contact-fn-info",
"description": "The contact object in an APIs.json file includes a full name (FN) property, which specifies the formatted text corresponding to the contact name in the vCard for an API. This provides a quick and clear way to assign a person, group, or other point of contact to an API for addressing questions and providing support.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file includes a full name (FN) property, which specifies the formatted text corresponding to the contact name in the vCard for an API. This provides a quick and clear way to assign a person, group, or other point of contact to an API for addressing questions and providing support.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","APIs","Metadata","Contacts"]
},{
"name": "APIs.json APIs Contact Info",
"slug": "apis-json-apis-contact-info",
"description": "The contact object in an APIs.json file allows for associating a vCard that represents an individual or organizational entity. It includes common contact information such as a name, email, or other references, offering a standardized method for providing support for an API.",
"scope": "",
"property": "",
"type": "The contact object in an APIs.json file allows for associating a vCard that represents an individual or organizational entity. It includes common contact information such as a name, email, or other references, offering a standardized method for providing support for an API.",
"guidance": "APIs Contact",
"image": "",
"tags": ["APIs.json","Metadata","Contacts","APIs"]
},{
"name": "APIs.json APIs Description Info",
"slug": "apis-json-apis-description-info",
"description": "Each API included in an APIs.json file should have a 1-3 paragraph description. This description serves as the first impression for potential consumers and is often displayed in portals, networks, search results, and other discovery channels. A well-crafted description plays a key role in helping API consumers understand and onboard with the API effectively.",
"scope": "",
"property": "",
"type": "Each API included in an APIs.json file should have a 1-3 paragraph description. This description serves as the first impression for potential consumers and is often displayed in portals, networks, search results, and other discovery channels. A well-crafted description plays a key role in helping API consumers understand and onboard with the API effectively.",
"guidance": "APIs Descriptions",
"image": "",
"tags": ["APIs.json","Metadata","APIs"]
},{
"name": "APIs.json APIs Human URL Info",
"slug": "apis-json-apis-humanURL-info",
"description": "The humanURL property for each API defined in an APIs.json contract provides a link for business or technical consumers to learn more about the API. This URL can direct users to a portal, documentation, or ideally, a dedicated landing page designed specifically to onboard consumers with a single API.",
"scope": "",
"property": "",
"type": "The humanURL property for each API defined in an APIs.json contract provides a link for business or technical consumers to learn more about the API. This URL can direct users to a portal, documentation, or ideally, a dedicated landing page designed specifically to onboard consumers with a single API.",
"guidance": "APIs Human URL",
"image": "",
"tags": ["APIs.json","Metadata","APIs","URLs"]
},{
"name": "APIs.json Apis Image Info",
"slug": "apis-json-apis-image-info",
"description": "Each API defined within an APIs.json file can include a dedicated image, offering a visual representation of the resource or capability it provides. This enhances the API's approachability and visual appeal in portals, documentation, catalogs, and marketplaces, making it more engaging for potential users.",
"scope": "",
"property": "",
"type": "Each API defined within an APIs.json file can include a dedicated image, offering a visual representation of the resource or capability it provides. This enhances the API's approachability and visual appeal in portals, documentation, catalogs, and marketplaces, making it more engaging for potential users.",
"guidance": "APIs Images",
"image": "",
"tags": ["APIs.json","APIs","Metadata"]
},{
"name": "APIs.json APIs Info",
"slug": "apis-json-apis-info",
"description": "The APIs property in an APIs.json file enables the definition of one or more APIs as part of a larger collection. Each API within this property has its own subset of metadata, allowing it to be uniquely identified and distinguished from the rest of the collection. This individual metadata contributes to the overall value and functionality of the API collection.",
"scope": "",
"property": "",
"type": "The APIs property in an APIs.json file enables the definition of one or more APIs as part of a larger collection. Each API within this property has its own subset of metadata, allowing it to be uniquely identified and distinguished from the rest of the collection. This individual metadata contributes to the overall value and functionality of the API collection.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","Metadata","Info","APIs"]
},{
"name": "APIs.json APIs Name Info",
"slug": "apis-json-apis-name-info",
"description": "Each individual API in an APIs.json collection has its own name property, allowing for a clear description of the API. This name might match the API's title in the OpenAPI Info section, but it could also represent the API's business purpose, as displayed in catalogs and search results.",
"scope": "",
"property": "",
"type": "Each individual API in an APIs.json collection has its own name property, allowing for a clear description of the API. This name might match the API's title in the OpenAPI Info section, but it could also represent the API's business purpose, as displayed in catalogs and search results.",
"guidance": "APIs Names",
"image": "",
"tags": ["APIs.json","Metadata","APIs"]
},{
"name": "APIs.json Apis Properties About Info",
"slug": "apis-json-apis-properties-about-info",
"description": "This property ensures provides a reference to an about page, either for the company, organization, or government agency behind an API, or specifically about the domain, team, and the APIs they produce",
"scope": "",
"property": "",
"type": "This property ensures provides a reference to an about page, either for the company, organization, or government agency behind an API, or specifically about the domain, team, and the APIs they produce",
"guidance": "APIs Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Business Impact Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-business-impact-canvas-info",
"description": "This ensures that an API has had the [APIOps Business Impact Canvas](https://www.apiopscycles.com/resources/business-impact-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Business Impact Canvas](https://www.apiopscycles.com/resources/business-impact-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Business Model Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-business-model-canvas-info",
"description": "This ensures that an API has had the [APIOps Business Model Canvas](https://www.apiopscycles.com/resources/api-business-model-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Business Model Canvas](https://www.apiopscycles.com/resources/api-business-model-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Capacity Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-capacity-canvas-info",
"description": "This ensures that an API has had the [APIOps Capacity Canvas](https://www.apiopscycles.com/resources/capacity-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Capacity Canvas](https://www.apiopscycles.com/resources/capacity-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Customer Journey Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-customer-journey-canvas-info",
"description": "This ensures that an API has had the [APIOps Customer Journey Canvas](https://www.apiopscycles.com/resources/customer-journey-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Customer Journey Canvas](https://www.apiopscycles.com/resources/customer-journey-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Domain Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-domain-canvas-info",
"description": "This ensures that an API has had the [APIOps Domain Canvas](https://www.apiopscycles.com/resources/domain-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Domain Canvas](https://www.apiopscycles.com/resources/domain-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Event Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-event-canvas-info",
"description": "This ensures that an API has had the [APIOps Event Canvas](https://www.apiopscycles.com/resources/event-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Event Canvas](https://www.apiopscycles.com/resources/event-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Interaction Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-interaction-canvas-info",
"description": "This ensures that an API has had the [APIOps Interaction Canvas](https://www.apiopscycles.com/resources/interaction-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Interaction Canvas](https://www.apiopscycles.com/resources/interaction-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Locations Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-locations-canvas-info",
"description": "This ensures that an API has had the [APIOps Locations Canvas](https://www.apiopscycles.com/resources/locations-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Locations Canvas](https://www.apiopscycles.com/resources/locations-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Locations Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-rest-canvas-info",
"description": "This ensures that an API has had the [APIOps Locations Canvas](https://www.apiopscycles.com/resources/rest-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Locations Canvas](https://www.apiopscycles.com/resources/rest-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties APIOps Cycles Value Proposition Canvas",
"slug": "apis-json-apis-properties-apiop-cycles-value-proposition-canvas-info",
"description": "This ensures that an API has had the [APIOps Value Proposition Canvas](https://www.apiopscycles.com/resources/api-value-proposition-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"scope": "",
"property": "",
"type": "This ensures that an API has had the [APIOps Value Proposition Canvas](https://www.apiopscycles.com/resources/api-value-proposition-canvas) applied to the API, requiring that the canvas is present in the repository and registered in the APIs.json index for the API, helping with discovery and governance.",
"guidance": "APIs Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties","APIOps Cycles"]
},{
"name": "APIs.json Apis Properties Apis Json Rules Info",
"slug": "apis-json-apis-properties-apis-json-rules-info",
"description": "This property ensures that an API has operational level rules for APIs",
"scope": "",
"property": "",
"type": "This property ensures that an API has operational level rules for APIs",
"guidance": "API Governance Rules",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Apis Json Validator Info",
"slug": "apis-json-apis-properties-apis-json-validator-info",
"description": "This property ensures that there is a link to the validator for the APIs",
"scope": "",
"property": "",
"type": "This property ensures that there is a link to the validator for the APIs",
"guidance": "API Validator",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Authentication Info",
"slug": "apis-json-apis-properties-authentication-info",
"description": "This property ensures that there is a human readable authentication page available that will provide what type of authentication is used and how it can be applied, as well as any services or tooling that API consumers can use to troubleshoot authentication with APIs",
"scope": "",
"property": "",
"type": "This property ensures that there is a human readable authentication page available that will provide what type of authentication is used and how it can be applied, as well as any services or tooling that API consumers can use to troubleshoot authentication with APIs",
"guidance": "Authentication",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Blog Feed Info",
"slug": "apis-json-apis-properties-blog-feed-info",
"description": "This property ensures that blogs in support of APIs have an Atom or RSS feed of posts, allowing for the syndication of updates and information around individual APIs and the operations around them",
"scope": "",
"property": "",
"type": "This property ensures that blogs in support of APIs have an Atom or RSS feed of posts, allowing for the syndication of updates and information around individual APIs and the operations around them",
"guidance": "Communication",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Blog Info",
"slug": "apis-json-apis-properties-blog-info",
"description": "This property ensures that an API has a reference to a blog where anyone can find updates and other stories that will help keep API consumers and other stakeholders up to speed on what is happening with an API, and the larger operations",
"scope": "",
"property": "",
"type": "This property ensures that an API has a reference to a blog where anyone can find updates and other stories that will help keep API consumers and other stakeholders up to speed on what is happening with an API, and the larger operations",
"guidance": "Communication",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Change Log Info",
"slug": "apis-json-apis-properties-change-log-info",
"description": "This property ensures that than an individual API or API operations possesses a change log that catalogs all the changes that have occurred in a recent time frame, with historical and version information available if possible",
"scope": "",
"property": "",
"type": "This property ensures that than an individual API or API operations possesses a change log that catalogs all the changes that have occurred in a recent time frame, with historical and version information available if possible",
"guidance": "Change Management",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Compare Info",
"slug": "apis-json-apis-properties-compare-info",
"description": "This property ensures that an API has the ability to compare two different versions of an API and see what the difference are between them",
"scope": "",
"property": "",
"type": "This property ensures that an API has the ability to compare two different versions of an API and see what the difference are between them",
"guidance": "APIs Comparison",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Deprecation Policy Info",
"slug": "apis-json-apis-properties-deprecation-policy-info",
"description": "This property ensures that an API has a deprecation policy shared as part of the contract, communicating what the lifespan of APIs are, each individual version, as well as communication around the deprecation of APIs",
"scope": "",
"property": "",
"type": "This property ensures that an API has a deprecation policy shared as part of the contract, communicating what the lifespan of APIs are, each individual version, as well as communication around the deprecation of APIs",
"guidance": "Deprecation",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Documentation Info",
"slug": "apis-json-apis-properties-documentation-info",
"description": "This property ensures that there is documentation published for an API, and API consumers will have a set of human-readable instructions for onboarding and integrating with HTTP APIs in their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is documentation published for an API, and API consumers will have a set of human-readable instructions for onboarding and integrating with HTTP APIs in their applications",
"guidance": "Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Environments Production Info",
"slug": "apis-json-apis-properties-environments-production-info",
"description": "This property ensures that there is a production environment available for an API, providing base URL, tokens, keys, and other key / value pairs that are needed to integrate with an API",
"scope": "",
"property": "",
"type": "This property ensures that there is a production environment available for an API, providing base URL, tokens, keys, and other key / value pairs that are needed to integrate with an API",
"guidance": "Environments",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Environments Staging Info",
"slug": "apis-json-apis-properties-environments-staging-info",
"description": "This property ensures that there is a staging environment available for an API, providing base URL, tokens, keys, and other key / value pairs that are needed to integrate with an API",
"scope": "",
"property": "",
"type": "This property ensures that there is a staging environment available for an API, providing base URL, tokens, keys, and other key / value pairs that are needed to integrate with an API",
"guidance": "Environments",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json API Properties Examples Info",
"slug": "apis-json-apis-properties-examples-info",
"description": "This property ensures that an API has a reference to a examples for individual APIs or as part of common properties, providing examples and synthentic data that can be used for APIs.",
"scope": "",
"property": "",
"type": "This property ensures that an API has a reference to a examples for individual APIs or as part of common properties, providing examples and synthentic data that can be used for APIs.",
"guidance": "Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties","Sandbox","Examples"]
},{
"name": "APIs.json Apis Properties Feedback Email Info",
"slug": "apis-json-apis-properties-feedback-email-info",
"description": "This property ensures that there is an email available for API consumers to provide feedback",
"scope": "",
"property": "",
"type": "This property ensures that there is an email available for API consumers to provide feedback",
"guidance": "Feedback",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Feedback Issues Info",
"slug": "apis-json-apis-properties-feedback-issues-info",
"description": "This property ensures there is a URL to Git issues specifically for providing feedback",
"scope": "",
"property": "",
"type": "This property ensures there is a URL to Git issues specifically for providing feedback",
"guidance": "Feedback",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Forum Info",
"slug": "apis-json-apis-properties-forum-info",
"description": "This property ensures that there is a link to a discussion forum, providing a way for consumers and producers to engage and support either other throughout the lifecycle",
"scope": "",
"property": "",
"type": "This property ensures that there is a link to a discussion forum, providing a way for consumers and producers to engage and support either other throughout the lifecycle",
"guidance": "Support",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Gateway Info",
"slug": "apis-json-apis-properties-gateway-info",
"description": "This property ensures that there is a reference to the gateway for an API, referencing where you can manage the configuration for each API",
"scope": "",
"property": "",
"type": "This property ensures that there is a reference to the gateway for an API, referencing where you can manage the configuration for each API",
"guidance": "Gateways",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Getting Started Info",
"slug": "apis-json-apis-properties-getting-started-info",
"description": "This property ensures that there is a getting started link available, providing a reference for API consumers to get started with an API is as few steps as possible",
"scope": "",
"property": "",
"type": "This property ensures that there is a getting started link available, providing a reference for API consumers to get started with an API is as few steps as possible",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Github Action Info",
"slug": "apis-json-apis-properties-github-action-info",
"description": "This property ensures that a GitHub Actions CI/CD pipeline is available for an API, providing a link to the pipeline YAML artifact, which can be used to automate and govern the API as part of the build process",
"scope": "",
"property": "",
"type": "This property ensures that a GitHub Actions CI/CD pipeline is available for an API, providing a link to the pipeline YAML artifact, which can be used to automate and govern the API as part of the build process",
"guidance": "Pipelines",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Github Organization Info",
"slug": "apis-json-apis-properties-github-organization-info",
"description": "This property ensures that an API is associated with GitHub organization, providing the URL to where you can engage with the operations surrounding an API",
"scope": "",
"property": "",
"type": "This property ensures that an API is associated with GitHub organization, providing the URL to where you can engage with the operations surrounding an API",
"guidance": "Workspaces",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Github Repository Info",
"slug": "apis-json-apis-properties-github-repository-info",
"description": "This property ensures that an API possess a reference to a dedicated GitHub repository that is used to manage the Open, but also possible server and client code",
"scope": "",
"property": "",
"type": "This property ensures that an API possess a reference to a dedicated GitHub repository that is used to manage the Open, but also possible server and client code",
"guidance": "Repositories",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json APIs Properties Info",
"slug": "apis-json-apis-properties-about-info",
"description": "Each individual API included in an APIs.json file can have a properties collection, which contains specific properties relevant to that API. These properties often start with human-readable elements, such as documentation links, and can also include machine-readable properties to enhance functionality and integration.",
"scope": "",
"property": "",
"type": "Each individual API included in an APIs.json file can have a properties collection, which contains specific properties relevant to that API. These properties often start with human-readable elements, such as documentation links, and can also include machine-readable properties to enhance functionality and integration.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Metadata"]
},{
"name": "APIs.json Apis Properties Insomnia Collection Info",
"slug": "apis-json-apis-properties-insomnia-collection-info",
"description": "This property defines an Insomnia collection available for each API, providing executable artifacts that can be used in the Insomnia client for making calls, and executing automation workflows",
"scope": "",
"property": "",
"type": "This property defines an Insomnia collection available for each API, providing executable artifacts that can be used in the Insomnia client for making calls, and executing automation workflows",
"guidance": "Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties License Info",
"slug": "apis-json-apis-properties-license-info",
"description": "This property ensures that an API Commons interface license exists for an API, providing a machine-readable reference for an API, as well as data, backend, and front-end code",
"scope": "",
"property": "",
"type": "This property ensures that an API Commons interface license exists for an API, providing a machine-readable reference for an API, as well as data, backend, and front-end code",
"guidance": "Legal",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Lifecycle Info",
"slug": "apis-json-apis-properties-lifecycle-info",
"description": "This property makes sure there is an API lifecycle schema defining all of the stages of a lifecycle and which policies get applied at each stage of the API lifecycle",
"scope": "",
"property": "",
"type": "This property makes sure there is an API lifecycle schema defining all of the stages of a lifecycle and which policies get applied at each stage of the API lifecycle",
"guidance": "Lifecycle",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json API Properties Mock Server Info",
"slug": "apis-json-apis-properties-mock-server-info",
"description": "This property ensures that an API has a reference to a mock servers for individual APIs or as part of common properties, providing mocked deployments of an API that can be used for making test API calls.",
"scope": "",
"property": "",
"type": "This property ensures that an API has a reference to a mock servers for individual APIs or as part of common properties, providing mocked deployments of an API that can be used for making test API calls.",
"guidance": "Virtualization",
"image": "",
"tags": ["APIs.json","APIs","Properties","Sandbox","Mock Servers"]
},{
"name": "APIs.json Apis Properties OpenAPI Info",
"slug": "apis-json-apis-properties-openapi-info",
"description": "This property ensures that there is an OpenAPI present for an API, providing the technical contract that describes the surface area of an API",
"scope": "",
"property": "",
"type": "This property ensures that there is an OpenAPI present for an API, providing the technical contract that describes the surface area of an API",
"guidance": "OpenAPI",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties OpenAPI Rules Info",
"slug": "apis-json-apis-properties-openapi-rules-info",
"description": "This property ensures that an OpenAPI has support governance rules, that can be applied during design time via editors, development time via IDE, and run-time via CI/CD pipelines",
"scope": "",
"property": "",
"type": "This property ensures that an OpenAPI has support governance rules, that can be applied during design time via editors, development time via IDE, and run-time via CI/CD pipelines",
"guidance": "OpenAPI",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties OpenAPI Validator Info",
"slug": "apis-json-apis-properties-openapi-validator-info",
"description": "This property ensures that there is a link to the validator for the OpenAPI technical contract, allowing anyone to see the details of governance being applied",
"scope": "",
"property": "",
"type": "This property ensures that there is a link to the validator for the OpenAPI technical contract, allowing anyone to see the details of governance being applied",
"guidance": "OpenAPI",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Performance Info",
"slug": "apis-json-apis-properties-performance-info",
"description": "This property ensures that an API has performance testing in place, providing a URL to the performance testing, dashboard, or other resource",
"scope": "",
"property": "",
"type": "This property ensures that an API has performance testing in place, providing a URL to the performance testing, dashboard, or other resource",
"guidance": "Monitoring",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Plans Info",
"slug": "apis-json-apis-properties-plans-info",
"description": "This property provides a link to the dedicated plans page that applies to an API, providing information about access tiers, rate limits, and features available for an API as part of a wider API business plan",
"scope": "",
"property": "",
"type": "This property provides a link to the dedicated plans page that applies to an API, providing information about access tiers, rate limits, and features available for an API as part of a wider API business plan",
"guidance": "Plans",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Policies Info",
"slug": "apis-json-apis-properties-policies-info",
"description": "This property ensures there is a governance policies reference as part of an API contract, usually a common property pointing to a centralized set of policies that get applied",
"scope": "",
"property": "",
"type": "This property ensures there is a governance policies reference as part of an API contract, usually a common property pointing to a centralized set of policies that get applied",
"guidance": "Policies",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Portal Info",
"slug": "apis-json-apis-properties-portal-info",
"description": "This property ensures there a developer portal associated with an API and that you can find a landing page for the API, documentation, SDKs, and other resources",
"scope": "",
"property": "",
"type": "This property ensures there a developer portal associated with an API and that you can find a landing page for the API, documentation, SDKs, and other resources",
"guidance": "Portals",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Postman Collection Info",
"slug": "apis-json-apis-properties-postman-collection-info",
"description": "This property ensures that an API has at least one Postman Collection associated with it, providing automation, tests, and other executable derivatives of an APIs OpenAPI",
"scope": "",
"property": "",
"type": "This property ensures that an API has at least one Postman Collection associated with it, providing automation, tests, and other executable derivatives of an APIs OpenAPI",
"guidance": "Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Postman Public Workspace Info",
"slug": "apis-json-apis-properties-postman-public-workspace-info",
"description": "This property ensures that an API is associated with a Postman Workspace, providing a single location that API producers and/or API consumers can engage around an API",
"scope": "",
"property": "",
"type": "This property ensures that an API is associated with a Postman Workspace, providing a single location that API producers and/or API consumers can engage around an API",
"guidance": "Documentation",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Pricing Info",
"slug": "apis-json-apis-properties-pricing-info",
"description": "This property provides a link to a pricing page that applies to an API, providing a breakdown of the costs associated with using an API",
"scope": "",
"property": "",
"type": "This property provides a link to a pricing page that applies to an API, providing a breakdown of the costs associated with using an API",
"guidance": "Plans",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Privacy Policy Info",
"slug": "apis-json-apis-properties-privacy-policy-info",
"description": "This property provides a link to the privacy policy for an API, providing the legal details of how privacy is approached for each API",
"scope": "",
"property": "",
"type": "This property provides a link to the privacy policy for an API, providing the legal details of how privacy is approached for each API",
"guidance": "Legal",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Questions Issues Info",
"slug": "apis-json-apis-properties-questions-issues-info",
"description": "This property ensures that an API has a dedicated link to Git issues for asking questions",
"scope": "",
"property": "",
"type": "This property ensures that an API has a dedicated link to Git issues for asking questions",
"guidance": "Support",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Rate Limits Info",
"slug": "apis-json-apis-properties-rate-limits-info",
"description": "This property ensures there is an API rate limits reference associated with API, ensuring the rate limits applied to an API are clearly communicated",
"scope": "",
"property": "",
"type": "This property ensures there is an API rate limits reference associated with API, ensuring the rate limits applied to an API are clearly communicated",
"guidance": "Rate Limits",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Road Map Info",
"slug": "apis-json-apis-properties-road-map-info",
"description": "This property ensures there is a reference to the road map for an API or for the entire API operations within domain, line of business, or teams",
"scope": "",
"property": "",
"type": "This property ensures there is a reference to the road map for an API or for the entire API operations within domain, line of business, or teams",
"guidance": "Change Management",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Rules Info",
"slug": "apis-json-apis-properties-rules-info",
"description": "This property ensures that an API has governance rules applied, usually as part of a central set of governance rules, defined by policy, or stages of the API lifecycle",
"scope": "",
"property": "",
"type": "This property ensures that an API has governance rules applied, usually as part of a central set of governance rules, defined by policy, or stages of the API lifecycle",
"guidance": "API Governance Rules",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json API Properties Sandbox Info",
"slug": "apis-json-apis-properties-sandbox-info",
"description": "This property ensures that an API has a reference to a sandbox for individual APIs or as part of common properties, providing sandbox, synthetic data, and mock servers for use in making test requests.",
"scope": "",
"property": "",
"type": "This property ensures that an API has a reference to a sandbox for individual APIs or as part of common properties, providing sandbox, synthetic data, and mock servers for use in making test requests.",
"guidance": "Environments",
"image": "",
"tags": ["APIs.json","APIs","Properties","Sandbox"]
},{
"name": "APIs.json Apis Properties Sdk Go Info",
"slug": "apis-json-apis-properties-sdk-go-info",
"description": "This property ensures that there is a Go SDK available for an API, making it easier for Go developers to integrate an API into their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is a Go SDK available for an API, making it easier for Go developers to integrate an API into their applications",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Sdk Info",
"slug": "apis-json-apis-properties-sdk-info",
"description": "This property ensures that there is an SDK available for an API, making it easier for developers to integrate an API into their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is an SDK available for an API, making it easier for developers to integrate an API into their applications",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Sdk Java Info",
"slug": "apis-json-apis-properties-sdk-java-info",
"description": "This property ensures that there is a Java SDK available for an API, making it easier for Java developers to integrate an API into their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is a Java SDK available for an API, making it easier for Java developers to integrate an API into their applications",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Sdk Node Info",
"slug": "apis-json-apis-properties-sdk-node-info",
"description": "This property ensures that there is a Node SDK available for an API, making it easier for Node developers to integrate an API into their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is a Node SDK available for an API, making it easier for Node developers to integrate an API into their applications",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Sdk Python Info",
"slug": "apis-json-apis-properties-sdk-python-info",
"description": "This property ensures that there is a Python SDK available for an API, making it easier for Python developers to integrate an API into their applications",
"scope": "",
"property": "",
"type": "This property ensures that there is a Python SDK available for an API, making it easier for Python developers to integrate an API into their applications",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Security Info",
"slug": "apis-json-apis-properties-security-info",
"description": "This property ensures there is a URL to the security page, providing details about how security is handled for an API",
"scope": "",
"property": "",
"type": "This property ensures there is a URL to the security page, providing details about how security is handled for an API",
"guidance": "Security",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Signup Info",
"slug": "apis-json-apis-properties-signup-info",
"description": "This property ensures there is a link to where you sign up for an API, making sure API consumers can access in a single click",
"scope": "",
"property": "",
"type": "This property ensures there is a link to where you sign up for an API, making sure API consumers can access in a single click",
"guidance": "Onboarding",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Status Info",
"slug": "apis-json-apis-properties-status-info",
"description": "This property ensures that there is a status page available for each API, providing the uptime status for any given moment, as well as historical data",
"scope": "",
"property": "",
"type": "This property ensures that there is a status page available for each API, providing the uptime status for any given moment, as well as historical data",
"guidance": "Monitoring",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Support Email Info",
"slug": "apis-json-apis-properties-support-email-info",
"description": "This property ensures that an API has email support, providing a valid email address that can be used to get API support",
"scope": "",
"property": "",
"type": "This property ensures that an API has email support, providing a valid email address that can be used to get API support",
"guidance": "Support",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Support Issues Info",
"slug": "apis-json-apis-properties-support-issues-info",
"description": "This property ensures that there are Git issues available to support an API, using the issues capability of GitHub, GitLab, or Bitbucket to support API consumers",
"scope": "",
"property": "",
"type": "This property ensures that there are Git issues available to support an API, using the issues capability of GitHub, GitLab, or Bitbucket to support API consumers",
"guidance": "Support",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Support Support Info",
"slug": "apis-json-apis-properties-support-support-info",
"description": "This property ensures that there is a support page available for an API, providing direct and in-direct support opportunities for each API or for entire API platform",
"scope": "",
"property": "",
"type": "This property ensures that there is a support page available for an API, providing direct and in-direct support opportunities for each API or for entire API platform",
"guidance": "Support",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Teams Info",
"slug": "apis-json-apis-properties-teams-info",
"description": "This property ensures that there is a reference to the team behind an API, providing a reference to business and engineering stakeholders",
"scope": "",
"property": "",
"type": "This property ensures that there is a reference to the team behind an API, providing a reference to business and engineering stakeholders",
"guidance": "Organizations",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Terms Of Service Info",
"slug": "apis-json-apis-properties-terms-of-service-info",
"description": "This property ensures that an API has a reference to a terms of service, covering the legal side of using an API",
"scope": "",
"property": "",
"type": "This property ensures that an API has a reference to a terms of service, covering the legal side of using an API",
"guidance": "Legal",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Url Info",
"slug": "apis-json-apis-properties-url-info",
"description": "This property ensures that properties of an API or API contract all have valid URLs, checking if any of the URLs are not properly formed, or could be other formats",
"scope": "",
"property": "",
"type": "This property ensures that properties of an API or API contract all have valid URLs, checking if any of the URLs are not properly formed, or could be other formats",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Properties Use Cases Info",
"slug": "apis-json-apis-properties-use-cases-info",
"description": "This property ensures there is a reference to the use cases for an API, helping align an API with the who, what, how, and why of putting an API to work",
"scope": "",
"property": "",
"type": "This property ensures there is a reference to the use cases for an API, helping align an API with the who, what, how, and why of putting an API to work",
"guidance": "Use Cases",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Versioning Info",
"slug": "apis-json-apis-properties-versioning-info",
"description": "This property ensures there is a reference to how APIs are versioned, providing a single place where teams can learn about how change is communicated",
"scope": "",
"property": "",
"type": "This property ensures there is a reference to how APIs are versioned, providing a single place where teams can learn about how change is communicated",
"guidance": "Change Management",
"image": "",
"tags": ["APIs.json","APIs","Properties","Fundamentals"]
},{
"name": "APIs.json Apis Properties Video Info",
"slug": "apis-json-apis-properties-video-info",
"description": "This property ensures there is a reference to a video page or channel for an API",
"scope": "",
"property": "",
"type": "This property ensures there is a reference to a video page or channel for an API",
"guidance": "Communication",
"image": "",
"tags": ["APIs.json","APIs","Properties","Additional"]
},{
"name": "APIs.json Apis Properties Vocabulary Info",
"slug": "apis-json-apis-properties-vocabulary-info",
"description": "This property ensures that there is a centralized vocabulary in use for guiding the creation and usage of tags, path segments, and other metadata associated with an APIs",
"scope": "",
"property": "",
"type": "This property ensures that there is a centralized vocabulary in use for guiding the creation and usage of tags, path segments, and other metadata associated with an APIs",
"guidance": "Governance",
"image": "",
"tags": ["APIs.json","APIs","Properties"]
},{
"name": "APIs.json Apis Tags Error",
"slug": "apis-json-apis-tags-error",
"description": "Each API defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered by the API, highlighting its business value and the domain in which it is applied.",
"scope": "",
"property": "",
"type": "Each API defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered by the API, highlighting its business value and the domain in which it is applied.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Tags"]
},{
"name": "APIs.json Apis Tags Info",
"slug": "apis-json-apis-tags-info",
"description": "Each API defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered by the API, highlighting its business value and the domain in which it is applied.",
"scope": "",
"property": "",
"type": "Each API defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered by the API, highlighting its business value and the domain in which it is applied.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Tags"]
},{
"name": "APIs.json Apis Tags Upper Case Error",
"slug": "apis-json-apis-tags-upper-case-error",
"description": "Maintaining consistent casing for tags applied to individual APIs ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"scope": "",
"property": "",
"type": "Maintaining consistent casing for tags applied to individual APIs ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Tags"]
},{
"name": "APIs.json Apis Tags Upper Case Info",
"slug": "apis-json-apis-tags-upper-case-info",
"description": "Maintaining consistent casing for tags applied to individual APIs ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"scope": "",
"property": "",
"type": "Maintaining consistent casing for tags applied to individual APIs ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"guidance": "APIs Metadata",
"image": "",
"tags": ["APIs.json","APIs","Tags"]
},{
"name": "APIs.json Arazzo Info",
"slug": "apis-json-arazzo-info",
"description": "APIs should declare Arazzo workflows so consumers and agents can discover documented, multi-step sequences for accomplishing common tasks with the API. Declaring a property of type Arazzo in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should declare Arazzo workflows so consumers and agents can discover documented, multi-step sequences for accomplishing common tasks with the API. Declaring a property of type Arazzo in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Workflows",
"image": "",
"tags": ["APIs.json","Workflows","Default"]
},{
"name": "APIs.json Common Info",
"slug": "apis-json-common-info",
"description": "An APIs.json artifact can include a set of common properties that describe aspects of API operations shared across multiple APIs in a collection. These common properties are typically managed by a centralized platform team, ensuring consistency and reducing the burden on individual teams. This allows API teams to focus on delivering the unique value of their APIs rather than duplicating efforts on shared operational elements.",
"scope": "",
"property": "",
"type": "An APIs.json artifact can include a set of common properties that describe aspects of API operations shared across multiple APIs in a collection. These common properties are typically managed by a centralized platform team, ensuring consistency and reducing the burden on individual teams. This allows API teams to focus on delivering the unique value of their APIs rather than duplicating efforts on shared operational elements.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Common","Metadata"]
},{
"name": "APIs.json Created Info",
"slug": "apis-json-created-info",
"description": "The created property in an APIs.json contract might seem like a minor detail, but it serves an important purpose by providing a timestamp that marks the origin of the intent to offer an interface for business purposes. This property offers a straightforward reference to indicate the age and potentially the maturity of a collection of APIs being used in business operations.",
"scope": "",
"property": "",
"type": "The created property in an APIs.json contract might seem like a minor detail, but it serves an important purpose by providing a timestamp that marks the origin of the intent to offer an interface for business purposes. This property offers a straightforward reference to indicate the age and potentially the maturity of a collection of APIs being used in business operations.",
"guidance": "Change Management",
"image": "",
"tags": ["APIs.json","Metadata","Changes"]
},{
"name": "APIs.json Description Info",
"slug": "apis-json-description-info",
"description": "Every collection of APIs defined in APIs.json should include a one- or two-paragraph description outlining the purpose of the APIs. While individual APIs should have their own descriptions, the collection’s description should focus on the overall business purpose and the domain in which the APIs are intended to be used.",
"scope": "",
"property": "",
"type": "Every collection of APIs defined in APIs.json should include a one- or two-paragraph description outlining the purpose of the APIs. While individual APIs should have their own descriptions, the collection’s description should focus on the overall business purpose and the domain in which the APIs are intended to be used.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Image Info",
"slug": "apis-json-image-info",
"description": "APIs.json contracts are often used to power discover and distribute as part of API catalogs and marketplaces. These are places where having a visual representation matching the purpose of a collection of APIs helps with discovery and onboarding, allowing some APIs to stand out and make a good first impression on consumers.",
"scope": "",
"property": "",
"type": "APIs.json contracts are often used to power discover and distribute as part of API catalogs and marketplaces. These are places where having a visual representation matching the purpose of a collection of APIs helps with discovery and onboarding, allowing some APIs to stand out and make a good first impression on consumers.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Maintainers Email Info",
"slug": "apis-json-maintainers-email-info",
"description": "The maintainers email is to provide a quick way to contact the maintainer of an APIs",
"scope": "",
"property": "",
"type": "The maintainers email is to provide a quick way to contact the maintainer of an APIs",
"guidance": "Owners",
"image": "",
"tags": ["APIs.json","Maintainers"]
},{
"name": "APIs.json Maintainers Fn Info",
"slug": "apis-json-maintainers-fn-info",
"description": "The purpose of the FN is to specify the formatted text corresponding to the contact name in the vCard for an APIs",
"scope": "",
"property": "",
"type": "The purpose of the FN is to specify the formatted text corresponding to the contact name in the vCard for an APIs",
"guidance": "Owners",
"image": "",
"tags": ["APIs.json","Maintainers"]
},{
"name": "APIs.json Maintainers Info",
"slug": "apis-json-maintainers-info",
"description": "The maintainers property is for identifying the entity who is maintaining an APIs",
"scope": "",
"property": "",
"type": "The maintainers property is for identifying the entity who is maintaining an APIs",
"guidance": "Owners",
"image": "",
"tags": ["APIs.json","Maintainers"]
},{
"name": "APIs.json MCP Server Info",
"slug": "apis-json-mcp-server-info",
"description": "APIs should declare an MCP server so agents and MCP-aware tooling can discover and connect to the API through the Model Context Protocol. Declaring a property of type MCPServer in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should declare an MCP server so agents and MCP-aware tooling can discover and connect to the API through the Model Context Protocol. Declaring a property of type MCPServer in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Agents",
"image": "",
"tags": ["APIs.json","Agents","Default"]
},{
"name": "APIs.json Modified Info",
"slug": "apis-json-modified-info",
"description": "The modified property in an APIs.json collection indicates the most recent updates made to a group of APIs. While detailed change logs can provide more specifics, an accurate and up-to-date modified timestamp is essential for tracking and managing changes effectively across operations.",
"scope": "",
"property": "",
"type": "The modified property in an APIs.json collection indicates the most recent updates made to a group of APIs. While detailed change logs can provide more specifics, an accurate and up-to-date modified timestamp is essential for tracking and managing changes effectively across operations.",
"guidance": "Change Management",
"image": "",
"tags": ["APIs.json","Metadata","Changes"]
},{
"name": "APIs.json Name Info",
"slug": "apis-json-name-info",
"description": "The name of a collection of APIs should describe their purpose, target audience, and the problems they aim to solve. While individual APIs should have their own specific names, the name in the APIs.json file should provide a higher-level description, emphasizing the overarching business purpose of the APIs.",
"scope": "",
"property": "",
"type": "The name of a collection of APIs should describe their purpose, target audience, and the problems they aim to solve. While individual APIs should have their own specific names, the name in the APIs.json file should provide a higher-level description, emphasizing the overarching business purpose of the APIs.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Overlay Info",
"slug": "apis-json-overlay-info",
"description": "APIs should declare an OpenAPI Overlay so consumers can discover documented, reusable modifications applied to the API's OpenAPI definition. Declaring a property of type OpenAPIOverlay in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should declare an OpenAPI Overlay so consumers can discover documented, reusable modifications applied to the API's OpenAPI definition. Declaring a property of type OpenAPIOverlay in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "OpenAPI",
"image": "",
"tags": ["APIs.json","OpenAPI","Default"]
},{
"name": "APIs.json Plans Info",
"slug": "apis-json-plans-info",
"description": "APIs should declare their pricing plans so consumers can discover the tiers, limits, and costs of using the API. Declaring a property of type Plans in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should declare their pricing plans so consumers can discover the tiers, limits, and costs of using the API. Declaring a property of type Plans in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Monetization",
"image": "",
"tags": ["APIs.json","Monetization","Default"]
},{
"name": "APIs.json SLA Info",
"slug": "apis-json-sla-info",
"description": "APIs should declare a service level agreement so consumers can discover the uptime, performance, and support commitments backing the API. Declaring a property of type ServiceLevelAgreement in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"scope": "",
"property": "",
"type": "APIs should declare a service level agreement so consumers can discover the uptime, performance, and support commitments backing the API. Declaring a property of type ServiceLevelAgreement in the APIs.json properties array publishes this artifact as part of the API's discoverable index.",
"guidance": "Operations",
"image": "",
"tags": ["APIs.json","Operations","Default"]
},{
"name": "APIs.json Specification AID Info",
"slug": "apis-json-specification-aid-info",
"description": "Every collection of APIs should have a unique identifier. This unique API identifier, or AID, serves as a human and machine-readable reference for organizing and managing various APIs. Similar to a barcode, a unique identifier helps track APIs, whether you are discovering them or putting them to use.
",
"scope": "",
"property": "",
"type": "Every collection of APIs should have a unique identifier. This unique API identifier, or AID, serves as a human and machine-readable reference for organizing and managing various APIs. Similar to a barcode, a unique identifier helps track APIs, whether you are discovering them or putting them to use.
",
"guidance": "Specifications",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Type Info",
"slug": "apis-json-specification-type-info",
"description": "The type property in an APIs.json file classifies the business contracts for different types of API collections. It can represent a simple index for a single API, a template or example to showcase possibilities, or classifications such as contract, search, and network to address specific business or discovery purposes.",
"scope": "",
"property": "",
"type": "The type property in an APIs.json file classifies the business contracts for different types of API collections. It can represent a simple index for a single API, a template or example to showcase possibilities, or classifications such as contract, search, and network to address specific business or discovery purposes.",
"guidance": "Specifications",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Version Info",
"slug": "apis-json-specification-version-info",
"description": "The specification version of an APIs.json collection indicates which version of the APIs.json specification is being used. This ensures compatibility and allows for the validation of new properties. While property types are the most common additions, new top-level elements are also being introduced. Proper governance ensures that the correct version of the specification is applied.",
"scope": "",
"property": "",
"type": "The specification version of an APIs.json collection indicates which version of the APIs.json specification is being used. This ensures compatibility and allows for the validation of new properties. While property types are the most common additions, new top-level elements are also being introduced. Proper governance ensures that the correct version of the specification is applied.",
"guidance": "Specifications",
"image": "",
"tags": ["APIs.json","Metadata","Changes"]
},{
"name": "APIs.json Tags Info",
"slug": "apis-json-tags-info",
"description": "Each collection of APIs defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered as part of the collection of APIs, highlighting its business value and the domain in which it is applied.",
"scope": "",
"property": "",
"type": "Each collection of APIs defined in an APIs.json artifact includes a property for adding one or more tags. These tags provide additional context about the resources or capabilities offered as part of the collection of APIs, highlighting its business value and the domain in which it is applied.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "APIs.json Tags Upper Case Error",
"slug": "apis-json-tags-upper-case-error",
"description": "Maintaining consistent casing for tags applied to APIs.json contracts ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"scope": "",
"property": "",
"type": "Maintaining consistent casing for tags applied to APIs.json contracts ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Tags"]
},{
"name": "APIs.json Tags Upper Case Info",
"slug": "apis-json-tags-upper-case-info",
"description": "Maintaining consistent casing for tags applied to APIs.json contracts ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"scope": "",
"property": "",
"type": "Maintaining consistent casing for tags applied to APIs.json contracts ensures a uniform appearance and enhances search and discovery. Each word in a tag should be capitalized, with the first letter of every word in a phrase treated the same way.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Tags"]
},{
"name": "APIs.json Url Info",
"slug": "apis-json-url-info",
"description": "The top-level URL in an APIs.json file contains a fully qualified link to where the APIs.json file is published. This URL serves as a reference for the API collection and can also be validated. When an APIs.json file includes URLs to various properties, it can be verified against the top-level domain, ensuring the creation of an authoritative APIs.json artifact.",
"scope": "",
"property": "",
"type": "The top-level URL in an APIs.json file contains a fully qualified link to where the APIs.json file is published. This URL serves as a reference for the API collection and can also be validated. When an APIs.json file includes URLs to various properties, it can be verified against the top-level domain, ensuring the creation of an authoritative APIs.json artifact.",
"guidance": "Contracts",
"image": "",
"tags": ["APIs.json","Metadata"]
},{
"name": "AsyncAPI Channel Description Info",
"slug": "asyncapi-channel-description-info",
"description": "Each AsyncAPI channel should include a description so consumers understand the purpose of the channel and the events that flow through it.",
"scope": "",
"property": "",
"type": "Each AsyncAPI channel should include a description so consumers understand the purpose of the channel and the events that flow through it.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Channels","Default"]
},{
"name": "AsyncAPI Channel Parameters Examples",
"slug": "asyncapi-channel-parameters-examples-warn",
"description": "AsyncAPI channel parameters should include examples to support mocking, testing, and documentation. Examples help consumers understand expected parameter values for channel subscriptions.",
"scope": "",
"property": "",
"type": "AsyncAPI channel parameters should include examples to support mocking, testing, and documentation. Examples help consumers understand expected parameter values for channel subscriptions.",
"guidance": "Documentation",
"image": "",
"tags": ["AsyncAPI","Channels","Parameters","Examples","Mocking"]
},{
"name": "AsyncAPI Channels Defined Error",
"slug": "asyncapi-channels-defined-error",
"description": "Every AsyncAPI definition must define a channels object so consumers know which topics, queues, or subjects are available for publishing and subscribing to events.",
"scope": "",
"property": "",
"type": "Every AsyncAPI definition must define a channels object so consumers know which topics, queues, or subjects are available for publishing and subscribing to events.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Channels","Default"]
},{
"name": "AsyncAPI Info Title Error",
"slug": "asyncapi-info-title-error",
"description": "Every AsyncAPI definition must provide a title in the info object so consumers, tooling, and discovery can identify the event-driven API by name.",
"scope": "",
"property": "",
"type": "Every AsyncAPI definition must provide a title in the info object so consumers, tooling, and discovery can identify the event-driven API by name.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Info","Default"]
},{
"name": "AsyncAPI Info Title Info",
"slug": "asyncapi-info-title-info",
"description": "Every AsyncAPI definition should provide a title in the info object so consumers, tooling, and discovery can identify the event-driven API by name.",
"scope": "",
"property": "",
"type": "Every AsyncAPI definition should provide a title in the info object so consumers, tooling, and discovery can identify the event-driven API by name.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Info","Default"]
},{
"name": "AsyncAPI Info Version Error",
"slug": "asyncapi-info-version-error",
"description": "Every AsyncAPI definition must provide a version in the info object so consumers and tooling can track the version of the event-driven API they are working with.",
"scope": "",
"property": "",
"type": "Every AsyncAPI definition must provide a version in the info object so consumers and tooling can track the version of the event-driven API they are working with.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Info","Default"]
},{
"name": "AsyncAPI Message Examples",
"slug": "asyncapi-message-examples-warn",
"description": "AsyncAPI messages should include examples to support event-driven API mocking, testing, and documentation. Examples help consumers understand message payloads and enable tools to generate realistic mock events.",
"scope": "",
"property": "",
"type": "AsyncAPI messages should include examples to support event-driven API mocking, testing, and documentation. Examples help consumers understand message payloads and enable tools to generate realistic mock events.",
"guidance": "Documentation",
"image": "",
"tags": ["AsyncAPI","Messages","Examples","Mocking"]
},{
"name": "AsyncAPI Message Payload Info",
"slug": "asyncapi-message-payload-info",
"description": "Each AsyncAPI message on a publish or subscribe operation should define a payload so consumers understand the structure of the event data they will produce or receive.",
"scope": "",
"property": "",
"type": "Each AsyncAPI message on a publish or subscribe operation should define a payload so consumers understand the structure of the event data they will produce or receive.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Messages","Default"]
},{
"name": "AsyncAPI Operation Description Info",
"slug": "asyncapi-operation-description-info",
"description": "Each AsyncAPI publish and subscribe operation should include a description so consumers understand what the operation does and when it should be used.",
"scope": "",
"property": "",
"type": "Each AsyncAPI publish and subscribe operation should include a description so consumers understand what the operation does and when it should be used.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Operations","Default"]
},{
"name": "AsyncAPI Servers Defined Info",
"slug": "asyncapi-servers-defined-info",
"description": "An AsyncAPI definition should define a servers object so consumers know which brokers or endpoints to connect to when producing or consuming events.",
"scope": "",
"property": "",
"type": "An AsyncAPI definition should define a servers object so consumers know which brokers or endpoints to connect to when producing or consuming events.",
"guidance": "AsyncAPI",
"image": "",
"tags": ["AsyncAPI","Servers","Default"]
},{
"name": "JSON Schema Draft 2020-12 Description Error",
"slug": "json-schema-2020-12-description-error",
"description": "Each JSON Schema object MUST include a description that explains, in plain language, the purpose and function of the object. This description should provide a clear overview of how the object is intended to be used within operations.",
"scope": "",
"property": "",
"type": "Each JSON Schema object MUST include a description that explains, in plain language, the purpose and function of the object. This description should provide a clear overview of how the object is intended to be used within operations.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Description Info",
"slug": "json-schema-2020-12-description-info",
"description": "Each JSON Schema object MUST include a description that explains, in plain language, the purpose and function of the object. This description should provide a clear overview of how the object is intended to be used within operations.",
"scope": "",
"property": "",
"type": "Each JSON Schema object MUST include a description that explains, in plain language, the purpose and function of the object. This description should provide a clear overview of how the object is intended to be used within operations.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Description Length Error",
"slug": "json-schema-2020-12-description-length-error",
"description": "The description for any JSON Schema object should be concise, ensuring it remains easy to read and understand for anyone using or interpreting it. This approach helps keep the schema self-contained while still providing enough context to inform its application wherever it is used.",
"scope": "",
"property": "",
"type": "The description for any JSON Schema object should be concise, ensuring it remains easy to read and understand for anyone using or interpreting it. This approach helps keep the schema self-contained while still providing enough context to inform its application wherever it is used.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Description Length Info",
"slug": "json-schema-2020-12-description-length-info",
"description": "The description for any JSON Schema object should be concise, ensuring it remains easy to read and understand for anyone using or interpreting it. This approach helps keep the schema self-contained while still providing enough context to inform its application wherever it is used.",
"scope": "",
"property": "",
"type": "The description for any JSON Schema object should be concise, ensuring it remains easy to read and understand for anyone using or interpreting it. This approach helps keep the schema self-contained while still providing enough context to inform its application wherever it is used.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 ID Error",
"slug": "json-schema-2020-12-id-error",
"description": "Each JSON Schema object MUST have a unique identifier, represented as a URL pointing to its location. The $id property in JSON Schema is used to establish the source of truth for any object being defined and validated.",
"scope": "",
"property": "",
"type": "Each JSON Schema object MUST have a unique identifier, represented as a URL pointing to its location. The $id property in JSON Schema is used to establish the source of truth for any object being defined and validated.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Identifiers"]
},{
"name": "JSON Schema Draft 2020-12 ID Info",
"slug": "json-schema-2020-12-id-info",
"description": "Each JSON Schema object MUST have a unique identifier, represented as a URL pointing to its location. The $id property in JSON Schema is used to establish the source of truth for any object being defined and validated.",
"scope": "",
"property": "",
"type": "Each JSON Schema object MUST have a unique identifier, represented as a URL pointing to its location. The $id property in JSON Schema is used to establish the source of truth for any object being defined and validated.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Identifiers"]
},{
"name": "JSON Schema Draft 2020-12 ID Source URL Error",
"slug": "json-schema-2020-12-id-source-url-error",
"description": "The $id property in any JSON Schema MUST contain a valid URL pointing to a central registry, repository, or another authoritative source for the object. This URL ensures that the object's source is always accessible and can be used for proper validation.",
"scope": "",
"property": "",
"type": "The $id property in any JSON Schema MUST contain a valid URL pointing to a central registry, repository, or another authoritative source for the object. This URL ensures that the object's source is always accessible and can be used for proper validation.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Identifiers"]
},{
"name": "JSON Schema Draft 2020-12 ID Source URL Info",
"slug": "json-schema-2020-12-id-source-url-info",
"description": "The $id property in any JSON Schema MUST contain a valid URL pointing to a central registry, repository, or another authoritative source for the object. This URL ensures that the object's source is always accessible and can be used for proper validation.",
"scope": "",
"property": "",
"type": "The $id property in any JSON Schema MUST contain a valid URL pointing to a central registry, repository, or another authoritative source for the object. This URL ensures that the object's source is always accessible and can be used for proper validation.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Identifiers"]
},{
"name": "JSON Schema Draft 2020-12 Properties Allowed Integer Format Error",
"slug": "json-schema-2020-12-properties-allowed-integer-format-error",
"description": "Schema integer properties should have a format property with int32 or int64 applied",
"scope": "",
"property": "",
"type": "Schema integer properties should have a format property with int32 or int64 applied",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Allowed Number Format Error",
"slug": "json-schema-2020-12-properties-allowed-number-format-error",
"description": "Schema integer properties should have a format property with int32 or int64 applied",
"scope": "",
"property": "",
"type": "Schema integer properties should have a format property with int32 or int64 applied",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Items Error",
"slug": "json-schema-2020-12-properties-array-items-error",
"description": "Schema properties that are of the type array must have an items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array must have an items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Items Info",
"slug": "json-schema-2020-12-properties-array-items-info",
"description": "Schema properties that are of the type array must have an items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array must have an items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Maxitems Error",
"slug": "json-schema-2020-12-properties-array-maxitems-error",
"description": "Schema properties that are of the type array should have a max items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a max items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Maxitems Info",
"slug": "json-schema-2020-12-properties-array-maxitems-info",
"description": "Schema properties that are of the type array should have a max items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a max items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Minitems Error",
"slug": "json-schema-2020-12-properties-array-minitems-error",
"description": "Schema properties that are of the type array should have a min items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a min items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Array Minitems Info",
"slug": "json-schema-2020-12-properties-array-minitems-info",
"description": "Schema properties that are of the type array should have a min items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a min items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Define Number Maximum Error",
"slug": "json-schema-2020-12-properties-define-number-maximum-error",
"description": "Schema properties that are of the type number should have a maximum property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type number should have a maximum property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Define Number Minimum Error",
"slug": "json-schema-2020-12-properties-define-number-minimum-error",
"description": "Schema properties that are of the type number should have a minimum property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type number should have a minimum property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties Descriptions Error",
"slug": "json-schema-2020-12-properties-descriptions-error",
"description": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"scope": "",
"property": "",
"type": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties Descriptions Info",
"slug": "json-schema-2020-12-properties-descriptions-info",
"description": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"scope": "",
"property": "",
"type": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties Descriptions Length Error",
"slug": "json-schema-2020-12-properties-descriptions-length-error",
"description": "Schema property descriptions should have a length limit applied, applying constraints to writing descriptions, and keeping consistent across APIs",
"scope": "",
"property": "",
"type": "Schema property descriptions should have a length limit applied, applying constraints to writing descriptions, and keeping consistent across APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties Enum Casing Error",
"slug": "json-schema-2020-12-properties-enum-casing-error",
"description": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"scope": "",
"property": "",
"type": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Enumerators"]
},{
"name": "JSON Schema Draft 2020-12 Properties Enum Casing Info",
"slug": "json-schema-2020-12-properties-enum-casing-info",
"description": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"scope": "",
"property": "",
"type": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Enumerators"]
},{
"name": "JSON Schema Draft 2020-12 Properties Enum Info",
"slug": "json-schema-2020-12-properties-enum-info",
"description": "Schema property has enumerators, providing consistent values chosen by consumers when making requests",
"scope": "",
"property": "",
"type": "Schema property has enumerators, providing consistent values chosen by consumers when making requests",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Enumerators"]
},{
"name": "JSON Schema Draft 2020-12 Properties Error",
"slug": "json-schema-2020-12-properties-error",
"description": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"scope": "",
"property": "",
"type": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties"]
},{
"name": "JSON Schema Draft 2020-12 Properties Info",
"slug": "json-schema-2020-12-properties-info",
"description": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"scope": "",
"property": "",
"type": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties"]
},{
"name": "JSON Schema Draft 2020-12 Properties Names Camel Case Error",
"slug": "json-schema-2020-12-properties-names-camel-case-error",
"description": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"scope": "",
"property": "",
"type": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties Names Camel Case Info",
"slug": "json-schema-2020-12-properties-names-camel-case-info",
"description": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"scope": "",
"property": "",
"type": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties Names Length Error",
"slug": "json-schema-2020-12-properties-names-length-error",
"description": "Schema property names have a length restriction applied, keeping names consistent, and avoiding being too long",
"scope": "",
"property": "",
"type": "Schema property names have a length restriction applied, keeping names consistent, and avoiding being too long",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Properties String Maxlength Error",
"slug": "json-schema-2020-12-properties-string-maxlength-error",
"description": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties String Maxlength Info",
"slug": "json-schema-2020-12-properties-string-maxlength-info",
"description": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties String Minlength Error",
"slug": "json-schema-2020-12-properties-string-minlength-error",
"description": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Properties String Minlength Info",
"slug": "json-schema-2020-12-properties-string-minlength-info",
"description": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["JSON Schema","Schema","Properties","Types"]
},{
"name": "JSON Schema Draft 2020-12 Required Error",
"slug": "json-schema-2020-12-required-error",
"description": "All JSON Schema objects should explicitly define their properties and include at least one required property. Defining required properties enhances the accuracy and reliability of validation for each object.",
"scope": "",
"property": "",
"type": "All JSON Schema objects should explicitly define their properties and include at least one required property. Defining required properties enhances the accuracy and reliability of validation for each object.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Required"]
},{
"name": "JSON Schema Draft 2020-12 Required Info",
"slug": "json-schema-2020-12-required-info",
"description": "All JSON Schema objects should explicitly define their properties and include at least one required property. Defining required properties enhances the accuracy and reliability of validation for each object.",
"scope": "",
"property": "",
"type": "All JSON Schema objects should explicitly define their properties and include at least one required property. Defining required properties enhances the accuracy and reliability of validation for each object.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Required"]
},{
"name": "JSON Schema Draft 2020-12 Schema Draft Error",
"slug": "json-schema-2020-12-schema-draft-error",
"description": "The $schema property in a JSON Schema MUST always reference the latest draft of the specification to ensure consistent validation across all objects. Using the most up-to-date version of the specification helps maintain stability and reliability in the use of objects within any API.",
"scope": "",
"property": "",
"type": "The $schema property in a JSON Schema MUST always reference the latest draft of the specification to ensure consistent validation across all objects. Using the most up-to-date version of the specification helps maintain stability and reliability in the use of objects within any API.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Changes"]
},{
"name": "JSON Schema Draft 2020-12 Schema Draft Info",
"slug": "json-schema-2020-12-schema-draft-info",
"description": "The $schema property in a JSON Schema MUST always reference the latest draft of the specification to ensure consistent validation across all objects. Using the most up-to-date version of the specification helps maintain stability and reliability in the use of objects within any API.",
"scope": "",
"property": "",
"type": "The $schema property in a JSON Schema MUST always reference the latest draft of the specification to ensure consistent validation across all objects. Using the most up-to-date version of the specification helps maintain stability and reliability in the use of objects within any API.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Changes"]
},{
"name": "JSON Schema Draft 2020-12 Schema Error",
"slug": "json-schema-2020-12-schema-error",
"description": "JSON Schema objects should always include the $schema property to explicitly indicate which version of the specification is being used. This property is essential for tooling and should consistently reference the latest version to ensure compatibility and up-to-date functionality.",
"scope": "",
"property": "",
"type": "JSON Schema objects should always include the $schema property to explicitly indicate which version of the specification is being used. This property is essential for tooling and should consistently reference the latest version to ensure compatibility and up-to-date functionality.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Changes"]
},{
"name": "JSON Schema Draft 2020-12 Schema Info",
"slug": "json-schema-2020-12-schema-info",
"description": "JSON Schema objects should always include the $schema property to explicitly indicate which version of the specification is being used. This property is essential for tooling and should consistently reference the latest version to ensure compatibility and up-to-date functionality.",
"scope": "",
"property": "",
"type": "JSON Schema objects should always include the $schema property to explicitly indicate which version of the specification is being used. This property is essential for tooling and should consistently reference the latest version to ensure compatibility and up-to-date functionality.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata","Changes"]
},{
"name": "JSON Schema Draft 2020-12 Title Error",
"slug": "json-schema-2020-12-title-error",
"description": "JSON Schema objects MUST include a title property that describes the object in plain language while reflecting the object's file name. The title should convey the object's content and purpose, providing clarity on how it is intended to be used.",
"scope": "",
"property": "",
"type": "JSON Schema objects MUST include a title property that describes the object in plain language while reflecting the object's file name. The title should convey the object's content and purpose, providing clarity on how it is intended to be used.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Title Info",
"slug": "json-schema-2020-12-title-info",
"description": "JSON Schema objects MUST include a title property that describes the object in plain language while reflecting the object's file name. The title should convey the object's content and purpose, providing clarity on how it is intended to be used.",
"scope": "",
"property": "",
"type": "JSON Schema objects MUST include a title property that describes the object in plain language while reflecting the object's file name. The title should convey the object's content and purpose, providing clarity on how it is intended to be used.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Title Length Error",
"slug": "json-schema-2020-12-title-length-error",
"description": "The title of JSON Schema objects should be concise yet accurately describe the object's purpose. Keeping the title short ensures clarity and minimizes downstream impact on other items using the object.",
"scope": "",
"property": "",
"type": "The title of JSON Schema objects should be concise yet accurately describe the object's purpose. Keeping the title short ensures clarity and minimizes downstream impact on other items using the object.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Title Length info",
"slug": "json-schema-2020-12-title-length-error",
"description": "The title of JSON Schema objects should be concise yet accurately describe the object's purpose. Keeping the title short ensures clarity and minimizes downstream impact on other items using the object.",
"scope": "",
"property": "",
"type": "The title of JSON Schema objects should be concise yet accurately describe the object's purpose. Keeping the title short ensures clarity and minimizes downstream impact on other items using the object.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Title Pascal Case Error",
"slug": "json-schema-2020-12-title-pascal-case-error",
"description": "The name of a JSON Schema object should always be in PascalCase to ensure readability and consistency across APIs. Using PascalCase helps maintain uniformity and aligns the object's name with its plain-language title.",
"scope": "",
"property": "",
"type": "The name of a JSON Schema object should always be in PascalCase to ensure readability and consistency across APIs. Using PascalCase helps maintain uniformity and aligns the object's name with its plain-language title.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Title Pascal Case Info",
"slug": "json-schema-2020-12-title-pascal-case-info",
"description": "The name of a JSON Schema object should always be in PascalCase to ensure readability and consistency across APIs. Using PascalCase helps maintain uniformity and aligns the object's name with its plain-language title.",
"scope": "",
"property": "",
"type": "The name of a JSON Schema object should always be in PascalCase to ensure readability and consistency across APIs. Using PascalCase helps maintain uniformity and aligns the object's name with its plain-language title.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Type Error",
"slug": "json-schema-2020-12-type-error",
"description": "JSON Schema objects should explicitly define their type, ensuring clarity about each object's structure. This allows tools utilizing the schema to accurately validate the object wherever it is applied.",
"scope": "",
"property": "",
"type": "JSON Schema objects should explicitly define their type, ensuring clarity about each object's structure. This allows tools utilizing the schema to accurately validate the object wherever it is applied.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "JSON Schema Draft 2020-12 Type Info",
"slug": "json-schema-2020-12-type-info",
"description": "JSON Schema objects should explicitly define their type, ensuring clarity about each object's structure. This allows tools utilizing the schema to accurately validate the object wherever it is applied.",
"scope": "",
"property": "",
"type": "JSON Schema objects should explicitly define their type, ensuring clarity about each object's structure. This allows tools utilizing the schema to accurately validate the object wherever it is applied.",
"guidance": "API Evangelist",
"image": "",
"tags": ["JSON Schema","Metadata"]
},{
"name": "OpenAPI Components Examples Error",
"slug": "openapi-components-examples-error",
"description": "Utilizing an example object in the centralized OpenAPI components library helps make examples reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing an example object in the centralized OpenAPI components library helps make examples reusable across API requests and responses",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Examples Info",
"slug": "openapi-components-examples-info",
"description": "Utilizing an example object in the centralized OpenAPI components library helps make examples reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing an example object in the centralized OpenAPI components library helps make examples reusable across API requests and responses",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Headers Error",
"slug": "openapi-components-headers-error",
"description": "Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Headers Info",
"slug": "openapi-components-headers-info",
"description": "Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Headers Rate Limit Error",
"slug": "openapi-components-headers-rate-limit-error",
"description": "Utilizing centralized headers rate limits allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limits applied consistently across all APIs.",
"scope": "",
"property": "",
"type": "Utilizing centralized headers rate limits allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limits applied consistently across all APIs.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components","Headers"]
},{
"name": "OpenAPI Components Headers Rate Limit Info",
"slug": "openapi-components-headers-rate-limit-info",
"description": "Utilizing centralized headers rate limits allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limits applied consistently across all APIs.",
"scope": "",
"property": "",
"type": "Utilizing centralized headers rate limits allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limits applied consistently across all APIs.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components","Headers"]
},{
"name": "OpenAPI Components Headers Retry After Error",
"slug": "openapi-components-headers-retry-after-error",
"description": "Utilizing centralized retry after headers allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limiting applied consistently across all APIs.",
"scope": "",
"property": "",
"type": "Utilizing centralized retry after headers allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limiting applied consistently across all APIs.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components","Headers"]
},{
"name": "OpenAPI Components Headers Retry After Info",
"slug": "openapi-components-headers-retry-after-info",
"description": "Utilizing centralized retry after headers allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limiting applied consistently across all APIs.",
"scope": "",
"property": "",
"type": "Utilizing centralized retry after headers allows you to reuse headers across all API requests and responses, enabling a more organized approach to handling the transport and rate limiting applied consistently across all APIs.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OpenAPI","Components","Headers"]
},{
"name": "OpenAPI Components Parameters Casing Camel Error",
"slug": "openapi-components-parameters-casing-camel-error",
"description": "Providing parameters with consistent naming helps make it easier for API consumers to understand how they are able to configure their API requests",
"scope": "",
"property": "",
"type": "Providing parameters with consistent naming helps make it easier for API consumers to understand how they are able to configure their API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Casing Camel Info",
"slug": "openapi-components-parameters-casing-camel-info",
"description": "Providing parameters with consistent naming helps make it easier for API consumers to understand how they are able to configure their API requests",
"scope": "",
"property": "",
"type": "Providing parameters with consistent naming helps make it easier for API consumers to understand how they are able to configure their API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Casing Camel Warn",
"slug": "openapi-components-parameters-casing-camel-warn",
"description": "Component parameter names should be written in camelCase so that consumers encounter consistent, predictable naming across every operation in the API.",
"scope": "",
"property": "",
"type": "Component parameter names should be written in camelCase so that consumers encounter consistent, predictable naming across every operation in the API.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Parameters","Casing","Default"]
},{
"name": "OpenAPI Components Parameters Description Error",
"slug": "openapi-components-parameters-description-error",
"description": "Having a parameters description provides more depth to what a parameter does and will be displayed via documentation, and other tooling used across the API lifecycle",
"scope": "",
"property": "",
"type": "Having a parameters description provides more depth to what a parameter does and will be displayed via documentation, and other tooling used across the API lifecycle",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Description Info",
"slug": "openapi-components-parameters-description-info",
"description": "Having a parameters description provides more depth to what a parameter does and will be displayed via documentation, and other tooling used across the API lifecycle",
"scope": "",
"property": "",
"type": "Having a parameters description provides more depth to what a parameter does and will be displayed via documentation, and other tooling used across the API lifecycle",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Description Length Error",
"slug": "openapi-components-parameters-description-length-error",
"description": "Limiting the length of parameters description forces us to be more concise in how we describe each parameter, while keeping our documentation and other ways descriptions show up in discovery and portals more consistent",
"scope": "",
"property": "",
"type": "Limiting the length of parameters description forces us to be more concise in how we describe each parameter, while keeping our documentation and other ways descriptions show up in discovery and portals more consistent",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Enum Casing Error",
"slug": "openapi-components-parameters-enum-casing-error",
"description": "Keeping parameters enumerator casing consistent across APIs helps reduce confusion by consumers, and can keep aligned with services and applications putting an API to work",
"scope": "",
"property": "",
"type": "Keeping parameters enumerator casing consistent across APIs helps reduce confusion by consumers, and can keep aligned with services and applications putting an API to work",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Enumerators","Type","Default"]
},{
"name": "OpenAPI Components Parameters Enum Casing Info",
"slug": "openapi-components-parameters-enum-casing-info",
"description": "Keeping parameters enumerator casing consistent across APIs helps reduce confusion by consumers, and can keep aligned with services and applications putting an API to work",
"scope": "",
"property": "",
"type": "Keeping parameters enumerator casing consistent across APIs helps reduce confusion by consumers, and can keep aligned with services and applications putting an API to work",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Enumerators","Type","Default"]
},{
"name": "OpenAPI Components Parameters Enum Info",
"slug": "openapi-components-parameters-enum-info",
"description": "Providing enums for your parameters helps reduce errors and keeps the inputs for your API requests more consistent for consumers",
"scope": "",
"property": "",
"type": "Providing enums for your parameters helps reduce errors and keeps the inputs for your API requests more consistent for consumers",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Enumerators","Type"]
},{
"name": "OpenAPI Components Parameters Error",
"slug": "openapi-components-parameters-error",
"description": "Having a components parameters object allows all parameters used across an API to be centralized, allowing for reuse and easier governance of the parameters used to configure API requests",
"scope": "",
"property": "",
"type": "Having a components parameters object allows all parameters used across an API to be centralized, allowing for reuse and easier governance of the parameters used to configure API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters"]
},{
"name": "OpenAPI Components Parameters Example Error",
"slug": "openapi-components-parameters-example-error",
"description": "Parameters must always possess a example to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"scope": "",
"property": "",
"type": "Parameters must always possess a example to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Example"]
},{
"name": "OpenAPI Components Parameters Example Info",
"slug": "openapi-components-parameters-example-info",
"description": "Parameters must always possess a example to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"scope": "",
"property": "",
"type": "Parameters must always possess a example to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Example"]
},{
"name": "OpenAPI Components Parameters In Error",
"slug": "openapi-components-parameters-in-error",
"description": "Providing an in property for parameters gets explicit about whether a parameter is in the path, query, or a header, making it clear to consumers where they can configure their request",
"scope": "",
"property": "",
"type": "Providing an in property for parameters gets explicit about whether a parameter is in the path, query, or a header, making it clear to consumers where they can configure their request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters In Info",
"slug": "openapi-components-parameters-in-info",
"description": "Providing an in property for parameters gets explicit about whether a parameter is in the path, query, or a header, making it clear to consumers where they can configure their request",
"scope": "",
"property": "",
"type": "Providing an in property for parameters gets explicit about whether a parameter is in the path, query, or a header, making it clear to consumers where they can configure their request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Info",
"slug": "openapi-components-parameters-info",
"description": "Having a components parameters object allows all parameters used across an API to be centralized, allowing for reuse and easier governance of the parameters used to configure API requests",
"scope": "",
"property": "",
"type": "Having a components parameters object allows all parameters used across an API to be centralized, allowing for reuse and easier governance of the parameters used to configure API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Name Error",
"slug": "openapi-components-parameters-name-error",
"description": "Providing a simple, intuitive, and consistent names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"scope": "",
"property": "",
"type": "Providing a simple, intuitive, and consistent names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Name Info",
"slug": "openapi-components-parameters-name-info",
"description": "Providing a simple, intuitive, and consistent names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"scope": "",
"property": "",
"type": "Providing a simple, intuitive, and consistent names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default","Default"]
},{
"name": "OpenAPI Components Parameters Name Length Error",
"slug": "openapi-components-parameters-name-length-error",
"description": "Providing short and concise names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"scope": "",
"property": "",
"type": "Providing short and concise names for your parameters helps make it easier for API consumers to understand how they are able to configure their API requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Required Error",
"slug": "openapi-components-parameters-required-error",
"description": "Providrequiredg an required property for parameters gets explicit about whether a parameter is required the path, query, or a header, making it clear to consumers where they can configure their request",
"scope": "",
"property": "",
"type": "Providrequiredg an required property for parameters gets explicit about whether a parameter is required the path, query, or a header, making it clear to consumers where they can configure their request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Required Info",
"slug": "openapi-components-parameters-required-info",
"description": "Providrequiredg an required property for parameters gets explicit about whether a parameter is required the path, query, or a header, makrequiredg it clear to consumers where they can configure their request.",
"scope": "",
"property": "",
"type": "Providrequiredg an required property for parameters gets explicit about whether a parameter is required the path, query, or a header, makrequiredg it clear to consumers where they can configure their request.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Metadata","Default"]
},{
"name": "OpenAPI Components Parameters Schema Error",
"slug": "openapi-components-parameters-schema-error",
"description": "Parameters must always possess a schema to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"scope": "",
"property": "",
"type": "Parameters must always possess a schema to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Default"]
},{
"name": "OpenAPI Components Parameters Schema Info",
"slug": "openapi-components-parameters-schema-info",
"description": "Parameters must always possess a schema to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"scope": "",
"property": "",
"type": "Parameters must always possess a schema to help define the format and shape of the parameter, setting expections with consumers about what should be passed in",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Default"]
},{
"name": "OpenAPI Components Parameters Schema Items Array Error",
"slug": "openapi-components-parameters-schema-items-array-error",
"description": "Parameters that are of an array type should always have the items defined, being explicit about what is continued as part of the array",
"scope": "",
"property": "",
"type": "Parameters that are of an array type should always have the items defined, being explicit about what is continued as part of the array",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Items Array Info",
"slug": "openapi-components-parameters-schema-items-array-info",
"description": "Parameters that are of an array type should always have the items defined, being explicit about what is continued as part of the array",
"scope": "",
"property": "",
"type": "Parameters that are of an array type should always have the items defined, being explicit about what is continued as part of the array",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Ref Error",
"slug": "openapi-components-parameters-schema-ref-error",
"description": "Parameters must always use a schema reference that utilizes reusable schema that are defined as part of a centralized schema components library",
"scope": "",
"property": "",
"type": "Parameters must always use a schema reference that utilizes reusable schema that are defined as part of a centralized schema components library",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Default"]
},{
"name": "OpenAPI Components Parameters Schema Ref Info",
"slug": "openapi-components-parameters-schema-ref-info",
"description": "Parameters must always use a schema reference that utilizes reusable schema that are defined as part of a centralized schema components library",
"scope": "",
"property": "",
"type": "Parameters must always use a schema reference that utilizes reusable schema that are defined as part of a centralized schema components library",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Default"]
},{
"name": "OpenAPI Components Parameters Schema Type Error",
"slug": "openapi-components-parameters-schema-type-error",
"description": "Parameters must always have their schema type defined, being precise about what type of data can be inputted and used to configure an API request",
"scope": "",
"property": "",
"type": "Parameters must always have their schema type defined, being precise about what type of data can be inputted and used to configure an API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default"]
},{
"name": "OpenAPI Components Parameters Schema Type Info",
"slug": "openapi-components-parameters-schema-type-info",
"description": "Parameters must always have their schema type defined, being precise about what type of data can be inputted and used to configure an API request",
"scope": "",
"property": "",
"type": "Parameters must always have their schema type defined, being precise about what type of data can be inputted and used to configure an API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default"]
},{
"name": "OpenAPI Components Parameters Schema Type Integer Maximum Info",
"slug": "openapi-components-parameters-schema-type-integer-maximum-info",
"description": "Parameters that are of the integer schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the integer schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type Integer Maximum Warn",
"slug": "openapi-components-parameters-schema-type-integer-maximum-warn",
"description": "Parameters that are of the integer schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the integer schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type Integer Minimum Info",
"slug": "openapi-components-parameters-schema-type-integer-minimum-info",
"description": "Parameters that are of the integer schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the integer schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type Integer Minimum Warn",
"slug": "openapi-components-parameters-schema-type-integer-minimum-warn",
"description": "Parameters that are of the integer schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the integer schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Maxlength Info",
"slug": "openapi-components-parameters-schema-type-string-maxlength-info",
"description": "Parameters that are of the type string schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the type string schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Maxlength Warn",
"slug": "openapi-components-parameters-schema-type-string-maxlength-warn",
"description": "Parameters that are of the string schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the string schema type must have their maximum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Minlength Info",
"slug": "openapi-components-parameters-schema-type-string-minlength-info",
"description": "Parameters that are of the string schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the string schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Minlength Warn",
"slug": "openapi-components-parameters-schema-type-string-minlength-warn",
"description": "Parameters that are of the string schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the string schema type must have their minimum value set, defining the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Pattern Info",
"slug": "openapi-components-parameters-schema-type-string-pattern-info",
"description": "Parameters that are of the string schema type must have a pattern set, using a regex to define the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the string schema type must have a pattern set, using a regex to define the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Parameters Schema Type String Pattern Warn",
"slug": "openapi-components-parameters-schema-type-string-pattern-warn",
"description": "Parameters that are of the string schema type must have a pattern set, using a regex to define the shape of parameter data passed in with a request",
"scope": "",
"property": "",
"type": "Parameters that are of the string schema type must have a pattern set, using a regex to define the shape of parameter data passed in with a request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters","Schema","Type","Default","Security"]
},{
"name": "OpenAPI Components Responses Bad Request Error",
"slug": "openapi-components-responses-bad-request-error",
"description": "Having a bad request responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a bad request responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Bad Request Info",
"slug": "openapi-components-responses-bad-request-info",
"description": "Having a bad request responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a bad request responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Conflict Error",
"slug": "openapi-components-responses-conflict-error",
"description": "Having a conflict responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a conflict responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Conflict Info",
"slug": "openapi-components-responses-conflict-info",
"description": "Having a conflict responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a conflict responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Error",
"slug": "openapi-components-responses-error",
"description": "Utilizing the responses object in the centralized OpenAPI components library helps make responses reusable across API requests",
"scope": "",
"property": "",
"type": "Utilizing the responses object in the centralized OpenAPI components library helps make responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Responses Forbidden Error",
"slug": "openapi-components-responses-forbidden-error",
"description": "Having a forbidden responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a forbidden responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Forbidden Info",
"slug": "openapi-components-responses-forbidden-info",
"description": "Having a forbidden responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a forbidden responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Info",
"slug": "openapi-components-responses-info",
"description": "Utilizing the responses object in the centralized OpenAPI components library helps make responses reusable across API requests",
"scope": "",
"property": "",
"type": "Utilizing the responses object in the centralized OpenAPI components library helps make responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components"]
},{
"name": "OpenAPI Components Responses Internal Server Error Error",
"slug": "openapi-components-responses-internal-server-error-error",
"description": "Having a internal server error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a internal server error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Internal Server Error Info",
"slug": "openapi-components-responses-internal-server-error-info",
"description": "Having a internal server error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a internal server error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Not Found Error",
"slug": "openapi-components-responses-not-found-error",
"description": "Having a not found error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a not found error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Not Found Info",
"slug": "openapi-components-responses-not-found-info",
"description": "Having a not found error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a not found error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Too Many Requests Error",
"slug": "openapi-components-responses-too-many-requests-error",
"description": "Having a too many requests error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a too many requests error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Too Many Requests Info",
"slug": "openapi-components-responses-too-many-requests-info",
"description": "Having a too many requests error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a too many requests error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Unauthorized Error",
"slug": "openapi-components-responses-unauthorized-error",
"description": "Having a unauthorized error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a unauthorized error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Responses Unauthorized Info",
"slug": "openapi-components-responses-unauthorized-info",
"description": "Having a unauthorized error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"scope": "",
"property": "",
"type": "Having a unauthorized error responses in the centralized OpenAPI components library helps make error responses reusable across API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Components","Responses"]
},{
"name": "OpenAPI Components Schemas Error",
"slug": "openapi-components-schemas-error",
"description": "Utilizing the schema object in the centralized OpenAPI components library helps make schema reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing the schema object in the centralized OpenAPI components library helps make schema reusable across API requests and responses",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Default"]
},{
"name": "OpenAPI Components Schemas Info",
"slug": "openapi-components-schemas-info",
"description": "Utilizing the schema object in the centralized OpenAPI components library helps make schema reusable across API requests and responses",
"scope": "",
"property": "",
"type": "Utilizing the schema object in the centralized OpenAPI components library helps make schema reusable across API requests and responses",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Default"]
},{
"name": "OpenAPI External Docs Error",
"slug": "openapi-external-docs-error",
"description": "Having an external documentation link present in the OpenAPI for an API, makes it easy for API producers or consumers to find their way to the rest of the operations and resources available around an API",
"scope": "",
"property": "",
"type": "Having an external documentation link present in the OpenAPI for an API, makes it easy for API producers or consumers to find their way to the rest of the operations and resources available around an API",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","External Documentation","Default"]
},{
"name": "OpenAPI External Docs Info",
"slug": "openapi-external-docs-info",
"description": "Having an external documentation link present in the OpenAPI for an API, makes it easy for API producers or consumers to find their way to the rest of the operations and resources available around an API",
"scope": "",
"property": "",
"type": "Having an external documentation link present in the OpenAPI for an API, makes it easy for API producers or consumers to find their way to the rest of the operations and resources available around an API",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","External Documentation","Default"]
},{
"name": "OpenAPI Headers Hyphenated Pascal Case",
"slug": "openapi-headers-hyphenated-pascal-case-error",
"description": "HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.",
"scope": "",
"property": "",
"type": "HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Headers","Casing","Naming"]
},{
"name": "OpenAPI Info Contact Email Error",
"slug": "openapi-info-contact-email-error",
"description": "Having a contact email address associated with the technical contract ensures that anyone who comes across the API has someone to email and get more information",
"scope": "",
"property": "",
"type": "Having a contact email address associated with the technical contract ensures that anyone who comes across the API has someone to email and get more information",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Email Info",
"slug": "openapi-info-contact-email-info",
"description": "Having a contact email address associated with the technical contract ensures that anyone who comes across the API has someone to email and get more information",
"scope": "",
"property": "",
"type": "Having a contact email address associated with the technical contract ensures that anyone who comes across the API has someone to email and get more information",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Error",
"slug": "openapi-info-contact-error",
"description": "Having a contact object associated with the technical contract ensures that anyone who comes across the API has someone to contact and get more information",
"scope": "",
"property": "",
"type": "Having a contact object associated with the technical contract ensures that anyone who comes across the API has someone to contact and get more information",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Info",
"slug": "openapi-info-contact-info",
"description": "Having a contact object associated with the technical contract ensures that anyone who comes across the API has someone to contact and get more information",
"scope": "",
"property": "",
"type": "Having a contact object associated with the technical contract ensures that anyone who comes across the API has someone to contact and get more information",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Name Error",
"slug": "openapi-info-contact-name-error",
"description": "Having a contact name associated with the technical contract ensures that anyone who comes across the API knows who to contact",
"scope": "",
"property": "",
"type": "Having a contact name associated with the technical contract ensures that anyone who comes across the API knows who to contact",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Name Info",
"slug": "openapi-info-contact-name-info",
"description": "Having a contact name associated with the technical contract ensures that anyone who comes across the API knows who to contact",
"scope": "",
"property": "",
"type": "Having a contact name associated with the technical contract ensures that anyone who comes across the API knows who to contact",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Url Error",
"slug": "openapi-info-contact-url-error",
"description": "Having a contact url associated with the technical contract ensures that anyone who comes across the API knows where to go to contact someone",
"scope": "",
"property": "",
"type": "Having a contact url associated with the technical contract ensures that anyone who comes across the API knows where to go to contact someone",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Contact Url Info",
"slug": "openapi-info-contact-url-info",
"description": "Having a contact url associated with the technical contract ensures that anyone who comes across the API knows where to go to contact someone",
"scope": "",
"property": "",
"type": "Having a contact url associated with the technical contract ensures that anyone who comes across the API knows where to go to contact someone",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Contacts","Default"]
},{
"name": "OpenAPI Info Description Error",
"slug": "openapi-info-description-error",
"description": "Having a detailed description as part of the OpenAPI info object helps describe what a collection of paths and operations does for consumers, providing a short, concise, and relevant couple of paragraphs about the value that is represented as the OpenAPI",
"scope": "",
"property": "",
"type": "Having a detailed description as part of the OpenAPI info object helps describe what a collection of paths and operations does for consumers, providing a short, concise, and relevant couple of paragraphs about the value that is represented as the OpenAPI",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Eval Tag Error",
"slug": "openapi-info-description-eval-error",
"description": "Eval functions MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"scope": "",
"property": "",
"type": "Eval functions MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Eval Tag Info",
"slug": "openapi-info-description-eval-info",
"description": "Eval functions MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"scope": "",
"property": "",
"type": "Eval functions MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Info",
"slug": "openapi-info-description-info",
"description": "Having a detailed description as part of the OpenAPI info object helps describe what a collection of paths and operations does for consumers, providing a short, concise, and relevant couple of paragraphs about the value that is represented as the OpenAPI",
"scope": "",
"property": "",
"type": "Having a detailed description as part of the OpenAPI info object helps describe what a collection of paths and operations does for consumers, providing a short, concise, and relevant couple of paragraphs about the value that is represented as the OpenAPI",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Length Error",
"slug": "openapi-info-description-length-error",
"description": "Having a restriction on the length of the API description expressed as the OpenAPI info description helps provide constraints for consumers when adding a description, and keeps portals, landing pages, documentation, and discovery results more consistent",
"scope": "",
"property": "",
"type": "Having a restriction on the length of the API description expressed as the OpenAPI info description helps provide constraints for consumers when adding a description, and keeps portals, landing pages, documentation, and discovery results more consistent",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Script Tag Error",
"slug": "openapi-info-description-script-error",
"description": "Script tags MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"scope": "",
"property": "",
"type": "Script tags MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Description Script Tag Info",
"slug": "openapi-info-description-script-info",
"description": "Script tags MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"scope": "",
"property": "",
"type": "Script tags MUST not be included in the description of an API, keeping descriptions to just the text that is needed, and relying on the rest of the OpenAPI to describe what is possible.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Error",
"slug": "openapi-info-error",
"description": "Having an info object provides much of the metadata needed for the collection of APIs described in an OpenAPI",
"scope": "",
"property": "",
"type": "Having an info object provides much of the metadata needed for the collection of APIs described in an OpenAPI",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Default"]
},{
"name": "OpenAPI Info Info",
"slug": "openapi-info-info",
"description": "Having an info object provides much of the metadata needed for the collection of APIs described in an OpenAPI",
"scope": "",
"property": "",
"type": "Having an info object provides much of the metadata needed for the collection of APIs described in an OpenAPI",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Metadata","Default"]
},{
"name": "OpenAPI Info License Error",
"slug": "openapi-info-license-error",
"description": "Having a license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Identifier Cc By Nc Sa Error",
"slug": "openapi-info-license-identifier-cc-by-nc-sa-error",
"description": "Having a Create Commons CC BY NC SA license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a Create Commons CC BY NC SA license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Identifier Cc By Nc Sa Info",
"slug": "openapi-info-license-identifier-cc-by-nc-sa-info",
"description": "Having a Create Commons CC BY NC SA license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a Create Commons CC BY NC SA license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Identifier Error",
"slug": "openapi-info-license-identifier-error",
"description": "Having a license identifier associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license identifier associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Identifier Info",
"slug": "openapi-info-license-identifier-info",
"description": "Having a license identifier associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license identifier associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Info",
"slug": "openapi-info-license-info",
"description": "Having a license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Name Error",
"slug": "openapi-info-license-name-error",
"description": "Having a license name associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license name associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Name Info",
"slug": "openapi-info-license-name-info",
"description": "Having a license name associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license name associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Url Error",
"slug": "openapi-info-license-url-error",
"description": "Having a license url associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license url associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info License Url Info",
"slug": "openapi-info-license-url-info",
"description": "Having a license url associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a license url associated with an OpenAPI using the info licensing property ensures that the legal aspects of licensing the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info Terms Of Service Error",
"slug": "openapi-info-terms-of-service-error",
"description": "Having a terms of service associated with an OpenAPI using the info terms of service property ensures that the legal aspects of legal side of the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a terms of service associated with an OpenAPI using the info terms of service property ensures that the legal aspects of legal side of the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info Terms Of Service Info",
"slug": "openapi-info-terms-of-service-info",
"description": "Having a terms of service associated with an OpenAPI using the info terms of service property ensures that the legal aspects of legal side of the API always travel with the technical contract for an API",
"scope": "",
"property": "",
"type": "Having a terms of service associated with an OpenAPI using the info terms of service property ensures that the legal aspects of legal side of the API always travel with the technical contract for an API",
"guidance": "Legal",
"image": "",
"tags": ["OpenAPI","Metadata","Legal"]
},{
"name": "OpenAPI Info Title Error",
"slug": "openapi-info-title-error",
"description": "Having a intuitive and helpful title for your API using the OpenAPI info title is the first impression you will make on the consumers of your API",
"scope": "",
"property": "",
"type": "Having a intuitive and helpful title for your API using the OpenAPI info title is the first impression you will make on the consumers of your API",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Title Info",
"slug": "openapi-info-title-info",
"description": "Having a intuitive and helpful title for your API using the OpenAPI info title is the first impression you will make on the consumers of your API",
"scope": "",
"property": "",
"type": "Having a intuitive and helpful title for your API using the OpenAPI info title is the first impression you will make on the consumers of your API",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Title Length Error",
"slug": "openapi-info-title-length-error",
"description": "Having a limitation on the length of the title for your API helps provide constraints for teams naming it, but also keep consistent with other APIs from across teams",
"scope": "",
"property": "",
"type": "Having a limitation on the length of the title for your API helps provide constraints for teams naming it, but also keep consistent with other APIs from across teams",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Title Upper Case Error",
"slug": "openapi-info-title-upper-case-error",
"description": "Having a consistent casing for the title for your API helps provide constraints for teams naming the API, but also keep consistent with other APIs from across teams",
"scope": "",
"property": "",
"type": "Having a consistent casing for the title for your API helps provide constraints for teams naming the API, but also keep consistent with other APIs from across teams",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Title Upper Case Info",
"slug": "openapi-info-title-upper-case-info",
"description": "Having a consistent casing for the title for your API helps provide constraints for teams naming the API, but also keep consistent with other APIs from across teams",
"scope": "",
"property": "",
"type": "Having a consistent casing for the title for your API helps provide constraints for teams naming the API, but also keep consistent with other APIs from across teams",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Info Version Error",
"slug": "openapi-info-version-error",
"description": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property",
"scope": "",
"property": "",
"type": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Metadata","Versions","Default"]
},{
"name": "OpenAPI Info Version Info",
"slug": "openapi-info-version-info",
"description": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property",
"scope": "",
"property": "",
"type": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Metadata","Versions","Default"]
},{
"name": "OpenAPI Method DELETE Error",
"slug": "openapi-method-delete-error",
"description": "DELETE HTTP methods should be available.",
"scope": "",
"property": "",
"type": "DELETE HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","DELETE"]
},{
"name": "OpenAPI Method DELETE Info",
"slug": "openapi-method-delete-info",
"description": "DELETE HTTP methods should be available.",
"scope": "",
"property": "",
"type": "DELETE HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","DELETE"]
},{
"name": "OpenAPI Method GET Error",
"slug": "openapi-method-get-error",
"description": "GET HTTP methods should be available.",
"scope": "",
"property": "",
"type": "GET HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","GET"]
},{
"name": "OpenAPI Method GET Info",
"slug": "openapi-method-get-info",
"description": "GET HTTP methods should be available.",
"scope": "",
"property": "",
"type": "GET HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","GET"]
},{
"name": "OpenAPI Method POST Error",
"slug": "openapi-method-post-error",
"description": "POST HTTP methods should be available.",
"scope": "",
"property": "",
"type": "POST HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST"]
},{
"name": "OpenAPI Method POST Info",
"slug": "openapi-method-post-info",
"description": "POST HTTP methods should be available.",
"scope": "",
"property": "",
"type": "POST HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST"]
},{
"name": "OpenAPI Method PUT Error",
"slug": "openapi-method-put-error",
"description": "PUT HTTP methods should be available.",
"scope": "",
"property": "",
"type": "PUT HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT"]
},{
"name": "OpenAPI Method PUT Info",
"slug": "openapi-method-put-info",
"description": "PUT HTTP methods should be available.",
"scope": "",
"property": "",
"type": "PUT HTTP methods should be available.",
"guidance": "Standards",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT"]
},{
"name": "OpenAPI No Api In Path Error",
"slug": "openapi-no-api-in-path-error",
"description": "API paths must not contain a redundant "api" segment, since the fact that a resource is an API is already implied by the endpoint and adds no value.",
"scope": "",
"property": "",
"type": "API paths must not contain a redundant "api" segment, since the fact that a resource is an API is already implied by the endpoint and adds no value.",
"guidance": "Paths",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Api In Path Info",
"slug": "openapi-no-api-in-path-info",
"description": "API paths should not contain a redundant "api" segment, since the fact that a resource is an API is already implied by the endpoint and adds no value.",
"scope": "",
"property": "",
"type": "API paths should not contain a redundant "api" segment, since the fact that a resource is an API is already implied by the endpoint and adds no value.",
"guidance": "Paths",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Path Trailing Slash Error",
"slug": "openapi-no-path-trailing-slash-error",
"description": "API paths must not end with a trailing slash, avoiding ambiguous routing and duplicate representations of the same resource for API consumers.",
"scope": "",
"property": "",
"type": "API paths must not end with a trailing slash, avoiding ambiguous routing and duplicate representations of the same resource for API consumers.",
"guidance": "Paths",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Path Trailing Slash Info",
"slug": "openapi-no-path-trailing-slash-info",
"description": "API paths should not end with a trailing slash, avoiding ambiguous routing and duplicate representations of the same resource for API consumers.",
"scope": "",
"property": "",
"type": "API paths should not end with a trailing slash, avoiding ambiguous routing and duplicate representations of the same resource for API consumers.",
"guidance": "Paths",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Request Body On Delete Error",
"slug": "openapi-no-request-body-on-delete-error",
"description": "DELETE operations must not define a request body, since the resource to remove is identified by the path and a payload can be silently ignored by servers.",
"scope": "",
"property": "",
"type": "DELETE operations must not define a request body, since the resource to remove is identified by the path and a payload can be silently ignored by servers.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI No Request Body On Delete Info",
"slug": "openapi-no-request-body-on-delete-info",
"description": "DELETE operations should not define a request body, since the resource to remove is identified by the path and a payload can be silently ignored by servers.",
"scope": "",
"property": "",
"type": "DELETE operations should not define a request body, since the resource to remove is identified by the path and a payload can be silently ignored by servers.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI No Request Body On Get Error",
"slug": "openapi-no-request-body-on-get-error",
"description": "GET operations must not define a request body, keeping reads safe and cacheable and avoiding payloads that many clients and servers will ignore.",
"scope": "",
"property": "",
"type": "GET operations must not define a request body, keeping reads safe and cacheable and avoiding payloads that many clients and servers will ignore.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI No Request Body On Get Info",
"slug": "openapi-no-request-body-on-get-info",
"description": "GET operations should not define a request body, keeping reads safe and cacheable and avoiding payloads that many clients and servers will ignore.",
"scope": "",
"property": "",
"type": "GET operations should not define a request body, keeping reads safe and cacheable and avoiding payloads that many clients and servers will ignore.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI Operation Deprecated Sunset Info",
"slug": "openapi-operation-deprecated-sunset-info",
"description": "A deprecated operation should provide a Sunset response header so consumers know when the operation will be removed and can plan their migration. Pairing deprecation with a Sunset header makes the deprecation policy explicit and machine-readable.",
"scope": "",
"property": "",
"type": "A deprecated operation should provide a Sunset response header so consumers know when the operation will be removed and can plan their migration. Pairing deprecation with a Sunset header makes the deprecation policy explicit and machine-readable.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Deprecation"]
},{
"name": "OpenAPI Operation Description Agent Sufficient Warn",
"slug": "openapi-operation-description-agent-sufficient-warn",
"description": "Every operation should have a description long enough for an AI agent to understand what the operation does and call it correctly. Short or missing operation descriptions leave agents guessing about intent, inputs, and side effects, so descriptions should carry enough detail to be self-sufficient.",
"scope": "",
"property": "",
"type": "Every operation should have a description long enough for an AI agent to understand what the operation does and call it correctly. Short or missing operation descriptions leave agents guessing about intent, inputs, and side effects, so descriptions should carry enough detail to be self-sufficient.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Agents"]
},{
"name": "OpenAPI Operation Security Definitions Error",
"slug": "openapi-operation-security-definitions-error",
"description": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI",
"scope": "",
"property": "",
"type": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Operations","Security","Default"]
},{
"name": "OpenAPI Operation Security Definitions Info",
"slug": "openapi-operation-security-definitions-info",
"description": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI",
"scope": "",
"property": "",
"type": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Operations","Security","Default"]
},{
"name": "OpenAPI Operation Security Definitions API Keys Error",
"slug": "openapi-operation-security-definitions-keys-error",
"description": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI referencing apiKeys property.",
"scope": "",
"property": "",
"type": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI referencing apiKeys property.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Operations","Security","Default"]
},{
"name": "OpenAPI Operation Security Definitions API Keys Info",
"slug": "openapi-operation-security-definitions-keys-info",
"description": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI referencing apiKeys property.",
"scope": "",
"property": "",
"type": "Each API operation should have a security definition referencing the central security scheme express for an OpenAPI referencing apiKeys property.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Operations","Security","Default"]
},{
"name": "OpenAPI Operations Description Error",
"slug": "openapi-operations-description-error",
"description": "Having a paragraph or two description of each API operation helps API consumers understand what is possible with each API request",
"scope": "",
"property": "",
"type": "Having a paragraph or two description of each API operation helps API consumers understand what is possible with each API request",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Description Info",
"slug": "openapi-operations-description-info",
"description": "Having a paragraph or two description of each API operation helps API consumers understand what is possible with each API request",
"scope": "",
"property": "",
"type": "Having a paragraph or two description of each API operation helps API consumers understand what is possible with each API request",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Description Length Error",
"slug": "openapi-operations-description-length-error",
"description": "Having a length limitation for each description of each API operation helps apply constraints to how you describe your APIs, while helping drive consistency across APIs when it comes to search, documentation, and other ways an API is made available.",
"scope": "",
"property": "",
"type": "Having a length limitation for each description of each API operation helps apply constraints to how you describe your APIs, while helping drive consistency across APIs when it comes to search, documentation, and other ways an API is made available.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Operation Ids Camel Case Error",
"slug": "openapi-operations-operation-ids-camel-case-error",
"description": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Operation Ids Camel Case Info",
"slug": "openapi-operations-operation-ids-camel-case-info",
"description": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Operation Ids Special Characters Error",
"slug": "openapi-operations-operation-ids-characters-error",
"description": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Operation Ids Special Characters Info",
"slug": "openapi-operations-operation-ids-characters-info",
"description": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs.",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, and requiring them to have consistent casing reduces friction when generating SDKs and automating around APIs.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Operation Ids Error",
"slug": "openapi-operations-operation-ids-error",
"description": "Operation identifiers provide a unique way to identify each individual API, which then used for SDK generation and other automation",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, which then used for SDK generation and other automation",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations Operation Ids Info",
"slug": "openapi-operations-operation-ids-info",
"description": "Operation identifiers provide a unique way to identify each individual API, which then used for SDK generation and other automation",
"scope": "",
"property": "",
"type": "Operation identifiers provide a unique way to identify each individual API, which then used for SDK generation and other automation",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default"]
},{
"name": "OpenAPI Operations POST No Retrieve Verbs",
"slug": "openapi-operations-post-no-retrieve-verbs-error",
"description": "POST operations should not use verbs like retrieve, fetch, get, or read in their summaries. If data retrieval is the goal, a GET method should be used instead to follow RESTful conventions.",
"scope": "",
"property": "",
"type": "POST operations should not use verbs like retrieve, fetch, get, or read in their summaries. If data retrieval is the goal, a GET method should be used instead to follow RESTful conventions.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Operations","POST","REST","Design"]
},{
"name": "OpenAPI Operations Summary Error",
"slug": "openapi-operations-summary-error",
"description": "Having short and intuitive summary for each API operation helps API consumers understand what is possible with each API request",
"scope": "",
"property": "",
"type": "Having short and intuitive summary for each API operation helps API consumers understand what is possible with each API request",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Summary Info",
"slug": "openapi-operations-summary-info",
"description": "Having short and intuitive summary for each API operation helps API consumers understand what is possible with each API request",
"scope": "",
"property": "",
"type": "Having short and intuitive summary for each API operation helps API consumers understand what is possible with each API request",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Summary Length Error",
"slug": "openapi-operations-summary-length-error",
"description": "Apply length constraints to the operation summary helps keep them consistent for publishing in documentation",
"scope": "",
"property": "",
"type": "Apply length constraints to the operation summary helps keep them consistent for publishing in documentation",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Summary Period Error",
"slug": "openapi-operations-summary-period-none-error",
"description": "Operation summaries should not have a period, keeping the primary summary for each API as consistent as possible for publishing in documentation",
"scope": "",
"property": "",
"type": "Operation summaries should not have a period, keeping the primary summary for each API as consistent as possible for publishing in documentation",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Summary Period Info",
"slug": "openapi-operations-summary-period-none-info",
"description": "Operation summaries should not have a period, keeping the primary summary foreach API as consistent as possible for publishing in documentation.",
"scope": "",
"property": "",
"type": "Operation summaries should not have a period, keeping the primary summary foreach API as consistent as possible for publishing in documentation.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Operations","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Operations Tags Error",
"slug": "openapi-operations-tags-error",
"description": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"scope": "",
"property": "",
"type": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Tags","Default","Documentation"]
},{
"name": "OpenAPI Operations Tags Info",
"slug": "openapi-operations-tags-info",
"description": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"scope": "",
"property": "",
"type": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Tags","Default","Documentation"]
},{
"name": "OpenAPI Operations Tags One Error",
"slug": "openapi-operations-tags-one-error",
"description": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"scope": "",
"property": "",
"type": "Having tags applied to each API operations helps organize and group APIs in portals, documentation, search, and other ways in which APIs are made available",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Tags","Default","Documentation"]
},{
"name": "OpenAPI Operations Tags Upper Case Error",
"slug": "openapi-operations-tags-upper-case-error",
"description": "Having the first letter of each word applied as a tag to API operations helps keep a consistent layout when published via search, documentation, and other ways APIs are made available",
"scope": "",
"property": "",
"type": "Having the first letter of each word applied as a tag to API operations helps keep a consistent layout when published via search, documentation, and other ways APIs are made available",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Tags","Default","Documentation"]
},{
"name": "OpenAPI Operations Tags Upper Case Info",
"slug": "openapi-operations-tags-upper-case-info",
"description": "Having the first letter of each word applied as a tag to API operations helps keep a consistent layout when published via search, documentation, and other ways APIs are made available",
"scope": "",
"property": "",
"type": "Having the first letter of each word applied as a tag to API operations helps keep a consistent layout when published via search, documentation, and other ways APIs are made available",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Operations","Tags","Default","Documentation"]
},{
"name": "OpenAPI Parameters Componentized Error",
"slug": "openapi-parameters-componentized-error",
"description": "Having all parameters using the central OpenAPI components parameters object helps increase the reusability of parameters across API operations, but it also help standardize parameter across all APIs",
"scope": "",
"property": "",
"type": "Having all parameters using the central OpenAPI components parameters object helps increase the reusability of parameters across API operations, but it also help standardize parameter across all APIs",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters"]
},{
"name": "OpenAPI Parameters Componentized Info",
"slug": "openapi-parameters-componentized-info",
"description": "Having all parameters using the central OpenAPI components parameters object helps increase the reusability of parameters across API operations, but it also help standardize parameter across all APIs",
"scope": "",
"property": "",
"type": "Having all parameters using the central OpenAPI components parameters object helps increase the reusability of parameters across API operations, but it also help standardize parameter across all APIs",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Components","Parameters"]
},{
"name": "OpenAPI Parameters Optional Examples",
"slug": "openapi-parameters-optional-examples-info",
"description": "Optional parameters should include examples to support API mocking, testing, and documentation. While not strictly required, examples help consumers understand the range of acceptable values.",
"scope": "",
"property": "",
"type": "Optional parameters should include examples to support API mocking, testing, and documentation. While not strictly required, examples help consumers understand the range of acceptable values.",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","Parameters","Examples","Mocking"]
},{
"name": "OpenAPI Parameters Required Examples",
"slug": "openapi-parameters-required-examples-warn",
"description": "Required parameters should include examples to support API mocking, testing, and documentation. Examples help consumers understand expected values and enable tools like Microcks to generate realistic mock responses.",
"scope": "",
"property": "",
"type": "Required parameters should include examples to support API mocking, testing, and documentation. Examples help consumers understand expected values and enable tools like Microcks to generate realistic mock responses.",
"guidance": "Documentation",
"image": "",
"tags": ["OpenAPI","Parameters","Examples","Mocking"]
},{
"name": "OpenAPI Paths API",
"slug": "openapi-paths-apis-error",
"description": "There are very few situations where you actually want the acronym API in the path of your API, only when it is a resource.",
"scope": "",
"property": "",
"type": "There are very few situations where you actually want the acronym API in the path of your API, only when it is a resource.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Api In Path Info",
"slug": "openapi-paths-api-info",
"description": "There are very few situations where you actually want the acronym API in the path of your API, only when it is a resource.",
"scope": "",
"property": "",
"type": "There are very few situations where you actually want the acronym API in the path of your API, only when it is a resource.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI Path Declarations Error",
"slug": "openapi-paths-declarations-error",
"description": "There must be a paths property and have paths declared, providing the minimum viable definition for an API.",
"scope": "",
"property": "",
"type": "There must be a paths property and have paths declared, providing the minimum viable definition for an API.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI Path Declarations Info",
"slug": "openapi-paths-declarations-info",
"description": "There must be a paths property and have paths declared, providing the minimum viable definition for an API.",
"scope": "",
"property": "",
"type": "There must be a paths property and have paths declared, providing the minimum viable definition for an API.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI Path Kebab Case",
"slug": "openapi-paths-query-error",
"description": "Path segments should be kebab case and not have different casing that could cause other problems.",
"scope": "",
"property": "",
"type": "Path segments should be kebab case and not have different casing that could cause other problems.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Casing","Default"]
},{
"name": "OpenAPI Path Kebab Case",
"slug": "openapi-paths-query-info",
"description": "The query delimiter should not be included as part of any API path.",
"scope": "",
"property": "",
"type": "The query delimiter should not be included as part of any API path.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Casing","Default"]
},{
"name": "OpenAPI Paths No Verbs",
"slug": "openapi-paths-no-verbs-warn",
"description": "RESTful API path segments should not contain action verbs. HTTP methods already convey the action, so verbs in paths indicate a non-RESTful design. Paths should describe resources, not actions.",
"scope": "",
"property": "",
"type": "RESTful API path segments should not contain action verbs. HTTP methods already convey the action, so verbs in paths indicate a non-RESTful design. Paths should describe resources, not actions.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","REST","Design"]
},{
"name": "OpenAPI Path Parameters Camel Case",
"slug": "openapi-paths-parameters-camel-case-warn",
"description": "Path parameters should follow camelCase naming convention for consistency across the API, making parameter names predictable and aligned with common programming conventions.",
"scope": "",
"property": "",
"type": "Path parameters should follow camelCase naming convention for consistency across the API, making parameter names predictable and aligned with common programming conventions.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Parameters","Casing"]
},{
"name": "OpenAPI Path Query",
"slug": "openapi-paths-query-error",
"description": "The query delimiter should not be included as part of any API path.",
"scope": "",
"property": "",
"type": "The query delimiter should not be included as part of any API path.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Api In Path Info",
"slug": "openapi-paths-query-info",
"description": "The query delimiter should not be included as part of any API path.",
"scope": "",
"property": "",
"type": "The query delimiter should not be included as part of any API path.",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Path Trailing Slash Error",
"slug": "openapi-no-path-trailing-slash-error",
"description": "It is common to be explicit and consistent about whether or not to have a trailing slack on each API path",
"scope": "",
"property": "",
"type": "It is common to be explicit and consistent about whether or not to have a trailing slack on each API path",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI No Path Trailing Slash Info",
"slug": "openapi-no-path-trailing-slash-info",
"description": "It is common to be explicit and consistent about whether or not to have a trailing slack on each API path",
"scope": "",
"property": "",
"type": "It is common to be explicit and consistent about whether or not to have a trailing slack on each API path",
"guidance": "Naming",
"image": "",
"tags": ["OpenAPI","Paths","Default"]
},{
"name": "OpenAPI Request Body Have Application Json Info",
"slug": "openapi-request-bodies-application-json-info",
"description": "Request bodies use the application/json media type to encode the request payload is a common data format",
"scope": "",
"property": "",
"type": "Request bodies use the application/json media type to encode the request payload is a common data format",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Media Types"]
},{
"name": "OpenAPI Request Body Have Application X Www Form Url Encoded Info",
"slug": "openapi-request-bodies-application-x-www-form-url-encoded-info",
"description": "Request bodies use the application/x-www-form-urlencoded media type to encode the request payload is a common data format",
"scope": "",
"property": "",
"type": "Request bodies use the application/x-www-form-urlencoded media type to encode the request payload is a common data format",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Media Types"]
},{
"name": "OpenAPI Request Body Content On Post Error",
"slug": "openapi-request-bodies-content-post-error",
"description": "POST requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"scope": "",
"property": "",
"type": "POST requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST"]
},{
"name": "OpenAPI Request Body Content On Post Info",
"slug": "openapi-request-bodies-content-post-info",
"description": "POST requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"scope": "",
"property": "",
"type": "POST requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST"]
},{
"name": "OpenAPI Request Body Content On Put Error",
"slug": "openapi-request-bodies-content-put-error",
"description": "PUT requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"scope": "",
"property": "",
"type": "PUT requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT"]
},{
"name": "OpenAPI Request Body Content On Put Info",
"slug": "openapi-request-body-content-on-put-info",
"description": "PUT requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"scope": "",
"property": "",
"type": "PUT requests with a request body should have content defined, providing more detail on what is contained within the API request body",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT"]
},{
"name": "OpenAPI No Request Body On Delete Error",
"slug": "openapi-request-bodies-delete-error",
"description": "DELETE HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"scope": "",
"property": "",
"type": "DELETE HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","DELETE","Default"]
},{
"name": "OpenAPI No Request Body On Delete Info",
"slug": "openapi-request-bodies-delete-info",
"description": "DELETE HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"scope": "",
"property": "",
"type": "DELETE HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","DELETE","Default"]
},{
"name": "OpenAPI Request Bodies Description Error",
"slug": "openapi-request-bodies-description-error",
"description": "It is helpful to provide a description for request bodies, providing a simple explanation of what can be configured as part of the request payload",
"scope": "",
"property": "",
"type": "It is helpful to provide a description for request bodies, providing a simple explanation of what can be configured as part of the request payload",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Metadata"]
},{
"name": "OpenAPI Request Bodies Description Info",
"slug": "openapi-request-bodies-description-info",
"description": "It is helpful to provide a description for request bodies, providing a simple explanation of what can be configured as part of the request payload",
"scope": "",
"property": "",
"type": "It is helpful to provide a description for request bodies, providing a simple explanation of what can be configured as part of the request payload",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Metadata"]
},{
"name": "OpenAPI Request Bodies Examples Content",
"slug": "openapi-request-bodies-examples-content-warn",
"description": "Request body content should include examples to support API mocking, testing, and documentation. Examples enable tools to generate realistic mock requests and help consumers understand expected payloads.",
"scope": "",
"property": "",
"type": "Request body content should include examples to support API mocking, testing, and documentation. Examples enable tools to generate realistic mock requests and help consumers understand expected payloads.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Examples","Mocking"]
},{
"name": "OpenAPI Request Body Have Examples Error",
"slug": "openapi-request-bodies-examples-error",
"description": "POST, PUT, and PATCH request bodies should have examples, providing one or more examples of what should be submitted for different types of requests",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have examples, providing one or more examples of what should be submitted for different types of requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Examples"]
},{
"name": "OpenAPI Request Body Have Examples Info",
"slug": "openapi-request-bodies-examples-info",
"description": "POST, PUT, and PATCH request bodies should have examples, providing one or more examples of what should be submitted for different types of requests",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have examples, providing one or more examples of what should be submitted for different types of requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Examples"]
},{
"name": "OpenAPI Request Body Have Examples Ref Error",
"slug": "openapi-request-bodies-examples-ref-error",
"description": "POST, PUT, and PATCH request bodies should have examples using references to centralized component examples, providing one or more examples of what should be submitted for different types of requests",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have examples using references to centralized component examples, providing one or more examples of what should be submitted for different types of requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Examples"]
},{
"name": "OpenAPI Request Body Have Examples Ref Info",
"slug": "openapi-request-bodies-examples-ref-info",
"description": "POST, PUT, and PATCH request bodies should have examples using references to centralized component examples, providing one or more examples of what should be submitted for different types of requests",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have examples using references to centralized component examples, providing one or more examples of what should be submitted for different types of requests",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Examples"]
},{
"name": "OpenAPI No Request Body On Get Error",
"slug": "openapi-request-bodies-get-error",
"description": "GET HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"scope": "",
"property": "",
"type": "GET HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","GET","Default"]
},{
"name": "OpenAPI No Request Body On Get Info",
"slug": "openapi-request-bodies-get-info",
"description": "GET HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"scope": "",
"property": "",
"type": "GET HTTP methods should not have a request body, keeping API requests compliant with the HTTP standard",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","GET","Default"]
},{
"name": "OpenAPI Request Bodies PATCH Merge Patch",
"slug": "openapi-request-bodies-patch-merge-patch-info",
"description": "PATCH operations should use application/merge-patch+json content type as defined in RFC 7396, providing a standardized approach for partial updates to resources.",
"scope": "",
"property": "",
"type": "PATCH operations should use application/merge-patch+json content type as defined in RFC 7396, providing a standardized approach for partial updates to resources.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","PATCH","Content Type"]
},{
"name": "OpenAPI Request Body On Post Error",
"slug": "openapi-request-body-on-post-error",
"description": "POST HTTP methods can have a request body, providing a structured payload for configuring each API request",
"scope": "",
"property": "",
"type": "POST HTTP methods can have a request body, providing a structured payload for configuring each API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST","Default"]
},{
"name": "OpenAPI Request Body On Post Info",
"slug": "openapi-request-body-on-post-info",
"description": "POST HTTP methods can have a request body, providing a structured payload for configuring each API request",
"scope": "",
"property": "",
"type": "POST HTTP methods can have a request body, providing a structured payload for configuring each API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","POST","Default"]
},{
"name": "OpenAPI Request Body On Put Error Info",
"slug": "openapi-request-bodies-put-error",
"description": "PUT HTTP methods can have a request body, providing a structured payload for configuring each API request",
"scope": "",
"property": "",
"type": "PUT HTTP methods can have a request body, providing a structured payload for configuring each API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT","Default"]
},{
"name": "OpenAPI Request Body On Put Info",
"slug": "openapi-request-bodies-put-info",
"description": "PUT HTTP methods can have a request body, providing a structured payload for configuring each API request",
"scope": "",
"property": "",
"type": "PUT HTTP methods can have a request body, providing a structured payload for configuring each API request",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","PUT","Default"]
},{
"name": "OpenAPI Request Bodies Required Property Error",
"slug": "openapi-request-bodies-required-property-error",
"description": "It is important to be explicit about whether or not the request body for an API operation is required or not",
"scope": "",
"property": "",
"type": "It is important to be explicit about whether or not the request body for an API operation is required or not",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Metadata","Required"]
},{
"name": "OpenAPI Request Bodies Required Property Info",
"slug": "openapi-request-bodies-required-property-info",
"description": "It is important to be explicit about whether or not the request body for an API operation is required or not",
"scope": "",
"property": "",
"type": "It is important to be explicit about whether or not the request body for an API operation is required or not",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Metadata","Required"]
},{
"name": "OpenAPI Request Body Have Schema Error",
"slug": "openapi-request-bodies-schema-error",
"description": "POST, PUT, and PATCH request bodies should have schema defined, providing more detail on what the structure of the API request body should be",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have schema defined, providing more detail on what the structure of the API request body should be",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Schema"]
},{
"name": "OpenAPI Request Body Have Schema Info",
"slug": "openapi-request-bodies-schema-info",
"description": "POST, PUT, and PATCH request bodies should have schema defined, providing more detail on what the structure of the API request body should be",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have schema defined, providing more detail on what the structure of the API request body should be",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Schema"]
},{
"name": "OpenAPI Request Body Have Schema Ref Error",
"slug": "openapi-request-bodies-schema-ref-error",
"description": "POST, PUT, and PATCH request bodies should have schema reference defined, providing more detail on what the structure of the API request body should be",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have schema reference defined, providing more detail on what the structure of the API request body should be",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Schema"]
},{
"name": "OpenAPI Request Body Have Schema Ref Info",
"slug": "openapi-request-bodies-schema-ref-info",
"description": "POST, PUT, and PATCH request bodies should have schema reference defined, providing more detail on what the structure of the API request body should be",
"scope": "",
"property": "",
"type": "POST, PUT, and PATCH request bodies should have schema reference defined, providing more detail on what the structure of the API request body should be",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Request Bodies","Schema"]
},{
"name": "OpenAPI Request Body Content On Post Error",
"slug": "openapi-request-body-content-on-post-error",
"description": "A POST request body must define its content so that consumers know which media types and schemas are expected when creating a resource.",
"scope": "",
"property": "",
"type": "A POST request body must define its content so that consumers know which media types and schemas are expected when creating a resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Operations","Default"]
},{
"name": "OpenAPI Request Body Content On Post Info",
"slug": "openapi-request-body-content-on-post-info",
"description": "A POST request body should define its content so that consumers know which media types and schemas are expected when creating a resource.",
"scope": "",
"property": "",
"type": "A POST request body should define its content so that consumers know which media types and schemas are expected when creating a resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Operations","Default"]
},{
"name": "OpenAPI Request Body Content On Put Error",
"slug": "openapi-request-body-content-on-put-error",
"description": "A PUT request body must define its content so that consumers know which media types and schemas are expected when replacing a resource.",
"scope": "",
"property": "",
"type": "A PUT request body must define its content so that consumers know which media types and schemas are expected when replacing a resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Operations","Default"]
},{
"name": "OpenAPI Request Body Content On Put Info",
"slug": "openapi-request-body-content-on-put-info",
"description": "A PUT request body should define its content so that consumers know which media types and schemas are expected when replacing a resource.",
"scope": "",
"property": "",
"type": "A PUT request body should define its content so that consumers know which media types and schemas are expected when replacing a resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Operations","Default"]
},{
"name": "OpenAPI Request Body Have Application JSON Info",
"slug": "openapi-request-body-have-application-json-info",
"description": "Request bodies should offer an application/json media type so that consumers have a predictable, widely supported content type for sending data to the API.",
"scope": "",
"property": "",
"type": "Request bodies should offer an application/json media type so that consumers have a predictable, widely supported content type for sending data to the API.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Application X WWW Form URL Encoded Info",
"slug": "openapi-request-body-have-application-x-www-form-url-encoded-info",
"description": "Request bodies may offer an application/x-www-form-urlencoded media type to support form-style submissions alongside other supported content types.",
"scope": "",
"property": "",
"type": "Request bodies may offer an application/x-www-form-urlencoded media type to support form-style submissions alongside other supported content types.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Examples Error",
"slug": "openapi-request-body-have-examples-error",
"description": "Request body media types should provide examples so that consumers can understand the expected payload structure and values when calling the API.",
"scope": "",
"property": "",
"type": "Request body media types should provide examples so that consumers can understand the expected payload structure and values when calling the API.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Examples Info",
"slug": "openapi-request-body-have-examples-info",
"description": "Request body media types should provide examples so that consumers can understand the expected payload structure and values when calling the API.",
"scope": "",
"property": "",
"type": "Request body media types should provide examples so that consumers can understand the expected payload structure and values when calling the API.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Examples Ref Error",
"slug": "openapi-request-body-have-examples-ref-error",
"description": "Request body examples should be defined as $ref references to a centralized examples library so that they can be reused and maintained consistently.",
"scope": "",
"property": "",
"type": "Request body examples should be defined as $ref references to a centralized examples library so that they can be reused and maintained consistently.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Examples Ref Info",
"slug": "openapi-request-body-have-examples-ref-info",
"description": "Request body examples should be defined as $ref references to a centralized examples library so that they can be reused and maintained consistently.",
"scope": "",
"property": "",
"type": "Request body examples should be defined as $ref references to a centralized examples library so that they can be reused and maintained consistently.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body Have Schema Error",
"slug": "openapi-request-body-have-schema-error",
"description": "Request body media types must define a schema so that the structure of the expected payload is documented and can be validated by consumers and tooling.",
"scope": "",
"property": "",
"type": "Request body media types must define a schema so that the structure of the expected payload is documented and can be validated by consumers and tooling.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Schema","Default"]
},{
"name": "OpenAPI Request Body Have Schema Info",
"slug": "openapi-request-body-have-schema-info",
"description": "Request body media types must define a schema so that the structure of the expected payload is documented and can be validated by consumers and tooling.",
"scope": "",
"property": "",
"type": "Request body media types must define a schema so that the structure of the expected payload is documented and can be validated by consumers and tooling.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Schema","Default"]
},{
"name": "OpenAPI Request Body Have Schema Ref Error",
"slug": "openapi-request-body-have-schema-ref-error",
"description": "Request body schemas should be defined as $ref references to a centralized schema library so that data models are reused and maintained consistently.",
"scope": "",
"property": "",
"type": "Request body schemas should be defined as $ref references to a centralized schema library so that data models are reused and maintained consistently.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Schema","Default"]
},{
"name": "OpenAPI Request Body Have Schema Ref Info",
"slug": "openapi-request-body-have-schema-ref-info",
"description": "Request body schemas should be defined as $ref references to a centralized schema library so that data models are reused and maintained consistently.",
"scope": "",
"property": "",
"type": "Request body schemas should be defined as $ref references to a centralized schema library so that data models are reused and maintained consistently.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","RequestBodies","Schema","Default"]
},{
"name": "OpenAPI Request Body On Post Error",
"slug": "openapi-request-body-on-post-error",
"description": "POST operations should define a request body, since creating a resource almost always requires the consumer to submit a representation of that new resource.",
"scope": "",
"property": "",
"type": "POST operations should define a request body, since creating a resource almost always requires the consumer to submit a representation of that new resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body On Post Info",
"slug": "openapi-request-body-on-post-info",
"description": "POST operations should define a request body, since creating a resource almost always requires the consumer to submit a representation of that new resource.",
"scope": "",
"property": "",
"type": "POST operations should define a request body, since creating a resource almost always requires the consumer to submit a representation of that new resource.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body On Put Error Info",
"slug": "openapi-request-body-on-put-error-info",
"description": "PUT operations should define a requestBody because they typically replace a resource and require the client to send the representation being stored.",
"scope": "",
"property": "",
"type": "PUT operations should define a requestBody because they typically replace a resource and require the client to send the representation being stored.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI Request Body On Put Info",
"slug": "openapi-request-body-on-put-info",
"description": "PUT operations should define a requestBody because they typically replace a resource and require the client to send the representation being stored.",
"scope": "",
"property": "",
"type": "PUT operations should define a requestBody because they typically replace a resource and require the client to send the representation being stored.",
"guidance": "Request Bodies",
"image": "",
"tags": ["OpenAPI","Operations","RequestBodies","Default"]
},{
"name": "OpenAPI Response Cache Control Info",
"slug": "openapi-response-cache-control-info",
"description": "Successful GET responses should set a Cache-Control header so consumers, proxies, and CDNs know how to cache the response. Declaring caching behavior improves performance and predictability for read operations across the API.",
"scope": "",
"property": "",
"type": "Successful GET responses should set a Cache-Control header so consumers, proxies, and CDNs know how to cache the response. Declaring caching behavior improves performance and predictability for read operations across the API.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Responses","Performance"]
},{
"name": "OpenAPI Response Content Examples",
"slug": "openapi-response-content-examples-warn",
"description": "Response content should include examples to support API mocking, testing, and documentation. Examples enable tools to generate realistic mock responses and help consumers understand what to expect.",
"scope": "",
"property": "",
"type": "Response content should include examples to support API mocking, testing, and documentation. Examples enable tools to generate realistic mock responses and help consumers understand what to expect.",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Examples","Mocking"]
},{
"name": "OpenAPI Response Delete 204 No Body Error",
"slug": "openapi-response-delete-204-no-body-error",
"description": "A DELETE operation that returns a 204 No Content response must not define response content, as a 204 status code indicates there is no body to return.",
"scope": "",
"property": "",
"type": "A DELETE operation that returns a 204 No Content response must not define response content, as a 204 status code indicates there is no body to return.",
"guidance": "Responses",
"image": "",
"tags": ["OpenAPI","Responses","Default"]
},{
"name": "OpenAPI Response Delete 204 Status Code Error",
"slug": "openapi-response-delete-204-status-code-error",
"description": "DELETE responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","2xx","Default"]
},{
"name": "OpenAPI Response Delete 204 Status Code Info",
"slug": "openapi-response-delete-204-status-code-info",
"description": "DELETE responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","2xx","Default"]
},{
"name": "OpenAPI Response Delete 400 Schema Ref Error",
"slug": "openapi-response-delete-400-schema-ref-error",
"description": "DELETE 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 400 Schema Ref Info",
"slug": "openapi-response-delete-400-schema-ref-info",
"description": "DELETE 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 400 Status Code Error",
"slug": "openapi-response-delete-400-status-code-error",
"description": "DELETE responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 400 Status Code Info",
"slug": "openapi-response-delete-400-status-code-info",
"description": "DELETE responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 401 Schema Ref Error",
"slug": "openapi-response-delete-401-schema-ref-error",
"description": "DELETE 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 401 Schema Ref Info",
"slug": "openapi-response-delete-401-schema-ref-info",
"description": "DELETE 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 401 Status Code Error",
"slug": "openapi-response-delete-401-status-code-error",
"description": "DELETE responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "DELETE responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 401 Status Code Info",
"slug": "openapi-response-delete-401-status-code-info",
"description": "DELETE responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "DELETE responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 403 Schema Ref Error",
"slug": "openapi-response-delete-403-schema-ref-error",
"description": "DELETE 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 403 Schema Ref Info",
"slug": "openapi-response-delete-403-schema-ref-info",
"description": "DELETE 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 403 Status Code Error",
"slug": "openapi-response-delete-403-status-code-error",
"description": "DELETE responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "DELETE responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 403 Status Code Info",
"slug": "openapi-response-delete-403-status-code-info",
"description": "DELETE responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "DELETE responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 404 Schema Ref Error",
"slug": "openapi-response-delete-404-schema-ref-error",
"description": "DELETE 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx","Default"]
},{
"name": "OpenAPI Response Delete 404 Schema Ref Info",
"slug": "openapi-response-delete-404-schema-ref-info",
"description": "DELETE 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx","Default"]
},{
"name": "OpenAPI Response Delete 404 Status Code Error",
"slug": "openapi-response-delete-404-status-code-error",
"description": "DELETE responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 404 Status Code Info",
"slug": "openapi-response-delete-404-status-code-info",
"description": "DELETE responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 429 Schema Ref Error",
"slug": "openapi-response-delete-429-schema-ref-error",
"description": "DELETE 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 429 Schema Ref Info",
"slug": "openapi-response-delete-429-schema-ref-info",
"description": "DELETE 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 429 Status Code Error",
"slug": "openapi-response-delete-429-status-code-error",
"description": "DELETE responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "DELETE responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 429 Status Code Info",
"slug": "openapi-response-delete-429-status-code-info",
"description": "DELETE responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "DELETE responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","4xx"]
},{
"name": "OpenAPI Response Delete 500 Schema Ref Error",
"slug": "openapi-response-delete-500-schema-ref-error",
"description": "DELETE 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","5xx"]
},{
"name": "OpenAPI Response Delete 500 Schema Ref Info",
"slug": "openapi-response-delete-500-schema-ref-info",
"description": "DELETE 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "DELETE 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","5xx"]
},{
"name": "OpenAPI Response Delete 500 Status Code Error",
"slug": "openapi-response-delete-500-status-code-error",
"description": "DELETE responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","5xx","Default"]
},{
"name": "OpenAPI Response Delete 500 Status Code Info",
"slug": "openapi-response-delete-500-status-code-info",
"description": "DELETE responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "DELETE responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","DELETE","5xx","Default"]
},{
"name": "OpenAPI Response Error Problem JSON",
"slug": "openapi-response-error-problem-json-info",
"description": "Error responses (4XX and 5XX) should use application/problem+json media type as defined in RFC 7807, providing a consistent, machine-readable format for conveying error details to API consumers.",
"scope": "",
"property": "",
"type": "Error responses (4XX and 5XX) should use application/problem+json media type as defined in RFC 7807, providing a consistent, machine-readable format for conveying error details to API consumers.",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Errors","Problem JSON"]
},{
"name": "OpenAPI Response Examples Error",
"slug": "openapi-response-examples-error",
"description": "Have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Examples"]
},{
"name": "OpenAPI Response Examples Info",
"slug": "openapi-response-examples-info",
"description": "Have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Examples"]
},{
"name": "OpenAPI Response Examples Ref Error",
"slug": "openapi-response-examples-ref-error",
"description": "Have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Examples"]
},{
"name": "OpenAPI Response Examples Ref Info",
"slug": "openapi-response-examples-ref-error",
"description": "Have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Examples"]
},{
"name": "OpenAPI Response Get 200 Content Error",
"slug": "openapi-response-get-200-content-error",
"description": "GET 200 success HTTP status codes should have content property that provides the ability to describe the response content",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes should have content property that provides the ability to describe the response content",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx"]
},{
"name": "OpenAPI Response Get 200 Content Info",
"slug": "openapi-response-get-200-content-info",
"description": "GET 200 success HTTP status codes should have content property that provides the ability to describe the response content",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes should have content property that provides the ability to describe the response content",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx"]
},{
"name": "OpenAPI Response Get 200 Description Error",
"slug": "openapi-response-get-200-description-error",
"description": "GET 200 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx"]
},{
"name": "OpenAPI Response Get 200 Description Info",
"slug": "openapi-response-get-200-description-info",
"description": "GET 200 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx"]
},{
"name": "OpenAPI Response Get 200 Media Type Error",
"slug": "openapi-response-get-200-media-type-error",
"description": "GET 200 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types"]
},{
"name": "OpenAPI Response Get 200 Media Type Examples Error",
"slug": "openapi-response-get-200-media-type-examples-error",
"description": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Examples"]
},{
"name": "OpenAPI Response Get 200 Media Type Examples Info",
"slug": "openapi-response-get-200-media-type-examples-info",
"description": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Examples"]
},{
"name": "OpenAPI Response Get 200 Media Type Examples Ref Error",
"slug": "openapi-response-get-200-media-type-examples-ref-error",
"description": "GET 200 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Examples"]
},{
"name": "OpenAPI Response Get 200 Media Type Examples Ref Info",
"slug": "openapi-response-get-200-media-type-examples-ref-info",
"description": "GET 200 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Examples"]
},{
"name": "OpenAPI Response Get 200 Media Type Info",
"slug": "openapi-response-get-200-media-type-info",
"description": "GET 200 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types"]
},{
"name": "OpenAPI Response Get 200 Media Type Schema Error",
"slug": "openapi-response-get-200-media-type-schema-error",
"description": "GET 200 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Get 200 Media Type Schema Info",
"slug": "openapi-response-get-200-media-type-schema-info",
"description": "GET 200 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Get 200 Media Type Schema Ref Error",
"slug": "openapi-response-get-200-media-type-schema-ref-error",
"description": "GET 200 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Get 200 Media Type Schema Ref Info",
"slug": "openapi-response-get-200-media-type-schema-ref-info",
"description": "GET 200 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Get 200 Status Code Error",
"slug": "openapi-response-get-200-status-code-error",
"description": "GET responses should have a 200 success HTTP status codes, communicating a successful response to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 200 success HTTP status codes, communicating a successful response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Default"]
},{
"name": "OpenAPI Response Get 200 Status Code Info",
"slug": "openapi-response-get-200-status-code-info",
"description": "GET responses should have a 200 success HTTP status codes, communicating a successful response to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 200 success HTTP status codes, communicating a successful response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Default"]
},{
"name": "OpenAPI Response Get 400 Schema Ref Error",
"slug": "openapi-response-get-400-schema-ref-error",
"description": "GET 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 400 Schema Ref Info",
"slug": "openapi-response-get-400-schema-ref-info",
"description": "GET 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 400 Status Code Error",
"slug": "openapi-response-get-400-status-code-error",
"description": "GET responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 400 Status Code Info",
"slug": "openapi-response-get-400-status-code-info",
"description": "GET responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 401 Schema Ref Error",
"slug": "openapi-response-get-401-schema-ref-error",
"description": "GET 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 401 Schema Ref Info",
"slug": "openapi-response-get-401-schema-ref-info",
"description": "GET 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 401 Status Code Error",
"slug": "openapi-response-get-401-status-code-error",
"description": "GET responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "GET responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 401 Status Code Info",
"slug": "openapi-response-get-401-status-code-info",
"description": "GET responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "GET responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 403 Schema Ref Error",
"slug": "openapi-response-get-403-schema-ref-error",
"description": "GET 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 403 Schema Ref Info",
"slug": "openapi-response-get-403-schema-ref-info",
"description": "GET 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 403 Status Code Error",
"slug": "openapi-response-get-403-status-code-error",
"description": "GET responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "GET responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 403 Status Code Info",
"slug": "openapi-response-get-403-status-code-info",
"description": "GET responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "GET responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 404 Schema Ref Error",
"slug": "openapi-response-get-404-schema-ref-error",
"description": "GET 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 404 Schema Ref Info",
"slug": "openapi-response-get-404-schema-ref-info",
"description": "GET 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 404 Status Code Error",
"slug": "openapi-response-get-404-status-code-error",
"description": "GET responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Default"]
},{
"name": "OpenAPI Response Get 404 Status Code Info",
"slug": "openapi-response-get-404-status-code-info",
"description": "GET responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Default"]
},{
"name": "OpenAPI Response Get 429 Schema Ref Error",
"slug": "openapi-response-get-429-schema-ref-error",
"description": "GET 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 429 Schema Ref Info",
"slug": "openapi-response-get-429-schema-ref-info",
"description": "GET 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx","Schema"]
},{
"name": "OpenAPI Response Get 429 Status Code Error",
"slug": "openapi-response-get-429-status-code-error",
"description": "GET responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "GET responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 429 Status Code Info",
"slug": "openapi-response-get-429-status-code-info",
"description": "GET responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "GET responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","4xx"]
},{
"name": "OpenAPI Response Get 500 Schema Ref Error",
"slug": "openapi-response-get-500-schema-ref-error",
"description": "GET 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","5xx","Schema"]
},{
"name": "OpenAPI Response Get 500 Schema Ref Info",
"slug": "openapi-response-get-500-schema-ref-info",
"description": "GET 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "GET 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","5xx","Schema"]
},{
"name": "OpenAPI Response Get 500 Status Code Error",
"slug": "openapi-response-get-500-status-code-error",
"description": "GET responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","5xx","Default"]
},{
"name": "OpenAPI Response Get 500 Status Code Info",
"slug": "openapi-response-get-500-status-code-info",
"description": "GET responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "GET responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","5xx","Default"]
},{
"name": "OpenAPI Response Get 200 Media Type Examples Error",
"slug": "openapi-response-get-200-media-type-examples-error",
"description": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "GET 200 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","GET","2xx","Media Types","Examples"]
},{
"name": "OpenAPI Response Post 201 Content Error",
"slug": "openapi-response-post-201-content-error",
"description": "POST 201 success HTTP status codes should have content property that provides the ability to describe the response content",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes should have content property that provides the ability to describe the response content",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx"]
},{
"name": "OpenAPI Response Post 201 Content Info",
"slug": "openapi-response-post-201-content-info",
"description": "POST 201 success HTTP status codes should have content property that provides the ability to describe the response content",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes should have content property that provides the ability to describe the response content",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx"]
},{
"name": "OpenAPI Response Post 201 Description Error",
"slug": "openapi-response-post-201-description-error",
"description": "POST 201 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx"]
},{
"name": "OpenAPI Response Post 201 Description Info",
"slug": "openapi-response-post-201-description-info",
"description": "POST 201 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes should have a description, describing what an API consumer can expect as a result",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx"]
},{
"name": "OpenAPI Response Post 201 Examples Ref Error",
"slug": "openapi-response-post-201-examples-ref-error",
"description": "POST 201 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Examples"]
},{
"name": "OpenAPI Response Post 201 Examples Ref Info",
"slug": "openapi-response-post-201-examples-ref-info",
"description": "POST 201 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have example references to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Examples"]
},{
"name": "OpenAPI Response Post 201 Media Type Error",
"slug": "openapi-response-post-201-media-type-error",
"description": "POST 201 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types"]
},{
"name": "OpenAPI Response Post 201 Media Type Examples Error",
"slug": "openapi-response-post-201-media-type-examples-error",
"description": "POST 201 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types"]
},{
"name": "OpenAPI Response Post 201 Media Type Examples Info",
"slug": "openapi-response-post-201-media-type-examples-info",
"description": "POST 201 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have examples to show one or many examples of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types"]
},{
"name": "OpenAPI Response Post 201 Media Type Info",
"slug": "openapi-response-post-201-media-type-info",
"description": "POST 201 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a application/json media type, standardizing the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types"]
},{
"name": "OpenAPI Response Post 201 Media Type Schema Error",
"slug": "openapi-response-post-201-media-type-schema-error",
"description": "POST 201 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Post 201 Media Type Schema Info",
"slug": "openapi-response-post-201-media-type-schema-info",
"description": "POST 201 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a schema to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Media Types","Schema"]
},{
"name": "OpenAPI Response Post 201 Schema Ref Error",
"slug": "openapi-response-post-201-schema-ref-error",
"description": "POST 201 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Schema"]
},{
"name": "OpenAPI Response Post 201 Schema Ref Info",
"slug": "openapi-response-post-201-schema-ref-info",
"description": "POST 201 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"scope": "",
"property": "",
"type": "POST 201 success HTTP status codes have a schema references to standardize the response payload returned for a successful response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Schema"]
},{
"name": "OpenAPI Response Post 201 Status Code Error",
"slug": "openapi-response-post-201-status-code-error",
"description": "POST responses should have a 201 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 201 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Default"]
},{
"name": "OpenAPI Response Post 201 Status Code Info",
"slug": "openapi-response-post-201-status-code-info",
"description": "POST responses should have a 201 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 201 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","2xx","Default"]
},{
"name": "OpenAPI Response Post 400 Schema Ref Error",
"slug": "openapi-response-post-400-schema-ref-error",
"description": "POST 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 400 Schema Ref Info",
"slug": "openapi-response-post-400-schema-ref-info",
"description": "POST 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 400 Status Code Error",
"slug": "openapi-response-post-400-status-code-error",
"description": "POST responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 400 Status Code Info",
"slug": "openapi-response-post-400-status-code-info",
"description": "POST responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 401 Schema Ref Error",
"slug": "openapi-response-post-401-schema-ref-error",
"description": "POST 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 401 Schema Ref Info",
"slug": "openapi-response-post-401-schema-ref-info",
"description": "POST 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 401 Status Code Error",
"slug": "openapi-response-post-401-status-code-error",
"description": "POST responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "POST responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 401 Status Code Info",
"slug": "openapi-response-post-401-status-code-info",
"description": "POST responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "POST responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 403 Schema Ref Error",
"slug": "openapi-response-post-403-schema-ref-error",
"description": "POST 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 403 Schema Ref Info",
"slug": "openapi-response-post-403-schema-ref-info",
"description": "POST 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 403 Status Code Error",
"slug": "openapi-response-post-403-status-code-error",
"description": "POST responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "POST responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 403 Status Code Info",
"slug": "openapi-response-post-403-status-code-info",
"description": "POST responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "POST responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 404 Schema Ref Error",
"slug": "openapi-response-post-404-schema-ref-error",
"description": "POST 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 404 Schema Ref Info",
"slug": "openapi-response-post-404-schema-ref-info",
"description": "POST 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 404 Status Code Error",
"slug": "openapi-response-post-404-status-code-error",
"description": "POST responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 404 Status Code Info",
"slug": "openapi-response-post-404-status-code-info",
"description": "POST responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 429 Schema Ref Error",
"slug": "openapi-response-post-429-schema-ref-error",
"description": "POST 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 429 Schema Ref Info",
"slug": "openapi-response-post-429-schema-ref-info",
"description": "POST 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx","Schema"]
},{
"name": "OpenAPI Response Post 429 Status Code Error",
"slug": "openapi-response-post-429-status-code-error",
"description": "POST responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "POST responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 429 Status Code Info",
"slug": "openapi-response-post-429-status-code-info",
"description": "POST responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "POST responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","4xx"]
},{
"name": "OpenAPI Response Post 500 Schema Ref Error",
"slug": "openapi-response-post-500-schema-ref-error",
"description": "POST 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","5xx","Schema"]
},{
"name": "OpenAPI Response Post 500 Schema Ref Info",
"slug": "openapi-response-post-500-schema-ref-info",
"description": "POST 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "POST 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","5xx","Schema"]
},{
"name": "OpenAPI Response Post 500 Status Code Error",
"slug": "openapi-response-post-500-status-code-error",
"description": "POST responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","5xx","Default"]
},{
"name": "OpenAPI Response Post 500 Status Code Info",
"slug": "openapi-response-post-500-status-code-info",
"description": "POST responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "POST responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","POST","5xx","Default"]
},{
"name": "OpenAPI Response Put 204 No Body Error",
"slug": "openapi-response-put-204-no-body-error",
"description": "A PUT operation that returns a 204 No Content response must not define response content, as a 204 status code indicates there is no body to return.",
"scope": "",
"property": "",
"type": "A PUT operation that returns a 204 No Content response must not define response content, as a 204 status code indicates there is no body to return.",
"guidance": "Responses",
"image": "",
"tags": ["OpenAPI","Responses","Default"]
},{
"name": "OpenAPI Response Put 204 Status Code Error",
"slug": "openapi-response-put-204-status-code-error",
"description": "PUT responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","2xx"]
},{
"name": "OpenAPI Response Put 204 Status Code Info",
"slug": "openapi-response-put-204-status-code-info",
"description": "PUT responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 204 success HTTP status codes, communicating a success created response to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","2xx"]
},{
"name": "OpenAPI Response Put 400 Schema Ref Error",
"slug": "openapi-response-put-400-schema-ref-error",
"description": "PUT 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 400 Schema Ref Info",
"slug": "openapi-response-put-400-schema-ref-info",
"description": "PUT 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 400 bad request HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 400 Status Code Error",
"slug": "openapi-response-put-400-status-code-error",
"description": "PUT responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Default"]
},{
"name": "OpenAPI Response Put 400 Status Code Info",
"slug": "openapi-response-put-400-status-code-info",
"description": "PUT responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 400 not found HTTP status code, communicating nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Default"]
},{
"name": "OpenAPI Response Put 401 Schema Ref Error",
"slug": "openapi-response-put-401-schema-ref-error",
"description": "PUT 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 401 Schema Ref Info",
"slug": "openapi-response-put-401-schema-ref-info",
"description": "PUT 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 401 unauthorized HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 401 Status Code Error",
"slug": "openapi-response-put-401-status-code-error",
"description": "PUT responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "PUT responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 401 Status Code Info",
"slug": "openapi-response-put-401-status-code-info",
"description": "PUT responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"scope": "",
"property": "",
"type": "PUT responses should have a 401 unauthorized HTTP status code, communicating that consumers do not have access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 403 Schema Ref Error",
"slug": "openapi-response-put-403-schema-ref-error",
"description": "PUT 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 403 Schema Ref Info",
"slug": "openapi-response-put-403-schema-ref-info",
"description": "PUT 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 403 forbidden HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 403 Status Code Error",
"slug": "openapi-response-put-403-status-code-error",
"description": "PUT responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "PUT responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 403 Status Code Info",
"slug": "openapi-response-put-403-status-code-info",
"description": "PUT responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"scope": "",
"property": "",
"type": "PUT responses should have a 403 forbidden HTTP status code, communicating that consumers are not allowed to access",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 404 Schema Ref Error",
"slug": "openapi-response-put-404-schema-ref-error",
"description": "PUT 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 404 Schema Ref Info",
"slug": "openapi-response-put-404-schema-ref-info",
"description": "PUT 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 404 not found HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 404 Status Code Error",
"slug": "openapi-response-put-404-status-code-error",
"description": "PUT responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 404 Status Code Info",
"slug": "openapi-response-put-404-status-code-info",
"description": "PUT responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 404 not found HTTP status code, communicating that nothing was found to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 429 Schema Ref Error",
"slug": "openapi-response-put-429-schema-ref-error",
"description": "PUT 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 429 Schema Ref Info",
"slug": "openapi-response-put-429-schema-ref-info",
"description": "PUT 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 429 too many requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 429 Status Code Error",
"slug": "openapi-response-put-429-status-code-error",
"description": "PUT responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "PUT responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx"]
},{
"name": "OpenAPI Response Put 429 Status Code Info",
"slug": "openapi-response-put-429-status-code-info",
"description": "PUT responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"scope": "",
"property": "",
"type": "PUT responses should have a 429 too many requests HTTP status code, communicating a consumer has made too may requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","4xx","Schema"]
},{
"name": "OpenAPI Response Put 500 Schema Ref Error",
"slug": "openapi-response-put-500-schema-ref-error",
"description": "PUT 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","5xx","Schema"]
},{
"name": "OpenAPI Response Put 500 Schema Ref Info",
"slug": "openapi-response-put-500-schema-ref-info",
"description": "PUT 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"scope": "",
"property": "",
"type": "PUT 500 internal server error requests HTTP status codes have a schema references to standardize the response payload returned for the error response",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","5xx","Schema"]
},{
"name": "OpenAPI Response Put 500 Status Code Error",
"slug": "openapi-response-put-500-status-code-error",
"description": "PUT responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","5xx","Schema","Default"]
},{
"name": "OpenAPI Response Put 500 Status Code Info",
"slug": "openapi-response-put-500-status-code-info",
"description": "PUT responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"scope": "",
"property": "",
"type": "PUT responses should have a 500 internal server erorr HTTP status code, communicating the API had a problem to consumers",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","PUT","5xx","Schema","Default"]
},{
"name": "OpenAPI Response RateLimit Headers",
"slug": "openapi-response-ratelimit-headers-error",
"description": "API responses must include the standard rate limit header trio (ratelimit-limit, ratelimit-remaining, ratelimit-reset) to inform consumers of their current usage against rate limits.",
"scope": "",
"property": "",
"type": "API responses must include the standard rate limit header trio (ratelimit-limit, ratelimit-remaining, ratelimit-reset) to inform consumers of their current usage against rate limits.",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Rate Limiting","Headers"]
},{
"name": "OpenAPI Response Schemas Error",
"slug": "openapi-response-schemas-error",
"description": "Have schemas to show one or many schemas of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have schemas to show one or many schemas of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Schemas"]
},{
"name": "OpenAPI Response Schemas Info",
"slug": "openapi-response-schemas-info",
"description": "Have schemas to show one or many schemas of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have schemas to show one or many schemas of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Schemas"]
},{
"name": "OpenAPI Response Schemas Ref Error",
"slug": "openapi-response-schemas-ref-error",
"description": "Have example references to show one or many schemas of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have example references to show one or many schemas of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Schemas"]
},{
"name": "OpenAPI Response Schemas Ref Info",
"slug": "openapi-response-schemas-ref-error",
"description": "Have example references to show one or many schemas of responses for different types of API requests",
"scope": "",
"property": "",
"type": "Have example references to show one or many schemas of responses for different types of API requests",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","Schemas"]
},{
"name": "OpenAPI Response Success HAL JSON",
"slug": "openapi-response-success-hal-json-info",
"description": "Success responses (2XX excluding 204) should use application/hal+json media type to provide hypermedia links that enable clients to discover related resources and actions, following the HAL specification.",
"scope": "",
"property": "",
"type": "Success responses (2XX excluding 204) should use application/hal+json media type to provide hypermedia links that enable clients to discover related resources and actions, following the HAL specification.",
"guidance": "Errors",
"image": "",
"tags": ["OpenAPI","Responses","HAL","Hypermedia"]
},{
"name": "OpenAPI Schema Description Error",
"slug": "openapi-schema-description-error",
"description": "Schema should have descriptions that provide a narrative of what a schema object is for, and how it can be used, leaving examples to demonstrate what can actually be expected",
"scope": "",
"property": "",
"type": "Schema should have descriptions that provide a narrative of what a schema object is for, and how it can be used, leaving examples to demonstrate what can actually be expected",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Description Info",
"slug": "openapi-schema-description-info",
"description": "Schema should have descriptions that provide a narrative of what a schema object is for, and how it can be used, leaving examples to demonstrate what can actually be expected",
"scope": "",
"property": "",
"type": "Schema should have descriptions that provide a narrative of what a schema object is for, and how it can be used, leaving examples to demonstrate what can actually be expected",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Description Length Error",
"slug": "openapi-schema-description-length-error",
"description": "Schema should have a length limit applied, restricting how long schema descriptions can be, helping keep them concise and consistent",
"scope": "",
"property": "",
"type": "Schema should have a length limit applied, restricting how long schema descriptions can be, helping keep them concise and consistent",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Names Pascal Case Error",
"slug": "openapi-schema-names-error",
"description": "Schema names, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications.",
"scope": "",
"property": "",
"type": "Schema names, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Names Info",
"slug": "openapi-schema-names-info",
"description": "Schema names, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications.",
"scope": "",
"property": "",
"type": "Schema names, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Names Length Error",
"slug": "openapi-schema-names-length-error",
"description": "Schema should have a length limit applied keeping the names of schema consistent across APIs",
"scope": "",
"property": "",
"type": "Schema should have a length limit applied keeping the names of schema consistent across APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata","Default","Documentation"]
},{
"name": "OpenAPI Schema Names Pascal Case Error",
"slug": "openapi-schema-names-pascal-case-error",
"description": "Schema names are pascal case, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications",
"scope": "",
"property": "",
"type": "Schema names are pascal case, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata"]
},{
"name": "OpenAPI Schema Names Pascal Case Info",
"slug": "openapi-schema-names-pascal-case-info",
"description": "Schema names are pascal case, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications",
"scope": "",
"property": "",
"type": "Schema names are pascal case, keeping the naming of them consistent across APIs, standardizing how consumers can use in their applications",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Metadata"]
},{
"name": "OpenAPI Schema Names Snake Case",
"slug": "openapi-schema-names-snake-case-info",
"description": "Schema component keys should use snake_case naming convention for consistency, particularly in APIs that follow Python or Ruby conventions.",
"scope": "",
"property": "",
"type": "Schema component keys should use snake_case naming convention for consistency, particularly in APIs that follow Python or Ruby conventions.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Naming","Casing"]
},{
"name": "OpenAPI Schema Properties Allowed Integer Format Error",
"slug": "openapi-schema-properties-allowed-integer-format-error",
"description": "Schema integer properties should have a format property with int32 or int64 applied",
"scope": "",
"property": "",
"type": "Schema integer properties should have a format property with int32 or int64 applied",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types"]
},{
"name": "OpenAPI Schema Properties Allowed Number Format Error",
"slug": "openapi-schema-properties-allowed-number-format-error",
"description": "Schema integer properties should have a format property with int32 or int64 applied",
"scope": "",
"property": "",
"type": "Schema integer properties should have a format property with int32 or int64 applied",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types"]
},{
"name": "OpenAPI Schema Properties Array Items Error",
"slug": "openapi-schema-properties-array-items-error",
"description": "Schema properties that are of the type array must have an items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array must have an items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Array Items Info",
"slug": "openapi-schema-properties-array-items-info",
"description": "Schema properties that are of the type array must have an items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array must have an items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Array Maxitems Error",
"slug": "openapi-schema-properties-array-maxitems-error",
"description": "Schema properties that are of the type array should have a max items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a max items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Array Maxitems Info",
"slug": "openapi-schema-properties-array-maxitems-info",
"description": "Schema properties that are of the type array should have a max items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a max items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Array Minitems Error",
"slug": "openapi-schema-properties-array-minitems-error",
"description": "Schema properties that are of the type array should have a min items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a min items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Array Minitems Info",
"slug": "openapi-schema-properties-array-minitems-info",
"description": "Schema properties that are of the type array should have a min items property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type array should have a min items property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Boolean Naming",
"slug": "openapi-schema-properties-boolean-naming-warn",
"description": "Boolean properties should not use an "is" prefix in their names. The property type already indicates it is a boolean, and the "is" prefix adds unnecessary verbosity.",
"scope": "",
"property": "",
"type": "Boolean properties should not use an "is" prefix in their names. The property type already indicates it is a boolean, and the "is" prefix adds unnecessary verbosity.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Naming","Boolean"]
},{
"name": "OpenAPI Schema Properties DateTime Naming",
"slug": "openapi-schema-properties-datetime-naming-warn",
"description": "DateTime properties (format date-time) should include a temporal suffix such as At, Date, Time, or On to clearly communicate that the value represents a point in time.",
"scope": "",
"property": "",
"type": "DateTime properties (format date-time) should include a temporal suffix such as At, Date, Time, or On to clearly communicate that the value represents a point in time.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Naming","DateTime"]
},{
"name": "OpenAPI Schema Properties Define Number Maximum Error",
"slug": "openapi-schema-properties-define-number-maximum-error",
"description": "Schema properties that are of the type number should have a maximum property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type number should have a maximum property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Define Number Minimum Error",
"slug": "openapi-schema-properties-define-number-minimum-error",
"description": "Schema properties that are of the type number should have a minimum property defined",
"scope": "",
"property": "",
"type": "Schema properties that are of the type number should have a minimum property defined",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Descriptions Error",
"slug": "openapi-schema-properties-descriptions-error",
"description": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"scope": "",
"property": "",
"type": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties Descriptions Info",
"slug": "openapi-schema-properties-descriptions-info",
"description": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"scope": "",
"property": "",
"type": "Schema properties should have descriptions that provide a narrative of the property contains, and how it can be used",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties Descriptions Length Error",
"slug": "openapi-schema-properties-descriptions-length-error",
"description": "Schema property descriptions should have a length limit applied, applying constraints to writing descriptions, and keeping consistent across APIs",
"scope": "",
"property": "",
"type": "Schema property descriptions should have a length limit applied, applying constraints to writing descriptions, and keeping consistent across APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties Enum Casing Error",
"slug": "openapi-schema-properties-enum-casing-error",
"description": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"scope": "",
"property": "",
"type": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Enumerators","Default"]
},{
"name": "OpenAPI Schema Properties Enum Casing Info",
"slug": "openapi-schema-properties-enum-casing-info",
"description": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"scope": "",
"property": "",
"type": "Schema property enumerators are consistent casing, keeping all entries upper snake case, and consistent across all APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Enumerators","Default"]
},{
"name": "OpenAPI Schema Properties Enum Info",
"slug": "openapi-schema-properties-enum-info",
"description": "Schema property has enumerators, providing consistent values chosen by consumers when making requests",
"scope": "",
"property": "",
"type": "Schema property has enumerators, providing consistent values chosen by consumers when making requests",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Enumerators"]
},{
"name": "OpenAPI Schema Properties Error",
"slug": "openapi-schema-properties-error",
"description": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"scope": "",
"property": "",
"type": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties"]
},{
"name": "OpenAPI Schema Properties Info",
"slug": "openapi-schema-properties-info",
"description": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"scope": "",
"property": "",
"type": "Schema has properties, providing more detail regarding the structure of each schema being applied as part of a request or a response",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties"]
},{
"name": "OpenAPI Schema Properties Names Camel Case Error",
"slug": "openapi-schema-properties-names-camel-case-error",
"description": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"scope": "",
"property": "",
"type": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties Names Camel Case Info",
"slug": "openapi-schema-properties-names-camel-case-info",
"description": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"scope": "",
"property": "",
"type": "Schema property names are camel case, providing consistent casing across all the schema properties used by APIs",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties Names Length Error",
"slug": "openapi-schema-properties-names-length-error",
"description": "Schema property names have a length restriction applied, keeping names consistent, and avoiding being too long",
"scope": "",
"property": "",
"type": "Schema property names have a length restriction applied, keeping names consistent, and avoiding being too long",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Metadata","Default"]
},{
"name": "OpenAPI Schema Properties String Maxlength Error",
"slug": "openapi-schema-properties-string-maxlength-error",
"description": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties String Maxlength Info",
"slug": "openapi-schema-properties-string-maxlength-info",
"description": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the max length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties String Minlength Error",
"slug": "openapi-schema-properties-string-minlength-error",
"description": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties String Minlength Info",
"slug": "openapi-schema-properties-string-minlength-info",
"description": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"scope": "",
"property": "",
"type": "Schema properties that are of the string type have the min length applied defining the shape of the property",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types","Default","Security"]
},{
"name": "OpenAPI Schema Properties Type Defined",
"slug": "openapi-schema-properties-type-defined-error",
"description": "All schema properties must have a type explicitly defined to ensure proper validation, code generation, and documentation. Properties without types are ambiguous and error-prone.",
"scope": "",
"property": "",
"type": "All schema properties must have a type explicitly defined to ensure proper validation, code generation, and documentation. Properties without types are ambiguous and error-prone.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Properties","Types"]
},{
"name": "OpenAPI Schema Property PII Info",
"slug": "openapi-schema-property-pii-info",
"description": "Schema properties whose names suggest personally identifiable information such as email, ssn, phone, dob, birth, or address should carry an x-pii marker so privacy tooling, governance, and consumers can identify and handle sensitive data appropriately across the API surface.",
"scope": "",
"property": "",
"type": "Schema properties whose names suggest personally identifiable information such as email, ssn, phone, dob, birth, or address should carry an x-pii marker so privacy tooling, governance, and consumers can identify and handle sensitive data appropriately across the API surface.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Schema","Security","Privacy"]
},{
"name": "OpenAPI Schema Required Error",
"slug": "openapi-schema-required-error",
"description": "Schema should have a required property defined, being explicit about which properties have to be included with the schema when it is used as part of a request or response",
"scope": "",
"property": "",
"type": "Schema should have a required property defined, being explicit about which properties have to be included with the schema when it is used as part of a request or response",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Required"]
},{
"name": "OpenAPI Schema Required Info",
"slug": "openapi-schema-required-info",
"description": "Schema should have a required property defined, being explicit about which properties have to be included with the schema when it is used as part of a request or response",
"scope": "",
"property": "",
"type": "Schema should have a required property defined, being explicit about which properties have to be included with the schema when it is used as part of a request or response",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Required"]
},{
"name": "OpenAPI Schema Required No Default",
"slug": "openapi-schema-required-no-default-error",
"description": "Required properties should not have default values. If a property is required, the client must provide it explicitly. Having a default on a required property creates confusion about whether the client needs to send it.",
"scope": "",
"property": "",
"type": "Required properties should not have default values. If a property is required, the client must provide it explicitly. Having a default on a required property creates confusion about whether the client needs to send it.",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Required","Defaults"]
},{
"name": "OpenAPI Schema Type Error",
"slug": "openapi-schema-type-error",
"description": "Schema should have a type defined, being explicit about type of data a schema describes and can be used to validate, helping standardize the type of data being made available",
"scope": "",
"property": "",
"type": "Schema should have a type defined, being explicit about type of data a schema describes and can be used to validate, helping standardize the type of data being made available",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Types","Default"]
},{
"name": "OpenAPI Schema Type Info",
"slug": "openapi-schema-type-info",
"description": "Schema should have a type defined, being explicit about type of data a schema describes and can be used to validate, helping standardize the type of data being made available",
"scope": "",
"property": "",
"type": "Schema should have a type defined, being explicit about type of data a schema describes and can be used to validate, helping standardize the type of data being made available",
"guidance": "Descriptions",
"image": "",
"tags": ["OpenAPI","Schema","Types","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Error",
"slug": "openapi-security-schemes-api-key-error",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys In Header Error",
"slug": "openapi-security-schemes-api-key-in-error",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a in of header set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a in of header set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys In Header Info",
"slug": "openapi-security-schemes-api-key-info",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a in of header set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a in of header set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Info",
"slug": "openapi-security-schemes-api-key-info",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Name Error",
"slug": "openapi-security-schemes-api-key-name-error",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a name of api_key set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a name of api_key set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Name Info",
"slug": "openapi-security-schemes-api-key-name-info",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a name of api_key set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a name of api_key set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Type Error",
"slug": "openapi-security-schemes-api-key-type-error",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a type of apiKey set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a type of apiKey set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes API Keys Type Info",
"slug": "openapi-security-schemes-api-key-type-info",
"description": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a type of apiKey set.",
"scope": "",
"property": "",
"type": "Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a type of apiKey set.",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes Error",
"slug": "openapi-security-schemes-error",
"description": "Having components security schemes ensures that the security definition for an API have been standardized and are able to be applied across APIs",
"scope": "",
"property": "",
"type": "Having components security schemes ensures that the security definition for an API have been standardized and are able to be applied across APIs",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Security Schemes Info",
"slug": "openapi-security-schemes-info",
"description": "Having components security schemes ensures that the security definition for an API have been standardized and are able to be applied across APIs",
"scope": "",
"property": "",
"type": "Having components security schemes ensures that the security definition for an API have been standardized and are able to be applied across APIs",
"guidance": "Security",
"image": "",
"tags": ["OpenAPI","Security","Default"]
},{
"name": "OpenAPI Tags Alphabetical Error",
"slug": "openapi-tags-alphabetical-error",
"description": "The tags used to organize operations should be available in an alphabetical format keeping easy to navigate for consumers.",
"scope": "",
"property": "",
"type": "The tags used to organize operations should be available in an alphabetical format keeping easy to navigate for consumers.",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Description Error",
"slug": "openapi-tags-description-error",
"description": "Tags used as part of an OpenAPI should have descriptions, providing more of a narrative behind what a tag means when it is applied to an API",
"scope": "",
"property": "",
"type": "Tags used as part of an OpenAPI should have descriptions, providing more of a narrative behind what a tag means when it is applied to an API",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Description Info",
"slug": "openapi-tags-description-info",
"description": "Tags used as part of an OpenAPI should have descriptions, providing more of a narrative behind what a tag means when it is applied to an API",
"scope": "",
"property": "",
"type": "Tags used as part of an OpenAPI should have descriptions, providing more of a narrative behind what a tag means when it is applied to an API",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Name Error",
"slug": "openapi-tags-name-error",
"description": "Tags used as part of an OpenAPI should have names, providing a simple key word or phrase that represents the tag being applied to APIs",
"scope": "",
"property": "",
"type": "Tags used as part of an OpenAPI should have names, providing a simple key word or phrase that represents the tag being applied to APIs",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Name Info",
"slug": "openapi-tags-name-info",
"description": "Tags used as part of an OpenAPI should have names, providing a simple key word or phrase that represents the tag being applied to APIs",
"scope": "",
"property": "",
"type": "Tags used as part of an OpenAPI should have names, providing a simple key word or phrase that represents the tag being applied to APIs",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Object Error",
"slug": "openapi-tags-object-error",
"description": "There needs to be a central tags object applied to the OpenAPI, providing central tags that can be applied across all operations within an OpenAPI",
"scope": "",
"property": "",
"type": "There needs to be a central tags object applied to the OpenAPI, providing central tags that can be applied across all operations within an OpenAPI",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Object Info",
"slug": "openapi-tags-object-info",
"description": "There needs to be a central tags object applied to the OpenAPI, providing central tags that can be applied across all operations within an OpenAPI",
"scope": "",
"property": "",
"type": "There needs to be a central tags object applied to the OpenAPI, providing central tags that can be applied across all operations within an OpenAPI",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags One Error",
"slug": "openapi-tags-one-error",
"description": "There needs to be at least one tag applied to an OpenAPI, providing a key word or phrase that can be applied to API operations",
"scope": "",
"property": "",
"type": "There needs to be at least one tag applied to an OpenAPI, providing a key word or phrase that can be applied to API operations",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Tags Upper Case Error",
"slug": "openapi-tags-upper-case-error",
"description": "The first letter of each word in a tag being applied to APIs needs to be capitalized, keeping the tags being applied across APIs the same look and feel for organizing and publishing to documentation",
"scope": "",
"property": "",
"type": "The first letter of each word in a tag being applied to APIs needs to be capitalized, keeping the tags being applied across APIs the same look and feel for organizing and publishing to documentation",
"guidance": "OpenAPI",
"image": "",
"tags": ["OpenAPI","Tags","Default"]
},{
"name": "OpenAPI Version Date Format",
"slug": "openapi-version-date-format-info",
"description": "API versions using date-based format should follow the YYYY-MM-DD pattern, optionally followed by a -preview suffix for pre-release versions.",
"scope": "",
"property": "",
"type": "API versions using date-based format should follow the YYYY-MM-DD pattern, optionally followed by a -preview suffix for pre-release versions.",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Info","Version","Date"]
},{
"name": "OpenAPI Version Date Info",
"slug": "openapi-version-date-info",
"description": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using date-based versioning published to the info version property",
"scope": "",
"property": "",
"type": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using date-based versioning published to the info version property",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Versions"]
},{
"name": "OpenAPI Version In Path Error",
"slug": "openapi-version-in-path-error",
"description": "The majority of public APIs available on the Web today put the major version of the API as part of the path for each API",
"scope": "",
"property": "",
"type": "The majority of public APIs available on the Web today put the major version of the API as part of the path for each API",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Versions","Paths"]
},{
"name": "OpenAPI Version In Path Info",
"slug": "openapi-version-in-path-info",
"description": "The majority of public APIs available on the Web today put the major version of the API as part of the path for each API",
"scope": "",
"property": "",
"type": "The majority of public APIs available on the Web today put the major version of the API as part of the path for each API",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Versions","Paths"]
},{
"name": "OpenAPI Version Semantic Info",
"slug": "openapi-version-semantic-info",
"description": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic versioning published to the info version property",
"scope": "",
"property": "",
"type": "Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic versioning published to the info version property",
"guidance": "Change Management",
"image": "",
"tags": ["OpenAPI","Versions"]
},{
"name": "OWASP API1 2023 No Numeric IDs",
"slug": "owasp-api1-2023-no-numeric-ids-error",
"description": "Use random IDs that cannot be guessed. UUIDs are preferred but any other random string will do. Using numeric IDs can lead to enumeration attacks where attackers iterate through possible ID values.",
"scope": "",
"property": "",
"type": "Use random IDs that cannot be guessed. UUIDs are preferred but any other random string will do. Using numeric IDs can lead to enumeration attacks where attackers iterate through possible ID values.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Identifiers","OpenAPI"]
},{
"name": "OWASP API2 2023 Auth Insecure Schemes",
"slug": "owasp-api2-2023-auth-insecure-schemes-error",
"description": "There are many HTTP authorization schemes but some of them are now considered insecure, such as negotiating authentication using specifications like NTLM or OAuth v1.",
"scope": "",
"property": "",
"type": "There are many HTTP authorization schemes but some of them are now considered insecure, such as negotiating authentication using specifications like NTLM or OAuth v1.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Authentication","OpenAPI"]
},{
"name": "OWASP API2 2023 JWT Best Practices",
"slug": "owasp-api2-2023-jwt-best-practices-error",
"description": "JSON Web Token implementations must explicitly declare support for RFC8725 to address common pitfalls like ignoring algorithms or using insecure algorithms in JWT validation.",
"scope": "",
"property": "",
"type": "JSON Web Token implementations must explicitly declare support for RFC8725 to address common pitfalls like ignoring algorithms or using insecure algorithms in JWT validation.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","JWT","Authentication","OpenAPI"]
},{
"name": "OWASP API2 2023 No API Keys in URL",
"slug": "owasp-api2-2023-no-api-keys-in-url-error",
"description": "API Keys are passed in headers, cookies or query parameters to access APIs. Those keys can be eavesdropped, especially when they are passed in the URL as logging or history tools will keep track of them and potentially expose them.",
"scope": "",
"property": "",
"type": "API Keys are passed in headers, cookies or query parameters to access APIs. Those keys can be eavesdropped, especially when they are passed in the URL as logging or history tools will keep track of them and potentially expose them.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","API Keys","OpenAPI"]
},{
"name": "OWASP API2 2023 No Credentials in URL",
"slug": "owasp-api2-2023-no-credentials-in-url-error",
"description": "URL parameters MUST NOT contain credentials such as API key, password, or secret. This is a security risk as URLs are often logged and cached.",
"scope": "",
"property": "",
"type": "URL parameters MUST NOT contain credentials such as API key, password, or secret. This is a security risk as URLs are often logged and cached.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Credentials","OpenAPI"]
},{
"name": "OWASP API2 2023 No HTTP Basic",
"slug": "owasp-api2-2023-no-http-basic-error",
"description": "Basic authentication credentials transported over network are more susceptible to interception than other forms of authentication, and as they are not encrypted it means passwords and tokens are more easily leaked.",
"scope": "",
"property": "",
"type": "Basic authentication credentials transported over network are more susceptible to interception than other forms of authentication, and as they are not encrypted it means passwords and tokens are more easily leaked.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Authentication","OpenAPI"]
},{
"name": "OWASP API2 2023 Read Restricted",
"slug": "owasp-api2-2023-read-restricted-warn",
"description": "Read operations (GET, HEAD) should be secured by at least one security scheme to prevent unauthorized access to sensitive data.",
"scope": "",
"property": "",
"type": "Read operations (GET, HEAD) should be secured by at least one security scheme to prevent unauthorized access to sensitive data.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Operations","OpenAPI"]
},{
"name": "OWASP API2 2023 Short Lived Access Tokens",
"slug": "owasp-api2-2023-short-lived-access-tokens-error",
"description": "Using short-lived access tokens is a good practice. When using OAuth 2, this is done by using refresh tokens. If a malicious actor is able to get hold of an access token then rotation means that token might not work by the time they try to use it.",
"scope": "",
"property": "",
"type": "Using short-lived access tokens is a good practice. When using OAuth 2, this is done by using refresh tokens. If a malicious actor is able to get hold of an access token then rotation means that token might not work by the time they try to use it.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","OAuth","Tokens","OpenAPI"]
},{
"name": "OWASP API2 2023 Write Restricted",
"slug": "owasp-api2-2023-write-restricted-error",
"description": "All write operations (POST, PUT, PATCH, DELETE) must be secured by at least one security scheme to prevent unauthorized modifications.",
"scope": "",
"property": "",
"type": "All write operations (POST, PUT, PATCH, DELETE) must be secured by at least one security scheme to prevent unauthorized modifications.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Operations","OpenAPI"]
},{
"name": "OWASP API3 2023 No Additional Properties",
"slug": "owasp-api3-2023-no-additional-properties-warn",
"description": "By default JSON Schema allows additional properties, which can potentially lead to mass assignment issues, where unspecified fields are passed to the API without validation. Disable them with additionalProperties set to false or add maxProperties.",
"scope": "",
"property": "",
"type": "By default JSON Schema allows additional properties, which can potentially lead to mass assignment issues, where unspecified fields are passed to the API without validation. Disable them with additionalProperties set to false or add maxProperties.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","OpenAPI"]
},{
"name": "OWASP API4 2023 Array Limit",
"slug": "owasp-api4-2023-array-limit-error",
"description": "Array size should be limited to mitigate resource exhaustion attacks. This can be done using maxItems. You should ensure that the subschema in items is constrained too.",
"scope": "",
"property": "",
"type": "Array size should be limited to mitigate resource exhaustion attacks. This can be done using maxItems. You should ensure that the subschema in items is constrained too.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","Arrays","OpenAPI"]
},{
"name": "OWASP API4 2023 Integer Format",
"slug": "owasp-api4-2023-integer-format-error",
"description": "Integers should be limited to mitigate resource exhaustion attacks. Specifying whether int32 or int64 is expected via format helps enforce proper constraints.",
"scope": "",
"property": "",
"type": "Integers should be limited to mitigate resource exhaustion attacks. Specifying whether int32 or int64 is expected via format helps enforce proper constraints.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","Integers","OpenAPI"]
},{
"name": "OWASP API4 2023 Integer Limit",
"slug": "owasp-api4-2023-integer-limit-error",
"description": "Integers should be limited to mitigate resource exhaustion attacks. This can be done using minimum and maximum, which helps avoid negative numbers when positive are expected, or reducing unreasonable iterations.",
"scope": "",
"property": "",
"type": "Integers should be limited to mitigate resource exhaustion attacks. This can be done using minimum and maximum, which helps avoid negative numbers when positive are expected, or reducing unreasonable iterations.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","Integers","OpenAPI"]
},{
"name": "OWASP API4 2023 Rate Limit",
"slug": "owasp-api4-2023-rate-limit-error",
"description": "Define proper rate limiting to avoid attackers overloading the API. There are many ways to implement rate-limiting, but most of them involve using HTTP headers. All 2XX and 4XX responses should define rate limiting headers.",
"scope": "",
"property": "",
"type": "Define proper rate limiting to avoid attackers overloading the API. There are many ways to implement rate-limiting, but most of them involve using HTTP headers. All 2XX and 4XX responses should define rate limiting headers.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OWASP","Security","Rate Limiting","OpenAPI"]
},{
"name": "OWASP API4 2023 Rate Limit Responses 429",
"slug": "owasp-api4-2023-rate-limit-responses-429-warn",
"description": "A HTTP 429 response signals the API client is making too many requests, and will supply information about when to retry so that the client can back off calmly without everything breaking. All operations should define a 429 response.",
"scope": "",
"property": "",
"type": "A HTTP 429 response signals the API client is making too many requests, and will supply information about when to retry so that the client can back off calmly without everything breaking. All operations should define a 429 response.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OWASP","Security","Rate Limiting","Responses","OpenAPI"]
},{
"name": "OWASP API4 2023 Rate Limit Retry After",
"slug": "owasp-api4-2023-rate-limit-retry-after-error",
"description": "Define proper rate limiting to avoid attackers overloading the API. Part of that involves setting a Retry-After header so well-meaning consumers are not polling and potentially exacerbating problems.",
"scope": "",
"property": "",
"type": "Define proper rate limiting to avoid attackers overloading the API. Part of that involves setting a Retry-After header so well-meaning consumers are not polling and potentially exacerbating problems.",
"guidance": "Rate Limits",
"image": "",
"tags": ["OWASP","Security","Rate Limiting","OpenAPI"]
},{
"name": "OWASP API4 2023 String Limit",
"slug": "owasp-api4-2023-string-limit-error",
"description": "String size should be limited to mitigate resource exhaustion attacks. This can be done using maxLength, enum, or const.",
"scope": "",
"property": "",
"type": "String size should be limited to mitigate resource exhaustion attacks. This can be done using maxLength, enum, or const.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","Strings","OpenAPI"]
},{
"name": "OWASP API4 2023 String Restricted",
"slug": "owasp-api4-2023-string-restricted-warn",
"description": "To avoid unexpected values being sent or leaked, strings should have a format, RegEx pattern, enum, or const to restrict the possible values.",
"scope": "",
"property": "",
"type": "To avoid unexpected values being sent or leaked, strings should have a format, RegEx pattern, enum, or const to restrict the possible values.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Schema","Strings","OpenAPI"]
},{
"name": "OWASP API7 2023 Concerning URL Parameter",
"slug": "owasp-api7-2023-concerning-url-parameter-info",
"description": "Using external resource URLs based on user input for webhooks, file fetching, custom SSO, URL previews, or redirects can lead to Server Side Request Forgery (SSRF) and other security issues.",
"scope": "",
"property": "",
"type": "Using external resource URLs based on user input for webhooks, file fetching, custom SSO, URL previews, or redirects can lead to Server Side Request Forgery (SSRF) and other security issues.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","SSRF","Parameters","OpenAPI"]
},{
"name": "OWASP API8 2023 Define CORS Origin",
"slug": "owasp-api8-2023-define-cors-origin-error",
"description": "Setting up CORS headers will control which websites can make browser-based HTTP requests to your API. The Access-Control-Allow-Origin header should be defined on all responses.",
"scope": "",
"property": "",
"type": "Setting up CORS headers will control which websites can make browser-based HTTP requests to your API. The Access-Control-Allow-Origin header should be defined on all responses.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","CORS","Headers","OpenAPI"]
},{
"name": "OWASP API8 2023 Define Error Responses 401",
"slug": "owasp-api8-2023-define-error-responses-401-warn",
"description": "OWASP API Security recommends defining schemas for all responses, even errors. The 401 describes what happens when a request is unauthorized, so it is important to define this for documentation and contract testing.",
"scope": "",
"property": "",
"type": "OWASP API Security recommends defining schemas for all responses, even errors. The 401 describes what happens when a request is unauthorized, so it is important to define this for documentation and contract testing.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Responses","Authentication","OpenAPI"]
},{
"name": "OWASP API8 2023 Define Error Responses 500",
"slug": "owasp-api8-2023-define-error-responses-500-warn",
"description": "OWASP API Security recommends defining schemas for all responses, even errors. The 500 describes what happens when a request fails with an internal server error, so it is important to define this for documentation and contract testing.",
"scope": "",
"property": "",
"type": "OWASP API Security recommends defining schemas for all responses, even errors. The 500 describes what happens when a request fails with an internal server error, so it is important to define this for documentation and contract testing.",
"guidance": "Errors",
"image": "",
"tags": ["OWASP","Security","Responses","Errors","OpenAPI"]
},{
"name": "OWASP API8 2023 Define Error Validation",
"slug": "owasp-api8-2023-define-error-validation-warn",
"description": "Carefully define schemas for all the API responses, including either 400, 422 or 4XX responses which describe errors caused by invalid requests.",
"scope": "",
"property": "",
"type": "Carefully define schemas for all the API responses, including either 400, 422 or 4XX responses which describe errors caused by invalid requests.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Responses","Validation","OpenAPI"]
},{
"name": "OWASP API8 2023 No Server HTTP",
"slug": "owasp-api8-2023-no-server-http-error",
"description": "Server interactions must not use http:// as it is inherently insecure and can lead to PII and other sensitive information being leaked through traffic sniffing or man-in-the-middle attacks. Use https:// or wss:// instead.",
"scope": "",
"property": "",
"type": "Server interactions must not use http:// as it is inherently insecure and can lead to PII and other sensitive information being leaked through traffic sniffing or man-in-the-middle attacks. Use https:// or wss:// instead.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Transport","Servers","OpenAPI"]
},{
"name": "OWASP API9 2023 Inventory Access",
"slug": "owasp-api9-2023-inventory-access-error",
"description": "Servers should use the x-internal vendor extension set to true or false to explicitly declare the intended audience for the API, which will be picked up by most documentation tools.",
"scope": "",
"property": "",
"type": "Servers should use the x-internal vendor extension set to true or false to explicitly declare the intended audience for the API, which will be picked up by most documentation tools.",
"guidance": "Security",
"image": "",
"tags": ["OWASP","Security","Servers","Inventory","OpenAPI"]
},{
"name": "OWASP API9 2023 Inventory Environment",
"slug": "owasp-api9-2023-inventory-environment-error",
"description": "Make it clear which servers are expected to run in which environment to avoid unexpected problems, exposing test data to the public, or letting bad actors bypass security measures to reach production-like environments.",
"scope": "",
"property": "",
"type": "Make it clear which servers are expected to run in which environment to avoid unexpected problems, exposing test data to the public, or letting bad actors bypass security measures to reach production-like environments.",
"guidance": "Environments",
"image": "",
"tags": ["OWASP","Security","Servers","Inventory","OpenAPI"]
}]