---
title: "Update transaction"
method: PATCH
path: "/transactions/{companyId}/{id}"
tags: ["Transactions"]
---

# Update transaction

`PATCH /transactions/{companyId}/{id}`

Updates the synchronization status, additional info or custom attribute values of a transaction identified by `id`. Only the fields you send are changed. Note that updating an `id` that does not match any transaction also returns `200` without applying any change — no `404` is raised.

## Path parameters

- `id` string, required
- `companyId` string, required

## Request body

- PatchTransactionsRequestSchema
  - `additionalInfo` object — Free-form key/value metadata to attach to the transaction.
  - `attributes` AttributeValueRequestSchema[], nullable — Custom attribute values to attach to the transaction.
    - `customId` string, required — Custom ID of the attribute (see the Attributes endpoints) being set.
    - `value` string, required — Display text of the value being set on this entity.
    - `valueCustomId` string, nullable — Custom ID of one of the attribute's predefined `values`, when the attribute is of type `list`. Leave unset for free-form `string`/`number` attributes.
    - `parentCustomId` string, nullable — Not used when attaching an attribute value to an entity.
  - `sync` boolean, nullable — Marks the transaction as synchronized with your ERP.

## Response `200`

Successful Response

- ModifyTransactionsResponseSchema
  - `id` string, required — Embat transaction ID

## Other responses

- `401` — Unauthorized. The bearer token is missing, invalid or expired.
- `404` — Not found. The requested resource or `companyId` does not exist.
- `422` — Validation Error
- `500` — Unexpected error. Contact support if it persists.

---

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