---
title: "Update Article Embargo"
method: PUT
path: "/account/articles/{article_id}/embargo"
tags: ["articles"]
---

# Update Article Embargo

`PUT /account/articles/{article_id}/embargo`

Note: setting an article under whole embargo does not imply that the article will be published when the embargo will expire. You must explicitly call the publish endpoint to enable this functionality.

## Path parameters

- `article_id` integer, required

## Request body

- ArticleEmbargoUpdater
  - `is_embargoed` boolean, required — Embargo status
  - `embargo_date` string, required — Date when the embargo expires and the article gets published, '0' value will set up permanent embargo
  - `embargo_type` 'article' | 'file', required — Embargo can be enabled at the article or the file level. Possible values: article, file
  - `embargo_title` string — Title for embargo
  - `embargo_reason` string — Reason for setting embargo
  - `embargo_options` object[] — List of embargo permissions to be associated with the article. The list must contain `id` and can also contain `group_ids`(a field that only applies to 'logged_in' permissions). The new list replaces old options in the database, and an empty list removes all permissions for this article. Administration permission has to be set up alone but logged in and IP range permissions can be set up together.

## Response `205`

Reset Content

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/figshare/apis/figshare-api.md) · [All operations](https://skmtc.net/figshare/apis/figshare-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/figshare/figshare-api/versions/9dfb419f4430/schema)