OpenAPI Request Body On Put Error Info

PUT operations should define a requestBody because they typically replace a resource and require the client to send the representation being stored.

Message: PUT Operations SHOULD Define a Request Body

Policies

Requiring that all operational request body schema meets the policy standards.

#OpenAPI #Operations #RequestBodies #Default

6 tools reach this content

find_building_blocksBrowse every rules entry — call it with type="rules".
get_building_blockOne rules entry in full; add include=content for the body (Pro).
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.

curl for this page

This rule

curl "https://api.apievangelist.com/v1/rules/openapi-request-body-on-put-error-info"

Full body (Pro)

curl "https://api.apievangelist.com/v1/rules/openapi-request-body-on-put-error-info?include=content" \
  -H "x-api-key: $AE_KEY"

Related across the network

curl "https://api.apievangelist.com/v1/rules/openapi-request-body-on-put-error-info/related"

All rules

curl "https://api.apievangelist.com/v1/rules?limit=25"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.