chore: remove an obsolete file

chore: remove an obsolete file

don't know what the RAML is about. it's been added some years ago and i can't
find any reference to it, so let's remove it!

Closes DCOS-50293

#%RAML 0.8
title: Unit Health Checks API Spec
version: v1
baseUri: /api/{version}/system/health
mediaType: application/json
schemas:
  - units: !include ../../schema/unit-health/units.json
  - unit: !include ../../schema/unit-health/unit.json
  - nodes: !include ../../schema/unit-health/nodes.json
  - node: !include ../../schema/unit-health/node.json

/units:
  displayName: Units Health
  get:
    description: Get a list of units and their health status.
    responses:
      200:
        description: Successful response.
        body:
          application/json:
            schema: units
            example: |
              {
                "units": [
                  {
                    "id": "dcos-marathon.service",
                    "description": "A Long Running Jobs Scheduler",
                    "health": 0,
                  },
                  {
                    "id": "dcos-mesos-dns.service",
                    "description": "Mesos DNS",
                    "health": 1,
                  },
                  {
                    "id": "dcos-mesos-master.service",
                    "description": "The Mesos master service",
                    "health": 0,
                  },
                  {
                    "id": "dcos-nginx.service",
                    "description": "A High performance web proxy",
                    "health": 0,
                  }
                ]
              }
  /{unit-id}:
    uriParameters:
      unit-id:
        description: Requested unit.
        type: string
    displayName: Unit Health
    get:
      description: Get the unit health summaries by node_id.
      responses:
        200:
          description: Successful response.
          body:
            application/json:
              schema: unit
              example: |
                # Example query for nginx_service in a 3-master cluster would return the unit
                # health on the 3 masters on which that unit runs.
                {
                  "id": "dcos-nginx.service",
                  "description": "nginx service",
                  "health": 0,
                }
    /nodes:
      displayName: Unit Nodes Health
      get:
        description: Get a list of the units node health summaries.
        responses:
          200:
            description: Successful response.
            body:
              application/json:
                schema: nodes
                example: |
                  # Example response from a 2-node cluster where one node has units with health > 0
                  {
                    "nodes": [
                      {
                        "host_ip": "10.10.0.235",
                        "role": "master",
                        "health": 0,
                      },
                      {
                        "host_ip": "10.10.0.235",
                        "role": "agent",
                        "health": 1
                      }
                    ]
                  }
      # Must ensure all hostname's contain are hyphened and not "." separated. Only matters if we go
      # through a proxy of some sort, but generally not great to "." separate in our URL requested.
      /{node-id}:
        uriParameters:
          node-id:
            description: Requested node.
            type: string
        displayName: Node Health
        get:
          description: Get node health status.
          responses:
            200:
              description: Successful response.
              body:
                application/json:
                  schema: node
                  example: |
                    # Example response from a healthy node with all units == 0
                    {
                      "host_ip": "10.10.0.236",
                      "role": "agent",
                      "health": 1,
                      "output" "... journald..."
                      "help": "Please try `dcos node ssh ..."
                    }

