Rename entry or change its slug
update_entryUpdate a collection entry's metadata only (name and/or slug). Partial update: provided fields are changed, omitted fields are preserved. This does NOT change the entry's content fields (use save_entry_content for those; the built-in name and slug keys are refused there). A slug must be lowercase letters, numbers and hyphens, and free in the collection. For an entry with a page the new slug is a PENDING address (get_entry shows it as draftSlug): the page keeps its current address until the next publish_entry, which moves it and, by default, redirects the old address. Passing the current address back cancels the pending move. For an entry without a page the slug changes immediately. On a collection whose name and slug are the built-in types, the name is live data: listings on the published site show a new name without a publish. An older collection may keep them as plain text fields inside content, which is what its listings show; when that copy still matches the old value it is updated too, in the draft, so listings show it after the next publish_entry (the result says so in contentCopy). A copy that differs is left alone and the result says to change it with save_entry_content.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Updated entry name | |
| slug | No | Updated URL slug (lowercase letters, numbers and hyphens). Pending until publish when the entry has a page. | |
| entryId | Yes | The entry ID | |
| projectId | Yes | The project ID |