Update Model

Updates a model’s configuration.

Updating a model is a full replacement of its configuration. Every field in the request body is written to the model; any field you omit is cleared or reset to its default value, with two exceptions: an empty or omitted policies list leaves policies unchanged, and omitted field_overrides entries retain their current types.

To make a partial change, fetch the current model with GET /api/models/{id}, modify the fields you want to change, and send the complete object back in the update request.

Changes to source fields, filters, or the identity column take effect on the next sync execution that uses this model.

Field type overrides

Use field_overrides to choose types for detected source fields on CSV file, HTTP API, Google Sheets, and MongoDB models. Other model types reject overrides. Keep additional_fields for user-defined fields.

For example, include this fragment in a complete model request to treat amount as a number:

{
  "field_overrides": {
    "amount": { "type": "number" }
  }
}

Use fields separately to choose which fields to publish. The response’s fields[].type contains each published field’s effective type.

On update, only supplied override entries change types. Omitted entries, an empty map, or null preserve current types, including types chosen in the UI. Removing an entry does not restore its inferred type; supply another concrete type to change it. There is no separate inferred-type or override-state map in the response.