RFC7807 · Problem Details for HTTP APIs

{
  "id": "RFC7807",
  "number": 7807,
  "title_en": "Problem Details for HTTP APIs",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "This document defines a \"problem detail\" as a way to carry machine- readable details of errors in a HTTP response to avoid the need to define new error response formats for HTTP APIs.",
  "authors": [
    "M. Nottingham",
    "E. Wilde"
  ],
  "organizations": [],
  "publication_date": "2016-03-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "art",
  "area_ru": "Приложения и взаимодействие в реальном времени",
  "working_group": "appsawg",
  "source_draft": "draft-ietf-appsawg-http-problem-03",
  "page_count": 16,
  "doi": "10.17487/RFC7807",
  "keywords": [
    "status",
    "HTTP",
    "error",
    "problem",
    "API",
    "JSON",
    "XML"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC9457"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7807/",
    "html": "https://www.rfc-editor.org/rfc/rfc7807.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7807.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7807/"
  }
}