Skip to main content
PATCH
Update an experience history entry

Authorizations

Api-Token
string
header
required

Server-to-server authentication. Generate a token in the admin UI at Settings → Developers → API Access. Send the raw token in the Api-Token header — there is no Bearer prefix.

Tokens can be marked read-only at creation time, in which case the API rejects any non-GET request with 403 Forbidden.

Path Parameters

id
string
required

ExperienceHistory identifier

Body

application/merge-patch+json

The updated ExperienceHistory resource

user
string<iri-reference>
Example:

"/api/v1/users/1"

entity
string | null
yearBegin
integer | null
Required range: 1950 <= x <= 2050
yearEnd
integer | null
Required range: 1950 <= x <= 2050
position
string | null

Response

ExperienceHistory resource updated

entity
string | null
required
yearBegin
integer | null
required
Required range: 1950 <= x <= 2050
position
string | null
required
id
integer
read-only
user
string<iri-reference>
Example:

"/api/v1/users/1"

yearEnd
integer | null
Required range: 1950 <= x <= 2050