---
title: "Update a screenshot marker"
method: PATCH
path: "/projects/{project_id}/screenshots/{screenshot_id}/markers"
tags: ["Screenshot Markers"]
---

# Update a screenshot marker

`PATCH /projects/{project_id}/screenshots/{screenshot_id}/markers`

Update an existing screenshot marker.

## Path parameters

- `project_id` string, required
- `screenshot_id` string, required

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `branch` string — specify the branch to use
  - `key_id` string — Specify the Key ID which should be highlighted on the specified screenshot. The Key must belong to the project.
  - `presentation` string — Presentation details of the screenshot marker in JSON format. Each Screenshot Marker is represented as a rectangular shaped highlight box with the name of the specified Key attached. You can specify the marker position on the screenshot (`x`-axis and `y`-axis in pixels) from the top left corner of the screenshot and the dimensions of the marker itself (`w` and `h` in pixels).

## Response `200`

OK

- ScreenshotMarker
  - `id` string
  - `presentation` object — Coordinates and size of the marker on the screenshot, in pixels.
    - `x` integer
    - `y` integer
    - `w` integer
    - `h` integer
  - `presentation_type` string — Marker presentation style. The default value is `default`.
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `translation_key` TranslationKey
    - `id` string
    - `name` string
    - `description` string
    - `name_hash` string
    - `plural` boolean
    - `use_ordinal_rules` boolean
    - `tags` string[]
    - `data_type` string
    - `created_at` string, date-time
    - `updated_at` string, date-time

## Other responses

- `400` — Bad request. The request could not be parsed or a parameter failed validation. Verify the request body, the content type, and the parameter types, then retry.
- `401` — Unauthorized. Authentication failed because the access token is missing, expired, or invalid. Supply a valid access token and retry.
- `403` — Forbidden. The credentials are valid but not permitted for this request: the access token may lack the required scope, the user may lack permission on the resource, or the account plan may not include the feature. Use a token with the required scope on an account and user that hold the necessary permissions.
- `404` — Not found. The requested resource does not exist or is not visible to the authenticated user. Verify the identifiers in the request path and that the token has access to them, then retry.
- `422` — Unprocessable entity. The request was well-formed but failed validation. The response body lists each offending field in the `errors` array, with its resource, field, and a human-readable message. Correct the listed fields and retry.
- `429` — Too many requests. The rate limit has been exceeded. Wait until the time indicated by the `X-Rate-Limit-Reset` response header before retrying.

---

[API](https://skmtc.net/phrase/apis/control-hub-service.md) · [All operations](https://skmtc.net/phrase/apis/control-hub-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/phrase/control-hub-service/versions/98ecac7ba2bf/schema)