/nodes:
  displayName: Nodes
  get:
    description: Get a list of nodes with their accumulated healths.
    responses:
      200:
        description: Successful response.
        body:
          application/json:
            schema: nodes
            example: |
              {
                "nodes": [
                  {
                    "host_ip: "10.10.0.235",
                    "role": "master",
                    "health": 1
                  },
                  {
                    "host_ip: "10.10.0.236",
                    "role": "agent",
                    "health": 1
                  }
                ]
              }
  /{node-id}:
    uriParameters:
      node-id:
        description: Node ID
        type: string
    displayName: Node
    get:
      description: Requested node.
      responses:
        200:
          description: Successful response.
          body:
            application/json:
              schema: node
              example: |
                {
                  "host_ip: "10.10.0.236",
                  "role": "agent",
                  "health": 1
                }
    /units:
      displayName: Units Health
      get:
        description: Units residing on requested node.
        responses:
          200:
            description: Successful response.
            body:
              application/json:
                schema: units
                example: |
                  {
                    "units": [
                      {
                        "id": "dcos-marathon.service",
                        "description": "marathon service",
                        "health": 0,
                        "output": "OK",
                        "help": "NA"
                      },
                      {
                        "id": "mesos_dns_service",
                        "description": "mesos dns service",
                        "health": 1,
                        "output": "Here are some journald logs, log log log.",
                        "help": "Mesos Dns Service failed to start on host ip-10.0.0.1. Please see `systemctl -u mesos-dns.service` for more information"
                      }
                    ]
                  }
      /{unit-id}:
        uriParameters:
          unit-id:
            description: Requested unit.
            type: string
        displayName: Unit Health
        get:
          description: Get the unit health summaries by node_id.
          responses:
            200:
              description: Successful response.
              body:
                application/json:
                  schema: unit
                  example: |
                    {
                      "id": "dcos-mesos-dns.service"
                      "description": "mesos dns service",
                      "health": 1,
                      "output": "Here are some journald logs, log log log.",
                      "help": "Mesos Dns Service failed to start on host ip-10.0.0.1. Please see `systemctl -u mesos-dns.service` for more information"
                    }

/report:
  displayName: Health Report
  get:
    description: Get a full report of units health and nodes health.
    responses:
      200:
        description: Successful response.
        body:
          application/json:
            example: |
              {
                "nodes": {},
                "units": {}
              }


api: Add `POST /upload`

api: Add `POST /upload`

#%RAML 0.8
---
title: Coverit
version: 0.0.1
baseUri: http://api.coverit.io/
mediaType:  application/json
securedBy: [oauth_2_0]

documentation:
    - title: Objects
      content: !include README.md

securitySchemes:
    - oauth_2_0: !include http://raml.link/securitySchemes/oauth_2_0.yml

/upload:
    displayName: Upload coverage report
    post:
        description: |
            Upload coverage report
        body:
            application/x-www-form-urlencoded:
                formParameters:
                    token:
                        description: Repo Token
                        type: string
                        required: true
                        example: AFNetworking/AFNetworking
                    report:
                        description: Report file, it's type should carried in `Content-Type`
                        type: file
                    git_commit:
                        description: Git commit sha in 10 chars
                        type: string
                        required: true
                        example: 09b26bf784
                    git_branch:
                        description: Git branch
                        type: string
                        required: true
                        example: master

/builds:
    displayName: Build
    post:
        description: |
            Create a new build
        body:
            application/x-www-form-urlencoded:
                formParameters:
                    project_name:
                        description: Project name
                        type: string
                        required: true
                        example: AFNetworking/AFNetworking
                    gcno:
                        description: gcno files archive
                        type: file
                        required: true
                    git:
                        description: A hash of Git data that can be used to display more information to users.
                        type: string
                        example: '
                            "git": {
                              "head": {
                                "id": "b31f08d07ae564b08237e5a336e478b24ccc4a65",
                                "author_name": "Nick Merwin",
                                "author_email": "...",
                                "committer_name": "Nick Merwin",
                                "committer_email": "...",
                                "message": "version bump"
                              },
                              "branch": "master",
                              "remotes": [
                                {
                                  "name": "origin",
                                  "url": "git@github.com:lemurheavy/coveralls-ruby.git"
                                }
                              ]
                            }'

/reports:
    displayName: Report
    post:
        description: |
            Create a new report
        body:
            application/x-www-form-urlencoded:
                formParameters:
                    project_name:
                        description: Project name
                        type: string
                        required: true
                        example: AFNetworking/AFNetworking
                    lcov:
                        description: lcov file
                        type: file
                        required: true
                    git:
                        description: A hash of Git data that can be used to display more information to users.
                        type: string
                        example: '
                            "git": {
                              "head": {
                                "id": "b31f08d07ae564b08237e5a336e478b24ccc4a65",
                                "author_name": "Nick Merwin",
                                "author_email": "...",
                                "committer_name": "Nick Merwin",
                                "committer_email": "...",
                                "message": "version bump"
                              },
                              "branch": "master",
                              "remotes": [
                                {
                                  "name": "origin",
                                  "url": "git@github.com:lemurheavy/coveralls-ruby.git"
                                }
                              ]
                            }'

