Update an entry
What it does
Section titled “What it does”Updates an entry’s technical name, base term, and/or context info. This endpoint does not move the entry to another group.
Request
Section titled “Request”PATCH /api/v1/entries/{id}
| Auth | Required |
| Query parameters | None |
Path parameters
Section titled “Path parameters”| Name | Type | Description |
|---|---|---|
id | string | Entry id |
Headers
Section titled “Headers”Authorization: Bearer <your-api-key>Content-Type: application/jsonAll fields optional:
{ "technicalName": "labelLegalImprint", "baseTerm": "Legal imprint", "contextInfo": null}| Field | Type | Description |
|---|---|---|
technicalName | string | null | New technical name |
baseTerm | string | null | New base term |
contextInfo | string | null | New context, or null to clear |
Example
Section titled “Example”curl -sS -X PATCH https://collingo.app/api/v1/entries/clentry0123456789abcdefg \ -H "Authorization: Bearer <your-api-key>" \ -H "Content-Type: application/json" \ -d '{"baseTerm": "Legal imprint"}'Response
Section titled “Response”200 OK
Section titled “200 OK”{ "id": "clentry0123456789abcdefg", "groupId": "clgroupaaaaaaaaaaaaaaaaaa", "technicalName": "labelImprint", "baseTerm": "Legal imprint", "contextInfo": "Footer legal link", "createdAt": "2026-07-01T12:15:00Z"}Errors
Section titled “Errors”| Status | When |
|---|---|
400 | Validation failed |
401 | Missing or invalid API key (ERR_UNAUTHORIZED) |
403 | Insufficient role (ERR_FORBIDDEN) |
404 | Entry not found |
409 | Duplicate technical name |
500 | Database or internal error |