# [EXPERIMENTAL] Get Deployment

Get an existing Deployment, defined by their id. Deployments without a planning_id are externally managed Deployments. 
Deployments with a planning_id are managed by releasing or unreleasing routes in PTV OptiFlow.

Endpoint: GET /deployment/{id}
Version: 1.27.2
Security: clientCredentials

## Path parameters:

  - `id` (string, required)
    The unique ID used to identify this Deployment.

## Response 200 fields (application/json):

  - `id` (string)
    The unique deployment ID.
    Example: "deployment-123"

  - `resource_combination_id` (string)
    The ID of the associated resource combination, if any.
    Example: "rc-456"

  - `availability_id` (string)
    The ID of the associated availability, if any.
    Example: "avail-789"

  - `employee_id` (string)
    The ID of the employee assigned to this deployment.
    Example: "employee-42"

  - `transport_resource_ids` (array)
    The IDs of the transport resources assigned to this deployment.
    Example: ["truck-1","trailer-2"]

  - `start` (object)

  - `start.at` (string, required)
    When the deployment starts.
    Example: "2021-01-01T08:00:00Z"

  - `start.location` (object, required)
    Location for the deployment. For external deployments, either address or home_base must be provided, but not both.

  - `start.location.home_base` (object)
    The business_id of a known HomeBase in the system for this deployment location.

  - `start.location.home_base.business_id` (string, required)
    The unique identifier of a HomeBase.
    Example: "depot-1"

  - `start.location.address` (object)
    Address for this deployment location.

  - `start.location.address.name` (string, required)
    A name by which to identify this location. If used as a start_location, this is used for matching colocated entities.
    Example: "Conundra"

  - `start.location.address.address_line` (string)
    The address line of this location's address. Can contain street, house number, bus and more.
    Example: "Voordries 41b"

  - `start.location.address.city` (string)
    The name of the locality of this location.

Required when no geo_point is provided.
    Example: "Oosterzele"

  - `start.location.address.zip_code` (string)
    The ZIP code of the locality of this location.

Required when no geo_point is provided.
    Example: "9860"

  - `start.location.address.country_code` (string)
    The ISO3166-1 alpha-2 two letter country code for this location.

Required when no geo_point is provided.

  - `start.location.address.geo_point` (object)

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

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

  - `start.location.address.geo_point.resolved` (object)
    Indicates whether the address is resolved.

  - `start.location.address.geo_point.resolved.geocoded` (boolean)
    Example: true

  - `start.location.address.geo_point.resolved.address` (string)
    Example: "Voordries 31 bus B, 9860 Oosterzele"

  - `start.location.address.geo_point.resolved.precision` (integer)
    Example: 9

  - `end` (object)

  - `end.at` (string, required)
    When the deployment ends.
    Example: "2021-01-01T17:00:00Z"

  - `total_break_time` (string)
    Total break time during the deployment, formatted as ISO-8601 duration.
    Example: "PT1H"

  - `planning_id` (string)
    The ID of the planning that created this deployment, if any.
    Example: "planning-123"

## Response 404 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."


## Response 401 fields