name or key — a call with none of them has nothing to
update. Sending the values the table already has changes nothing, so the same
call can be sent twice.
A new key changes how Qobra’s public API addresses the table: anything calling
the API with the old key stops reaching it.
The table’s name field and conversion date field, and the import settings of a
table synced from an integration, can only be changed on the table’s page in
the Qobra web app: they rename every record or relaunch the import.
The call is refused when:
keyis passed for a table synced from an integration, which keeps the key of its source table.- the new key is already carried by another table of the company, or normalizes to nothing.
Qobra MCP agent.
Example arguments
Parameters
Body
Body
string
required
Id of the data table to update — the id list_data_tables returns, or the
one create_data_table just returned. Never a table name.
string
New display name of the table, as people will read it in Qobra. Omit to
leave the current name as it is.
string
New stable key of a local table: the identifier the public API addresses
it by, distinct from the display name. Lowercase and underscore-separated,
and unique across the company. A table synced from an integration keeps
the key of its source table. Omit to leave the current key as it is.
Response
Body
Body
object
The data table as it now stands — the same row list_data_tables returns.
See
list_data_tables for
the full field breakdown.