Tables

Update Row

Updates an existing row in a Big Table. If a column is not included in the passed row data, it will not be updated. If a column is passed that does not exist in the table schema, or with a value that does not match the column's type, the default behavior is for no update to be made and the API call to [return an error](/docs/classic-api/general/errors#invalid-row-data). However, you can control this behavior with the `onSchemaError` query parameter.

Authentication

AuthorizationBearer

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path parameters

tableIDstringRequired
rowIDstringRequired

Headers

if-matchstringOptionalformat: "^"[0-9]+"$"

Query parameters

onSchemaErrorenumOptional
The action to take when the passed data does not match the table schema: - `abort`: Abort the entire operation and return an error. - `dropColumns`: Ignore the data that caused the error, and do not import those columns in the affected rows. - `updateSchema`: Update the schema as needed to add any missing columns or widen the data types of existing columns, and then import the data from them.
Allowed values:

Request

This endpoint expects a map from strings to any.

Response

Errors

400
Bad Request Error
402
Payment Required Error
404
Not Found Error
412
Precondition Failed Error
422
Unprocessable Entity Error