---
title: "Update an event"
method: PATCH
path: "/events/{event_id}"
tags: ["Events"]
---

# Update an event

`PATCH /events/{event_id}`

Change information in existing events specified by `event_id` or *flag suspicious events*.

When an event is created, it can be assigned `linked_id` and `tags` submitted through the JS agent parameters. 
This information might not have been available on the client initially, so the Server API permits updating these attributes after the fact.

**Warning** It's not possible to update events older than one month. 

**Warning** Trying to update an event immediately after creation may temporarily result in an 
error (HTTP 409 Conflict. The event is not mutable yet.) as the event is fully propagated across our systems. In such a case, simply retry the request.

## Path parameters

- `event_id` string, required

## Request body

- EventUpdate
  - `linked_id` string — Linked ID value to assign to the existing event
  - `tags` object — A customer-provided value or an object that was sent with the identification request or updated later.
  - `suspect` boolean — Suspect flag indicating observed suspicious or fraudulent event

## Response `200`

OK.

## Other responses

- `400` — Bad request. The request payload is not valid.
- `403` — Forbidden. Access to this API is denied.
- `404` — Not found. The event Id cannot be found in this workspace's data.
- `409` — Conflict. The event is not mutable yet.

---

[API](https://skmtc.dev/fingerprint/apis/management-api.md) · [All operations](https://skmtc.dev/fingerprint/apis/management-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fingerprint/management-api/revisions/b17eccec9d47/schema)