Skip to content

Update Field

Updates the value of a single field on an existing content entry. You can target the field either by field value id or by field name + language.

Endpoint

shell
curl -X PUT https://api.contentisland.net/api/1.0/content/:id \
--header 'Authorization: Bearer YOUR_WRITE_TOKEN' \
--header 'Content-Type: application/json' \
--data '{ ... }'

Path Parameters

The :id segment in the URL is required and identifies which content entry to update.

NameTypeRequiredDescription
idstringyesThe ID of the content entry to update. You can find it in your project’s Content tab, either in the list or in the content details.

Body

The body has two valid shapes. Use the field name + language form — it’s the recommended one. The field value id form is kept for backwards compatibility but is deprecated and may be removed in a future version.

interface UpdateFieldValueByFieldNamePayload {
fieldName: string; // field name as defined in the model
language: LanguageCode; // language of the value to update
value: any; // new value
}
NameDescription
fieldNameThe name of the field as defined in the model (e.g. title).
languageThe language of the value being updated. Must be one of the languages enabled on the project.
valueThe new value for the field.

Update by field value id (deprecated)

interface UpdateFieldValuePayload {
id: string; // id of the field value to update (returned by GET /content)
value: any; // new value
}
NameDescription
idThe id of the existing field value. You can obtain it from the fields[].id returned by GET /content.
valueThe new value for the field. The expected type depends on the field’s type in the model.

Example

shell
curl -X PUT https://api.contentisland.net/api/1.0/content/660f5b8a3a1c2d4e7f8b9012 \
--header 'Authorization: Bearer YOUR_WRITE_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
"fieldName": "title",
"language": "en",
"value": "Hello world (updated)"
}'

Response

On success the endpoint returns 204 No Content with an empty body.

Status Codes

CodeDescription
204The field was updated successfully.
400Invalid payload (missing fields, wrong shape, or the supplied language is not configured in the project).
401Unauthorized. The token is missing, malformed or expired.
403Forbidden. The token does not have write permissions — use a Write Token.
404The content, the field name (when using fieldName) or the field value (when using the deprecated id form) was not found.
500Internal server error. An error occurred while processing the request.