# Update a shift link

Renames a shift link and returns it. Only the two names can be changed here - the repeat
the series was built on is fixed once its shifts exist, and the shifts themselves are
changed through the shift endpoints.
Both fields are optional and an update carrying neither is accepted; send only what you
are changing. `name` may be shortened or rewritten but not emptied - sending it as `null`
or as more than 255 characters is a 422.
The link has to belong to the event in the URL; a mismatch is a 404.

Endpoint: PUT /api/v2/event/{event_id}/shift/link/{id}
Version: 2.0.0
Security: default

## Path parameters:

  - `event_id` (integer, required)
    The ID of the event.

  - `id` (integer, required)
    The ID of the shift link.

## Header parameters:

  - `Rosterfy-Platform` (string)

## Request fields (application/json):

  - `name` (string)
    The name of the series, as it reads to your team. Up to 255 characters, and it may not be emptied.

  - `frontend_name` (object)
    The name of the series as volunteers see it, keyed by locale code - for example `{"en-US": "Saturday gate crew"}`. Only the locales you send are replaced; any others already stored are kept. A plain string is also accepted and is filed under the locale the request is being read in.

## Response 200 fields (application/json):

  - `object` (object)

  - `object.id` (integer)

  - `object.event_id` (integer)

  - `object.event_shift_pattern_id` (string | null)

  - `object.name` (string)

  - `object.frontend_name` (string)

  - `object.repeat` (integer)

  - `object.end_date` (string | null)

  - `object.rules` (object)

  - `object.rules.days` (array)

  - `object.created_at` (string)

  - `object.updated_at` (string)

  - `nice` (array)

  - `relations` (array)

  - `permissions` (object)

  - `permissions.read` (boolean)

  - `permissions.update` (boolean)

  - `permissions.delete` (boolean)