---
title: "Changes to Request review on an article"
method: POST
path: "/knowledge-bases/{id}/articles/{article_id}/request-review"
---

# Changes to Request review on an article

`POST /knowledge-bases/{id}/articles/{article_id}/request-review`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 3 of 63 revisions.

- **2026-10-12** `40bf3229d58f`: 1 info
- **2026-10-11** `dfb481067e5a`: 90 info
- **2026-09-12** `e85c0a2a3253`: 4 info

## Changes

- **2026-10-12** `40bf3229d58f`: 1 info
  - the response property `data` became required for the status `200`
- **2026-10-11** `dfb481067e5a`: 90 info
  - added the non-success response with the status `401`
  - added the non-success response with the status `429`
  - the response property `data/approval_status` became required for the status `200`
  - the response property `data/article_id` became required for the status `200`
  - the response property `data/article_version_id` became required for the status `200`
  - the response property `request_id` became required for the status `200`
  - the response property `request_id` became required for the status `400`
  - the response property `request_id` became required for the status `403`
  - the response property `request_id` became required for the status `404`
  - the response property `request_id` became required for the status `500`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `400`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `403`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `404`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `500`
  - removed the `email_bounced` enum value from the `code` response property for the response status `400`
  - removed the `email_bounced` enum value from the `code` response property for the response status `403`
  - removed the `email_bounced` enum value from the `code` response property for the response status `404`
  - removed the `email_bounced` enum value from the `code` response property for the response status `500`
  - removed the `internal_error` enum value from the `code` response property for the response status `400`
  - removed the `internal_error` enum value from the `code` response property for the response status `403`
  - removed the `internal_error` enum value from the `code` response property for the response status `404`
  - removed the `internal_error` enum value from the `code` response property for the response status `500`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `400`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `403`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `404`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `500`
  - removed the `invalid_api_token` enum value from the `code` response property for the response status `400`
  - removed the `invalid_api_token` enum value from the `code` response property for the response status `403`
  - removed the `invalid_api_token` enum value from the `code` response property for the response status `404`
  - removed the `invalid_api_token` enum value from the `code` response property for the response status `500`
  - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `400`
  - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `403`
  - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `404`
  - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `500`
  - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `400`
  - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `403`
  - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `404`
  - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `500`
  - removed the `invalid_request_body` enum value from the `code` response property for the response status `400`
  - removed the `invalid_request_body` enum value from the `code` response property for the response status `403`
  - …50 more
- **2026-09-12** `e85c0a2a3253`: 4 info
  - added the optional property `code` to the response with the `400` status
  - added the optional property `code` to the response with the `403` status
  - added the optional property `code` to the response with the `404` status
  - added the optional property `code` to the response with the `500` status

---

[Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/knowledge-bases/:id/articles/:article_id/request-review/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/knowledge-bases/:id/articles/:article_id/request-review/post)
