# [EXPERIMENTAL] Upsert Forecast

Upsert a single Forecast

Endpoint: PUT /resource-overview/{date}/{location}/forecasts
Version: 1.27.2
Security: clientCredentials

## Path parameters:

  - `date` (string, required)
    Date for which to upsert a forecast
    Example: "2023-10-01"

  - `location` (string, required)
    Name of the location for which to upsert the forecast
    Example: "Ghent"

## Header parameters:

  - `Prefer` (array)
    The RFC7240 Prefer header indicates that a particular server behavior
is preferred by the client but is not required for successful completion
of the request (see RFC 7240).

The following behavior (see _Examples_) is supported by this API:
* return= is used to suggest the server to
  return using 204 without resource (minimal) or using 200 or 201 with
  resource (representation) in the response body on success.

## Request fields (application/json):

  - `expected_shifts` (integer)
    Expected number of shifts
    Example: 27

## Response 201 fields (application/json):

  - `expected_shifts` (integer)
    Expected number of shifts
    Example: 27

  - `location` (string)
    Name of the location
    Example: "Ghent"

  - `date` (string)
    Date of the forecast
    Example: "2023-10-01"

## Response 400 fields (application/problem+json):

  - `title` (string)
    A short, summary of the problem.
    Example: "Validation exception"

  - `detail` (string)
    A detailed explanation specific to this problem.
    Example: "The field contains invalid business formatting."

  - `violations` (array)

  - `violations.field` (string)
    Example: "path.to.field"

  - `violations.message` (string)
    Example: "Field is required"


## Response 204 fields

## Response 401 fields