# Upsert depot set

Create or update a depot set. A unique ID (business_id) is required to identify the depot set.
Calling this endpoint with an existing business_id will update the depot set.

Endpoint: PUT /locations/depot-sets/{business_id}
Version: 1.5.0
Security: clientCredentials

## Path parameters:

  - `business_id` (string, required)
    The unique identifier of an entity

## Header parameters:

  - `If-Match` (string)
    Weak Etag used for optimistic locking.
    Example: "W/\"24\""

## Request fields (application/json):

  - `name` (string, required)
    The name of the depot set
    Example: "Belgian Depots"

  - `depots` (array, required)
    List of depots in this set

  - `depots.business_id` (string, required)
    Identifier of a depot unique within the set
    Example: "depot-ghent"

  - `depots.name` (string, required)
    Name of the depot
    Example: "Depot Ghent"

  - `depots.address` (object, required)
    Address information for the depot.
When geo_point is provided, address fields (address_line, city, zip_code, country_code) are optional.
When geo_point is omitted, address fields must be provided so that the address can be geo-coded.

  - `depots.address.address_line` (string)
    The part of the address that includes the street name, house number, bus number etc. 
Required when omitting geo_point.
    Example: "Voordries 41"

  - `depots.address.city` (string)
    City name. Required when omitting geo_point.
    Example: "Oosterzele"

  - `depots.address.zip_code` (string)
    Postal code. Required when omitting geo_point.
    Example: "9860"

  - `depots.address.country_code` (string)
    represents the ISO3166-1 alpha-2 two letter country codes

  - `depots.address.geo_point` (object)

  - `depots.address.geo_point.latitude` (number, required)
    Example: 50.9514048

  - `depots.address.geo_point.longitude` (number, required)
    Example: 3.8067878

  - `depots.stop_time` (string)
    Stop time at the depot in ISO-8601 duration format
    Example: "PT5M"

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

  - `type` (string, required)
    An absolute URI that identifies the problem type.  When dereferenced,
it SHOULD provide human-readable documentation for the problem type
(e.g., using HTML).
    Example: "https://developer.conundra.eu/developer-portal/problem/#constraint-violation"

  - `title` (string, required)
    A short, summary of the problem type. Written in english and readable
for engineers (usually not suited for non technical stakeholders and
not localized)
    Example: "Bad Request"

  - `status` (integer, required)
    The HTTP status code generated by the origin server for this occurrence
of the problem.
    Example: 400

  - `detail` (string, required)
    A human readable explanation specific to this occurrence of the
problem.
    Example: "Bad request. See violations for more details."

  - `violations` (array)

  - `violations.field` (string)
    A reference to the field in the request that triggered this violation.
    Example: "limit"

  - `violations.message` (string, required)
    A message explaining the violation in the referenced field.
    Example: "Limit must be strictly positive."

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

  - `type` (string, required)
    An absolute URI that identifies the problem type.  When dereferenced,
it SHOULD provide human-readable documentation for the problem type
(e.g., using HTML).
    Example: "https://developer.conundra.eu/developer-portal/problem/#constraint-violation"

  - `title` (string, required)
    A short, summary of the problem type. Written in english and readable
for engineers (usually not suited for non technical stakeholders and
not localized)
    Example: "Bad Request"

  - `status` (integer, required)
    The HTTP status code generated by the origin server for this occurrence
of the problem.
    Example: 400

  - `detail` (string, required)
    A human readable explanation specific to this occurrence of the
problem.
    Example: "Bad request. See violations for more details."

  - `violations` (array)

  - `violations.field` (string)
    A reference to the field in the request that triggered this violation.
    Example: "limit"

  - `violations.message` (string, required)
    A message explaining the violation in the referenced field.
    Example: "Limit must be strictly positive."


## Response 201 fields

## Response 204 fields

## Response 401 fields