---
title: "Upsert Row"
method: POST
path: "/api/v1/tables/{tableId}/rows/upsert"
tags: ["Tables"]
---

# Upsert Row

`POST /api/v1/tables/{tableId}/rows/upsert`

Insert a new row or update an existing one based on a unique column value. The table must have at least one column with a unique constraint. If a row with a matching unique value exists, it is updated; otherwise, a new row is inserted. When multiple unique columns exist, specify `conflictTarget` to indicate which column to match on.

## Path parameters

- `tableId` string, required

## Request body

- object
  - `workspaceId` string, required — The workspace ID.
  - `data` object, required — Row data. Must include a value for the conflict target column.
  - `conflictTarget` string — Name of the unique column to match on. Required when the table has multiple unique columns. If the table has exactly one unique column, this can be omitted.

## Response `200`

Row upserted successfully.

- object
  - `success` boolean — Indicates whether the request was successful.
  - `data` object — Response payload.
    - `row` TableRow — A single row in a table.
      - `id` string — Unique row identifier.
      - `data` object — Row data as key-value pairs matching the table schema.
      - `position` integer — Row's position/order in the table.
      - `createdAt` string, date-time — ISO 8601 timestamp when the row was created.
      - `updatedAt` string, date-time — ISO 8601 timestamp when the row was last modified.
    - `operation` 'insert' | 'update' — Whether the row was inserted or updated.
    - `message` string — Confirmation message.

## Other responses

- `400` — Invalid request parameters. Check the details array for specific validation errors.
- `401` — Invalid or missing API key. Ensure the X-API-Key header is set with a valid key.
- `403` — Access denied. You do not have permission to access this resource. For audit log endpoints, this requires an Enterprise subscription and organization admin/owner role.
- `404` — The requested resource was not found. Verify the ID is correct and belongs to your workspace.
- `429` — Rate limit exceeded. Wait for the duration specified in the Retry-After header before retrying. The X-RateLimit-* headers accompany every response from an authenticated v1 request — success and error alike — and are omitted only when the request fails authentication, since no rate-limit bucket is consulted in that case.

---

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