#%RAML 0.8
---
title: Coverit
version: 0.0.1
baseUri: http://api.coverit.io/
mediaType:  application/json
securedBy: [oauth_2_0]

documentation:
    - title: Objects
      content: !include README.md

securitySchemes:
    - oauth_2_0: !include http://raml.link/securitySchemes/oauth_2_0.yml

/builds:
    displayName: Build
    post:
        description: |
            Create a new build
        body:
            application/x-www-form-urlencoded:
                formParameters:
                    project_name:
                        description: Project name
                        type: string
                        required: true
                        example: AFNetworking/AFNetworking
                    gcno:
                        description: gcno files archive
                        type: file
                        required: true
                    git:
                        description: A hash of Git data that can be used to display more information to users.
                        type: string
                        example: '
                            "git": {
                              "head": {
                                "id": "b31f08d07ae564b08237e5a336e478b24ccc4a65",
                                "author_name": "Nick Merwin",
                                "author_email": "...",
                                "committer_name": "Nick Merwin",
                                "committer_email": "...",
                                "message": "version bump"
                              },
                              "branch": "master",
                              "remotes": [
                                {
                                  "name": "origin",
                                  "url": "git@github.com:lemurheavy/coveralls-ruby.git"
                                }
                              ]
                            }'

/reports:
    displayName: Report
    post:
        description: |
            Create a new report
        body:
            application/x-www-form-urlencoded:
                formParameters:
                    project_name:
                        description: Project name
                        type: string
                        required: true
                        example: AFNetworking/AFNetworking
                    lcov:
                        description: lcov file
                        type: file
                        required: true
                    git:
                        description: A hash of Git data that can be used to display more information to users.
                        type: string
                        example: '
                            "git": {
                              "head": {
                                "id": "b31f08d07ae564b08237e5a336e478b24ccc4a65",
                                "author_name": "Nick Merwin",
                                "author_email": "...",
                                "committer_name": "Nick Merwin",
                                "committer_email": "...",
                                "message": "version bump"
                              },
                              "branch": "master",
                              "remotes": [
                                {
                                  "name": "origin",
                                  "url": "git@github.com:lemurheavy/coveralls-ruby.git"
                                }
                              ]
                            }'


Update xsd path for tracking version 2

Update xsd path for tracking version 2

#%RAML 1.0
---
title: Tracking API
version: v2
baseUri: https://tracking.bring.com/api
types:
  Consignment:
    type: object
    properties:
      consignmentSet:
        type: ConsignmentSet
      apiVersion:
        type: ApiVersion
  ConsignmentSet:
    type: object
    description: ?
    properties:
      consignmentId:
        type: string
      previousConsignmentId:
        type: string
        required: false
      packageSet:
        type: Package[]
      recipientAddress:
        type: Address
      recipientHandlingAddress:
        type: Address
      senderReference:
        type: string
      senderCustomerNumber:
        type: string
      senderCustomerMasterNumber:
        type: string
      senderName:
        type: string
      senderAddress:
        type: Address
      senderCustomerType:
        type: string
      recipientCustomerNumber:
        type: string
      recipientCustomerMasterNumber:
        type: string
      recipientCustomerType:
        type: string
      isPickupNoticeAvailable:
        type: boolean
      consignmentActionSet:
        type: ConsignmentAction
      totalWeightInKgs:
        type: number
      totalVolumeInDm3:
        type: number
  ApiVersion:
    type: object
  ConsignmentAction:
    type: object
    properties:
      actionType:
        type: string
      actionURL:
        type: string
  Package:
    type: object
    properties:
      statusDescription:
        type: string
      descriptions:
        type: string[]
        required: false
      packageNumber:
        type: string
      previousPackageNumber:
        type: string
      productName:
        type: string
      productCode:
        type: string
      productLink:
        type: string
      brand:
        type: string
      lengthInCm:
        type: number
      widthInCm:
        type: number
      heightInCm:
        type: number
      volumeInDm3:
        type: number
      weightInKgs:
        type: number
      pickupCode:
        type: string
      dateOfReturn:
        type: string
      senderName:
        type: string
      senderAddress:
        type: Address
      recipientAddress:
        type: Address
      recipientHandlingAddress:
        type: Address
      eventSet:
        type: Event[]
      additionalServiceSet:
        type: object[]
        required: false
  Event:
    type: object
    properties:
      description: string
      status:
        type: string
      recipientSignature:
        type: NamedElement
      unitId:
        type: string
      unitType:
        type: string
      postalCode:
        type: string
        required: false
      city:
        type: string
        required: false
      countryCode:
        type: string
        required: false
      country:
        type: string
        required: false
      dateIso:
        type: string
      displayDate:
        type: string
      displayTime:
        type: string
      consignmentEvent:
        type: boolean
      insignificant:
        type: boolean
  Address:
    type: object
    properties:
      addressLine1:
        type: string
        required: false
      addressLine2:
        type: string
        required: false
      postalCode:
        type: string
        required: false
      city:
        type: string
        required: false
      countryCode:
        type: string
        required: false
      country:
        type: string
        required: false
  NamedElement:
    type: object
    properties:
      name:
        type: string
        required: false

