Skip to main content

API endpoint page template

Use this checklist for every new or substantially changed endpoint page. Keep the OpenAPI panel authoritative for fields and place practical decision guidance in MDX.

Review gates

  • The example satisfies required fields, types, enums, and constraints.
  • Request fields do not include keys absent from the public schema.
  • Response prose and examples use the same envelope as OpenAPI.
  • Side effects and retry safety are source-verified.
  • Safety labels use a semantic data-api-safety-label wrapper, never a frontmatter tag.
  • In preview, the safety label appears beside the endpoint heading and stays out of the sidebar.
  • The page says how to verify success and recover from common failures.
  • Every path and heading link resolves in docs.json.