# get a google earth kml file

generates a google earth kml file of the routing for the provided request uuid

Endpoint: GET /etw-rest/calculateTransport/kml
Version: 2025r4.1.4

## Query parameters:

  - `expires` (string, required)
    expiry date and time in ISO_8601 Standard UTC. YYYY-MM-DDThh:mmZ
    Example: "2007-04-05T14:30Z"

  - `uuid` (string, required)
    uuid of kml as stated in the original calculation response
    Example: "b2d738cb-2b54-4f49-8f03-db838a03d91b"

  - `signature` (string, required)
    signature to validate link
    Example: "ol3RA-NjoO2POfxEcko994JIip1EQHTM8n6uqxYS730"

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

  - `type` (string, required)
    a URI reference that identifies the problem via an errorKey. URI is not resolvable at the moment, but might be in the future
    Enum: "LOCATION", "PARAMETER", "INTERNAL", "ROUTING", "ERROR_HANDLING", "CONFIGURATION"

  - `title` (string, required)
    a short, human-readable summary of the error
    Example: "Location not found"

  - `status` (integer, required)
    indicating the HTTP status code
    Example: 400

  - `detail` (string, required)
    human-readable explanation specific to this occurrence of the problem
    Example: "could not find Location for IATA code: ZZZ"

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem
    Example: "/calculateTransport"

  - `action` (string)
    proposed action to solve the problem
    Example: "Verify location existence or define another location."

  - `timestamp` (string)
    date and time (in UTC) when the error occurred (YYYY-MM-DD)
    Example: "2024-06-30T06:39:25Z"

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

  - `type` (string, required)
    a URI reference that identifies the problem via an errorKey. URI is not resolvable at the moment, but might be in the future
    Enum: "LOCATION", "PARAMETER", "INTERNAL", "ROUTING", "ERROR_HANDLING", "CONFIGURATION"

  - `title` (string, required)
    a short, human-readable summary of the error
    Example: "Location not found"

  - `status` (integer, required)
    indicating the HTTP status code
    Example: 400

  - `detail` (string, required)
    human-readable explanation specific to this occurrence of the problem
    Example: "could not find Location for IATA code: ZZZ"

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem
    Example: "/calculateTransport"

  - `action` (string)
    proposed action to solve the problem
    Example: "Verify location existence or define another location."

  - `timestamp` (string)
    date and time (in UTC) when the error occurred (YYYY-MM-DD)
    Example: "2024-06-30T06:39:25Z"