documentation:
- title: Introduction
  content: |
      The Tracking API provides the opportunity to track shipments by reference, package or shipment number.
      It is an easy way to display details and the status of shipments.
      The information available in this API is the same that is publically available from the [Tracking web site](http://tracking.bring.com/).

- title: Formats
  content: |
    The Tracking API generates the following formats:
    - ```XML```
    - ```JSON```
    - ```JSONP```
- title: Versioning
  content: |
    Latest Tracking API version: `v2`

    We encourage you to use the latest version of our API all time.  Of course, we keep the previous version for some time so that you will get enough time to convert your application. This API supports versioning by two means.

    - **Select version by request-header**
      Use the normal URL but add the following request-header:

      | Header | Example |
      |:-------|:--------|
      | `api-version` | `2` |

      **Example request**
      ```curl -H "api-version: 2" https://tracking.bring.com/api/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT```

    - **Select version by URL**
      Use the normal URL, but add **```{v1, v2}```** to the URL. Example:

      | Application | URL example |
      |:-------|:--------|
      | Open tracking | https://tracking.bring.com/api/**v2**/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT |
      | Logged-in tracking | https://mybring.com/tracking/api/**v2**/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT |

      You can verify that your request were used correctly by certifying that the response contains an element based on the request type:

      | URI request | Response type | Example |
      |:-------|:--------|:--------|
      | tracking.json | `application/json; charset=utf-8` | `{"apiVersion": "2"}` |
      | tracking.xml | `application/xml;charset=utf-8` | `<ApiVersion>2</ApiVersion>` |

      **Example request**
      ```curl -v https://tracking.bring.com/api/v2/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT```

- title: Authentication
  content: |
    If you are a Mybring user, you can authenticate requests to the Tracking API. Authenticated requests have the following benefits:

    - More information about parcels:
      - Prices
      - Name
      - Address
      - Signatures for proof of develiery
    - Less strict rate limiting

    See the [getting started guide on authentication](/api/#authentication) if you're not sure what this means.

    | Header | Example | Comment |
    |:-------|:--------|:--------|
    | `X-MyBring-API-Uid` | `john.doe@example.com` | Mybring login ID |
    | `X-MyBring-API-Key` | `1234abc-abcd-1234-5678-abcd1234abcd ` | Mybring login's API key |
    | `X-Bring-Client-URL` | `https://example.com/` | A URL that sort of identifies where you're using the APIs. |

    Those headers must be present for authenticating requests, and you have to use the endpoint

        https://www.mybring.com/tracking/api/
- title: JSON API
  content: |
      We follow the [JSON API](http://jsonapi.org/) specification with one
      exception: we allow media type to be specified as `application/json`
      instead of `application/vnd.api+json`.

/{version}/tracking{mediaTypeExtension}:
  displayName: Tracking endpoint
  description: Get information about an existing shipment based on a tracking number, shipment number or reference.
  uriParameters:
    version:
      enum: [ v1, v2 ]
      description: v1 is deprecated and will be removed soon. Use v2 when requesting the tracking API
    mediaTypeExtension:
      enum: [ .json, .xml ]
      description: Use .json to specify application/json or .xml to specify application/xml
  get:
    description: Get information about a shipment
    headers:
      X-MyBring-API-Uid:
        description: Your Mybring login ID
      X-MyBring-API-Key:
        description: Your user's API key
      X-Bring-Client-URL:
        description: A URL that sort of identifies where you're using the APIs.
    queryParameters:
      q:
        description: Reference, package number, shipment number to search for
        type: string
        required: true
        example: TESTPACKAGE-AT-PICKUPPOINT, 370000000000000001
      aktornummer:
        description: Represents a valid customer number registered with Posten
        type: string
        required: false
        example: "12345678901"
      callback:
        description: JSONP callback function name
        type: string
        required: false
    responses:
      200:
        displayName: Successful response
        description: |
          For testing you can use "TESTPACKAGE-AT-PICKUPPOINT" as the tracking number to generate test results. For real tracking this must be a valid number.

          You can find an XSD for the XML response here: [tracking-v2.xsd](https://tracking.bring.com/schema/api/tracking-v2.xsd).

          A parcel has a number of events connected to it during its travel. Here are a list of current event statuses that can be returned.

          | Event | Description |
          |:-------|:--------|
          | `ARRIVED_DELIVERY` | Arrived Delivery point - This is when a container arrives at recipients address, and can start unloading.
 |
          | `ARRIVED_COLLECTION` | Arrived for collection at pickup point |
          | `ATTEMPTED_DELIVERY` | The package has been attempted delivered at the door. Depending on the service it will be tried again or sent to closest pickup point. |
          | `CUSTOMS` | Package is in customs clearance. |
          | `COLLECTED` | The parcel has been collected at pickup address. |
          | `DELIVERED` | Package has been delivered. |
          | `DELIVERED_SENDER` | Package has been returned to the sender |
          | `DELIVERY_CANCELLED` | Home delivery has been canceled by the customer. |
          | `DELIVERY_CHANGED` | Date for Home delivery has been changed by customer. |
          | `DELIVERY_ORDERED` | Home delivery has been ordered |
          | `DEVIATION` | Deviation in production. Something wrong has happened and there is a probability for delay. |
          | `HANDED_IN` | Package has been handed in to Bring. |
          | `INTERNATIONAL` | Package has been sent from origin country or arrived at destination country.
 |
          | `IN_TRANSIT` | Package is in transit. |
          | `NOTIFICATION_SENT` | Notification for this package has been sent by sms, push and/or mail. This can be informational notifications and action notification like pickup notice. |
          | `PRE_NOTIFIED` | EDI message for the package has been received by Bring. |
          | `READY_FOR_PICKUP` | Package has arrived at pickup point. |
          | `RETURN` | The package has been returned to sender.
 |
          | `TRANSPORT_TO_RECIPIENT` | Package has been loaded for delivery to the recipient. |
          | `TERMINAL` | The package is now registered/arrived at inbound/outbound storage terminal |
          | `UNKNOWN` | Represents unknown / undefined events |

        body:
          application/json:
            type: Consignment
            examples:
              successful:
                displayName: Successful
                description: The example below shows an successful deliverance of a package at a pickup point
                value: !include examples/successful.json
              unsuccessful:
                displayName: Unsuccessful request
                description: Returned upon no search responses being returned for the request itself
                value: !include examples/unsuccessful.json
              notification_received:
                displayName: Unreceived package, with notification regarding EDI
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/notification_received.json
              waiting_at_pup:
                displayName: Waiting at Pickup Point
                description: The example below is showing a package waiting for the recipient to collect it at a pickup point
                value: !include examples/waiting_at_pup.json
              loaded_for_delivery:
                displayName: Package loaded for delivery
                description: The example below is showing a package that has been loaded on a distribution car for delivery to the reciepient.
                value: !include examples/loaded_for_delivery.json
              delivered:
                displayName: Package delivered to customer
                description: The example below is showing a package that has been delivered to the reciepient.
                value: !include examples/delivered.json
          application/xml:
            type: Consignment
            examples:
              successful:
                displayName: Successful
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/successful.xml
              unsuccessful:
                displayName: Unsuccessful request
                description: Returned upon no search responses being returned for the request itself
                value: !include examples/unsuccessful.xml
              notification_received:
                displayName: Unreceived package, with notification regarding EDI
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/notification_received.xml
              waiting_at_pup:
                displayName: Waiting at Pickup Point
                description: The example below is showing a package waiting for the recipient to collect it at a pickup point
                value: !include examples/waiting_at_pup.xml
              loaded_for_delivery:
                displayName: Package loaded for delivery
                description: The example below is showing a package that has been loaded on a distribution car for delivery to the reciepient.
                value: !include examples/loaded_for_delivery.xml
              delivered:
                displayName: Package delivered to customer
                description: The example below is showing a package that has been delivered to the reciepient.
                value: !include examples/delivered.xml

#%RAML 1.0
---
title: Tracking API
version: v2
baseUri: https://tracking.bring.com/api
types:
  Consignment:
    type: object
    properties:
      consignmentSet:
        type: ConsignmentSet
      apiVersion:
        type: ApiVersion
  ConsignmentSet:
    type: object
    description: ?
    properties:
      consignmentId:
        type: string
      previousConsignmentId:
        type: string
        required: false
      packageSet:
        type: Package[]
      recipientAddress:
        type: Address
      recipientHandlingAddress:
        type: Address
      senderReference:
        type: string
      senderCustomerNumber:
        type: string
      senderCustomerMasterNumber:
        type: string
      senderName:
        type: string
      senderAddress:
        type: Address
      senderCustomerType:
        type: string
      recipientCustomerNumber:
        type: string
      recipientCustomerMasterNumber:
        type: string
      recipientCustomerType:
        type: string
      isPickupNoticeAvailable:
        type: boolean
      consignmentActionSet:
        type: ConsignmentAction
      totalWeightInKgs:
        type: number
      totalVolumeInDm3:
        type: number
  ApiVersion:
    type: object
  ConsignmentAction:
    type: object
    properties:
      actionType:
        type: string
      actionURL:
        type: string
  Package:
    type: object
    properties:
      statusDescription:
        type: string
      descriptions:
        type: string[]
        required: false
      packageNumber:
        type: string
      previousPackageNumber:
        type: string
      productName:
        type: string
      productCode:
        type: string
      productLink:
        type: string
      brand:
        type: string
      lengthInCm:
        type: number
      widthInCm:
        type: number
      heightInCm:
        type: number
      volumeInDm3:
        type: number
      weightInKgs:
        type: number
      pickupCode:
        type: string
      dateOfReturn:
        type: string
      senderName:
        type: string
      senderAddress:
        type: Address
      recipientAddress:
        type: Address
      recipientHandlingAddress:
        type: Address
      eventSet:
        type: Event[]
      additionalServiceSet:
        type: object[]
        required: false
  Event:
    type: object
    properties:
      description: string
      status:
        type: string
      recipientSignature:
        type: NamedElement
      unitId:
        type: string
      unitType:
        type: string
      postalCode:
        type: string
        required: false
      city:
        type: string
        required: false
      countryCode:
        type: string
        required: false
      country:
        type: string
        required: false
      dateIso:
        type: string
      displayDate:
        type: string
      displayTime:
        type: string
      consignmentEvent:
        type: boolean
      insignificant:
        type: boolean
  Address:
    type: object
    properties:
      addressLine1:
        type: string
        required: false
      addressLine2:
        type: string
        required: false
      postalCode:
        type: string
        required: false
      city:
        type: string
        required: false
      countryCode:
        type: string
        required: false
      country:
        type: string
        required: false
  NamedElement:
    type: object
    properties:
      name:
        type: string
        required: false

documentation:
- title: Introduction
  content: |
      The Tracking API provides the opportunity to track shipments by reference, package or shipment number.
      It is an easy way to display details and the status of shipments.
      The information available in this API is the same that is publically available from the [Tracking web site](http://tracking.bring.com/).

- title: Formats
  content: |
    The Tracking API generates the following formats:
    - ```XML```
    - ```JSON```
    - ```JSONP```
- title: Versioning
  content: |
    Latest Tracking API version: `v2`

    We encourage you to use the latest version of our API all time.  Of course, we keep the previous version for some time so that you will get enough time to convert your application. This API supports versioning by two means.

    - **Select version by request-header**
      Use the normal URL but add the following request-header:

      | Header | Example |
      |:-------|:--------|
      | `api-version` | `2` |

      **Example request**
      ```curl -H "api-version: 2" https://tracking.bring.com/api/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT```

    - **Select version by URL**
      Use the normal URL, but add **```{v1, v2}```** to the URL. Example:

      | Application | URL example |
      |:-------|:--------|
      | Open tracking | https://tracking.bring.com/api/**v2**/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT |
      | Logged-in tracking | https://mybring.com/tracking/api/**v2**/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT |

      You can verify that your request were used correctly by certifying that the response contains an element based on the request type:

      | URI request | Response type | Example |
      |:-------|:--------|:--------|
      | tracking.json | `application/json; charset=utf-8` | `{"apiVersion": "2"}` |
      | tracking.xml | `application/xml;charset=utf-8` | `<ApiVersion>2</ApiVersion>` |

      **Example request**
      ```curl -v https://tracking.bring.com/api/v2/tracking.json?q=TESTPACKAGE-AT-PICKUPPOINT```

- title: Authentication
  content: |
    If you are a Mybring user, you can authenticate requests to the Tracking API. Authenticated requests have the following benefits:

    - More information about parcels:
      - Prices
      - Name
      - Address
      - Signatures for proof of develiery
    - Less strict rate limiting

    See the [getting started guide on authentication](/api/#authentication) if you're not sure what this means.

    | Header | Example | Comment |
    |:-------|:--------|:--------|
    | `X-MyBring-API-Uid` | `john.doe@example.com` | Mybring login ID |
    | `X-MyBring-API-Key` | `1234abc-abcd-1234-5678-abcd1234abcd ` | Mybring login's API key |
    | `X-Bring-Client-URL` | `https://example.com/` | A URL that sort of identifies where you're using the APIs. |

    Those headers must be present for authenticating requests, and you have to use the endpoint

        https://www.mybring.com/tracking/api/
- title: JSON API
  content: |
      We follow the [JSON API](http://jsonapi.org/) specification with one
      exception: we allow media type to be specified as `application/json`
      instead of `application/vnd.api+json`.

/{version}/tracking{mediaTypeExtension}:
  displayName: Tracking endpoint
  description: Get information about an existing shipment based on a tracking number, shipment number or reference.
  uriParameters:
    version:
      enum: [ v1, v2 ]
      description: v1 is deprecated and will be removed soon. Use v2 when requesting the tracking API
    mediaTypeExtension:
      enum: [ .json, .xml ]
      description: Use .json to specify application/json or .xml to specify application/xml
  get:
    description: Get information about a shipment
    headers:
      X-MyBring-API-Uid:
        description: Your Mybring login ID
      X-MyBring-API-Key:
        description: Your user's API key
      X-Bring-Client-URL:
        description: A URL that sort of identifies where you're using the APIs.
    queryParameters:
      q:
        description: Reference, package number, shipment number to search for
        type: string
        required: true
        example: TESTPACKAGE-AT-PICKUPPOINT, 370000000000000001
      aktornummer:
        description: Represents a valid customer number registered with Posten
        type: string
        required: false
        example: "12345678901"
      callback:
        description: JSONP callback function name
        type: string
        required: false
    responses:
      200:
        displayName: Successful response
        description: |
          For testing you can use "TESTPACKAGE-AT-PICKUPPOINT" as the tracking number to generate test results. For real tracking this must be a valid number.

          You can find an XSD for the XML response here: [tracking-v2.xsd](https://tracking.bring.com/api/schema/sporing-v2.xsd).

          A parcel has a number of events connected to it during its travel. Here are a list of current event statuses that can be returned.

          | Event | Description |
          |:-------|:--------|
          | `ARRIVED_DELIVERY` | Arrived Delivery point - This is when a container arrives at recipients address, and can start unloading.
 |
          | `ARRIVED_COLLECTION` | Arrived for collection at pickup point |
          | `ATTEMPTED_DELIVERY` | The package has been attempted delivered at the door. Depending on the service it will be tried again or sent to closest pickup point. |
          | `CUSTOMS` | Package is in customs clearance. |
          | `COLLECTED` | The parcel has been collected at pickup address. |
          | `DELIVERED` | Package has been delivered. |
          | `DELIVERED_SENDER` | Package has been returned to the sender |
          | `DELIVERY_CANCELLED` | Home delivery has been canceled by the customer. |
          | `DELIVERY_CHANGED` | Date for Home delivery has been changed by customer. |
          | `DELIVERY_ORDERED` | Home delivery has been ordered |
          | `DEVIATION` | Deviation in production. Something wrong has happened and there is a probability for delay. |
          | `HANDED_IN` | Package has been handed in to Bring. |
          | `INTERNATIONAL` | Package has been sent from origin country or arrived at destination country.
 |
          | `IN_TRANSIT` | Package is in transit. |
          | `NOTIFICATION_SENT` | Notification for this package has been sent by sms, push and/or mail. This can be informational notifications and action notification like pickup notice. |
          | `PRE_NOTIFIED` | EDI message for the package has been received by Bring. |
          | `READY_FOR_PICKUP` | Package has arrived at pickup point. |
          | `RETURN` | The package has been returned to sender.
 |
          | `TRANSPORT_TO_RECIPIENT` | Package has been loaded for delivery to the recipient. |
          | `TERMINAL` | The package is now registered/arrived at inbound/outbound storage terminal |
          | `UNKNOWN` | Represents unknown / undefined events |

        body:
          application/json:
            type: Consignment
            examples:
              successful:
                displayName: Successful
                description: The example below shows an successful deliverance of a package at a pickup point
                value: !include examples/successful.json
              unsuccessful:
                displayName: Unsuccessful request
                description: Returned upon no search responses being returned for the request itself
                value: !include examples/unsuccessful.json
              notification_received:
                displayName: Unreceived package, with notification regarding EDI
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/notification_received.json
              waiting_at_pup:
                displayName: Waiting at Pickup Point
                description: The example below is showing a package waiting for the recipient to collect it at a pickup point
                value: !include examples/waiting_at_pup.json
              loaded_for_delivery:
                displayName: Package loaded for delivery
                description: The example below is showing a package that has been loaded on a distribution car for delivery to the reciepient.
                value: !include examples/loaded_for_delivery.json
              delivered:
                displayName: Package delivered to customer
                description: The example below is showing a package that has been delivered to the reciepient.
                value: !include examples/delivered.json
          application/xml:
            type: Consignment
            examples:
              successful:
                displayName: Successful
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/successful.xml
              unsuccessful:
                displayName: Unsuccessful request
                description: Returned upon no search responses being returned for the request itself
                value: !include examples/unsuccessful.xml
              notification_received:
                displayName: Unreceived package, with notification regarding EDI
                description: The example below is showing a package that have been EDI notified, but is not received by Bring.
                value: !include examples/notification_received.xml
              waiting_at_pup:
                displayName: Waiting at Pickup Point
                description: The example below is showing a package waiting for the recipient to collect it at a pickup point
                value: !include examples/waiting_at_pup.xml
              loaded_for_delivery:
                displayName: Package loaded for delivery
                description: The example below is showing a package that has been loaded on a distribution car for delivery to the reciepient.
                value: !include examples/loaded_for_delivery.xml
              delivered:
                displayName: Package delivered to customer
                description: The example below is showing a package that has been delivered to the reciepient.
                value: !include examples/delivered.xml