Add event's field "original_data" to RAML documentation

#%RAML 0.8
title: CTU Sirius API
version: v1
baseUri: https://sirius.fit.cvut.cz/api/{version}
securedBy: [access_token]
securitySchemes:
  - access_token:
      description: |
        All Sirius read-only resources are secured by an access token. The token is either
        associated with an username (personal) or is set as global. This authorization
        scheme uses the same query parameter as OAuth 2.0, and will be later
        replaced by OAuth 2.0.
      type: x-access-token
      describedBy:
        queryParameters:
          access_token:
            description: |
              Used to send a valid access token.
            type: string
        responses:
          401:
            description: |
              Missing or invalid token. Authorization token was not specified or is not valid.
traits:
  - paged:
      usage: Retreive further pages in collection
      description: Use `offset` and `limit` to paginate the records.
      queryParameters:
        limit:
          description: The number of entries in collection to return
          type: number
          default: 10
          maximum: 100
        offset:
          description: Offset of the first entry in collection
          type: number
          default: 0
  - dateScoped:
      queryParameters:
        from:
          description: Return events from this date
          type: date
        to:
          description: Return events up to this date
          type: date
  - filterable:
      queryParameters:
        event_type:
          description: Filter by event's type
          type: string
          enum: [ assessment, course_event, exam, laboratory, lecture, tutorial ]
  - includable:
      description: >
        Includes the specified linked resources into the response (similar to compound documents
        in the JSON API format).
      queryParameters:
        include:
          description: A comma-separated list of the link names to include.
          type: string
          example: courses,teachers
  - secured:
      description: Marks resource as secured. You need to be authenticated and authorized to access it.
      queryParameters:
        access_token:
          description: Authentication and authorization is required. You need to set your `access_token` in URL.
          type: string
          example: 07a855e0-6920-11e4-a40a-0002a5d5c51b
          required: true
resourceTypes:
  - events-collection:
      get:
        is: [ dateScoped, filterable, includable, paged, secured ]
        responses:
          200:
            body:
              application/json:
                example: |
                    {
                      "meta": {
                        "count": 2,
                        "offset": 0,
                        "limit": 20
                      },
                      "events": [
                        {
                          "id": 42,
                          "name": null,
                          "sequence_number": 12,
                          "starts_at": "2014-04-23T09:15:00.000+02:00",
                          "ends_at": "2014-04-23T10:45:00.000+02:00",
                          "deleted" : false,
                          "capacity": 24,
                          "event_type": "tutorial",
                          "parallel": "106",
                          "original_data": {
                            "starts_at": "2014-04-23T09:00:00.000+02:00",
                            "ends_at": "2014-04-23T10:30:00.000+02:00",
                            "room_id": "T9:111"
                          },
                          "links": {
                            "room": "T9:350",
                            "course": "MI-RUB",
                            "teachers": [
                              "skocdopet"
                            ],
                            "students": [
                              "szolatib",
                              "vomackar"
                            ],
                            "applied_exceptions": [ 10, 15 ]
                          }
                        },
                        {
                          "id": 43,
                          "name": null,
                          "sequence_number": 12,
                          "starts_at": "2014-04-24T09:15:00.000+02:00",
                          "ends_at": "2014-04-24T10:45:00.000+02:00",
                          "deleted" : false,
                          "capacity": 196,
                          "event_type": "lecture",
                          "parallel": "1",
                          "original_data": {},
                          "links": {
                            "room": "T9:155",
                            "course": "MI-W20",
                            "teachers": [
                              "kuchajar",
                              "vitvatom"
                            ],
                            "students": [
                              "jirutjak"
                            ]
                          }
                        }
                      ]
                    }
              text/calendar:
                example: |
                  BEGIN:VCALENDAR
                  VERSION:2.0
                  CALSCALE:GREGORIAN
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/123
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/125
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  END:VCALENDAR
          404:
            description: There are no events within the current scope
  - event:
      get:
        is: [ secured ]
        responses:
          200:
            body:
              application/json:
                example: |
                  {
                    "events": {
                      "id": 42,
                      "name": null,
                      "sequence_number": 12,
                      "starts_at": "2014-04-23T07:30:00.000+02:00",
                      "ends_at": "2014-04-23T11:00:00.000+02:00",
                      "deleted" : false,
                      "capacity": 24,
                      "event_type": "tutorial",
                      "parallel": "106",
                      "original_data": {
                        "starts_at": "2014-04-23T09:00:00.000+02:00",
                        "ends_at": "2014-04-23T10:30:00.000+02:00",
                        "room_id": "T9:111"
                      },
                      "links": {
                        "room": "T9:350",
                        "course": "MI-RUB",
                        "teachers": [
                          "skocdopet"
                        ],
                        "students": [
                          "szolatib",
                          "vomackar"
                        ],
                        "applied_exceptions": [ 10, 15 ]
                      }
                    }
                  }
              text/calendar:
                example: |
                  BEGIN:VCALENDAR
                  VERSION:2.0
                  CALSCALE:GREGORIAN
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/123
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  END:VCALENDAR
/events:
  type: events-collection
  get:
    description: "Get all events without any scope"
  /{eventId}:
    type: event
/people/{username}/events:
  type: events-collection
  description: Get a calendar for a person
  uriParameters:
    username:
      description: person's unique username
      required: true
      pattern: "[a-z0-9]{3,8}"
      example: vomackar
/rooms/{kosId}/events:
  type: events-collection
  description: Get a calendar for a room
  uriParameters:
    kosId:
      description: |
        Common room identification used by KOS, for details see [the documentation](https://rozvoj.fit.cvut.cz/Main/znaceni-mistnosti#HKOSEDzna10DenED-102).
      required: true
      pattern: "[A-Z0-9]{2}:([A-Z0-9]+-)?[a-z0-9]+"
      example: "TH:A-1333"
/courses/{courseCode}/events:
  type: events-collection
  description: Get events instances for a given course
  uriParameters:
    courseCode:
      description: |
        Course code, faculty specific.
      required: true
      example: BI-PA1
/schedule_exceptions:
  description: Manage schedule exceptions
  is: [ paged ]
  get:
    responses:
      200:
        body:
          application/json:
            example: |
              {
                "schedule_exceptions": [
                  {
                    "id": 1,
                    "type": "CANCEL",
                    "name": "Den české státnosti",
                    "scope": {
                      "starts_at": "2014-09-28T00:00:00.000+02:00",
                      "ends_at": "2014-09-29T00:00:00.000+02:00",
                      "faculty": null,
                      "semester": null,
                      "courses": null,
                      "timetable_slots": null
                    }
                  },
                  {
                    "id": 11,
                    "type": "CANCEL"
                    "name": "Děkanský den FIT",
                    "note": "Výuka odpadá",
                    "scope": {
                      "starts_at": "2015-04-30T00:00:00Z",
                      "ends_at": "2015-05-01T00:00:00Z",
                      "faculty": 18000,
                      "semester": "B142",
                      "courses": null,
                      "timetable_slots": null
                    }
                  }
                ],
                "meta": {
                  "count": 2,
                  "offset": 0,
                  "limit": 20
                }
              }
  /{id}:
    uriParameters:
      id:
        description: ID of the schedule exception
        required: true
    get:
      responses:
        200:
          body:
            application/json:
              example: |
                {
                  "schedule_exceptions": {
                    "id": 7,
                    "type": "ROOM_CHANGE",
                    "name": "MI-MPI - přednáška 24. 9. 2014 přesunuta do T9:105",
                    "scope": {
                      "starts_at": "2014-09-24T00:00:00.000+02:00",
                      "ends_at": "2014-09-25T00:00:00.000+02:00",
                      "faculty": 18000,
                      "semester": "B141",
                      "courses": null,
                      "timetable_slots": [ 392651000 ]
                    },
                    "options": {
                      "room_id": "T9:105"
                    }
                  }
                }
/semesters:
  is: [ paged, secured ]
  get:
    description: Get all semesters per faculties.
    responses:
      200:
        body:
          application/json:
            example: |
              {
                "semesters": [
                  {
                    "id": "18000-B142",
                    "semester": "B142",
                    "faculty": 18000,
                    "starts_at": "2015-02-16",
                    "ends_at": "2015-09-21",
                    "exams_start_at": "2015-05-18",
                    "exams_end_at": "2015-06-27",
                    "teaching_ends_at": "2015-05-16",
                    "first_week_parity": "even",
                    "hour_duration": 45,
                    "hour_starts": [
                      "07:30", "08:15", "09:15", "10:00", "11:00", "11:45",
                      "12:45", "13:30", "14:30", "15:15", "16:15", "17:00",
                      "18:00", "18:45", "19:45"
                    ]
                  }
                ],
                "meta": {
                  "count": 4,
                  "offset": 0,
                  "limit": 1
                }
              }
  /{faculty_semester}:
    is: [ secured ]
    uriParameters:
      faculty_semester:
        description: Faculty code and semester code connected with a dash.
        pattern: "[0-9]{5}-[AB][0-9]{2}[12]"
        example: 18000-B142
        required: true
    get:
      description: Get a semester on a faculty.
      responses:
        200:
          body:
            application/json:
              example: |
                {
                  "semesters": {
                    "id": "18000-B142",
                    "semester": "B142",
                    "faculty": 18000,
                    "starts_at": "2015-02-16",
                    "ends_at": "2015-09-21",
                    "exams_start_at": "2015-05-18",
                    "exams_end_at": "2015-06-27",
                    "teaching_ends_at": "2015-05-16",
                    "first_week_parity": "even",
                    "hour_duration": 45,
                    "hour_starts": [
                      "07:30", "08:15", "09:15", "10:00", "11:00", "11:45",
                      "12:45", "13:30", "14:30", "15:15", "16:15", "17:00",
                      "18:00", "18:45", "19:45"
                    ]
                  }
                }

#%RAML 0.8
title: CTU Sirius API
version: v1
baseUri: https://sirius.fit.cvut.cz/api/{version}
securedBy: [access_token]
securitySchemes:
  - access_token:
      description: |
        All Sirius read-only resources are secured by an access token. The token is either
        associated with an username (personal) or is set as global. This authorization
        scheme uses the same query parameter as OAuth 2.0, and will be later
        replaced by OAuth 2.0.
      type: x-access-token
      describedBy:
        queryParameters:
          access_token:
            description: |
              Used to send a valid access token.
            type: string
        responses:
          401:
            description: |
              Missing or invalid token. Authorization token was not specified or is not valid.
traits:
  - paged:
      usage: Retreive further pages in collection
      description: Use `offset` and `limit` to paginate the records.
      queryParameters:
        limit:
          description: The number of entries in collection to return
          type: number
          default: 10
          maximum: 100
        offset:
          description: Offset of the first entry in collection
          type: number
          default: 0
  - dateScoped:
      queryParameters:
        from:
          description: Return events from this date
          type: date
        to:
          description: Return events up to this date
          type: date
  - filterable:
      queryParameters:
        event_type:
          description: Filter by event's type
          type: string
          enum: [ assessment, course_event, exam, laboratory, lecture, tutorial ]
  - includable:
      description: >
        Includes the specified linked resources into the response (similar to compound documents
        in the JSON API format).
      queryParameters:
        include:
          description: A comma-separated list of the link names to include.
          type: string
          example: courses,teachers
  - secured:
      description: Marks resource as secured. You need to be authenticated and authorized to access it.
      queryParameters:
        access_token:
          description: Authentication and authorization is required. You need to set your `access_token` in URL.
          type: string
          example: 07a855e0-6920-11e4-a40a-0002a5d5c51b
          required: true
resourceTypes:
  - events-collection:
      get:
        is: [ dateScoped, filterable, includable, paged, secured ]
        responses:
          200:
            body:
              application/json:
                example: |
                    {
                      "meta": {
                        "count": 2,
                        "offset": 0,
                        "limit": 20
                      },
                      "events": [
                        {
                          "id": 42,
                          "name": null,
                          "sequence_number": 12,
                          "starts_at": "2014-04-23T07:30:00.000+02:00",
                          "ends_at": "2014-04-23T11:00:00.000+02:00",
                          "deleted" : false,
                          "capacity": 24,
                          "event_type": "tutorial",
                          "parallel": "106",
                          "links": {
                            "room": "T9:350",
                            "course": "MI-RUB",
                            "teachers": [
                              "skocdopet"
                            ],
                            "students": [
                              "szolatib",
                              "vomackar"
                            ],
                            "applied_exceptions": [ 10, 15 ]
                          }
                        },
                        {
                          "id": 43,
                          "name": null,
                          "sequence_number": 12,
                          "starts_at": "2014-04-24T09:15:00.000+02:00",
                          "ends_at": "2014-04-24T10:45:00.000+02:00",
                          "deleted" : false,
                          "capacity": 196,
                          "event_type": "lecture",
                          "parallel": "1",
                          "links": {
                            "room": "T9:155",
                            "course": "MI-W20",
                            "teachers": [
                              "kuchajar",
                              "vitvatom"
                            ],
                            "students": [
                              "jirutjak"
                            ]
                          }
                        }
                      ]
                    }
              text/calendar:
                example: |
                  BEGIN:VCALENDAR
                  VERSION:2.0
                  CALSCALE:GREGORIAN
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/123
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/125
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  END:VCALENDAR
          404:
            description: There are no events within the current scope
  - event:
      get:
        is: [ secured ]
        responses:
          200:
            body:
              application/json:
                example: |
                  {
                    "events": {
                      "id": 42,
                      "name": null,
                      "sequence_number": 12,
                      "starts_at": "2014-04-23T07:30:00.000+02:00",
                      "ends_at": "2014-04-23T11:00:00.000+02:00",
                      "deleted" : false,
                      "capacity": 24,
                      "event_type": "tutorial",
                      "parallel": "106",
                      "links": {
                        "room": "T9:350",
                        "course": "MI-RUB",
                        "teachers": [
                          "skocdopet"
                        ],
                        "students": [
                          "szolatib",
                          "vomackar"
                        ],
                        "applied_exceptions": [ 10, 15 ]
                      }
                    }
                  }
              text/calendar:
                example: |
                  BEGIN:VCALENDAR
                  VERSION:2.0
                  CALSCALE:GREGORIAN
                  BEGIN:VEVENT
                  DTSTAMP:20140702T140133Z
                  UID:https://sirius.fit.cvut.cz/events/123
                  DTSTART:20140312T101500
                  DTEND:20140312T114500
                  CLASS:PUBLIC
                  CREATED:20140410T182546
                  LAST-MODIFIED:20140410T182546
                  LOCATION:T9:130
                  SUMMARY:MI-PSL 2. cvičení
                  END:VEVENT
                  END:VCALENDAR
/events:
  type: events-collection
  get:
    description: "Get all events without any scope"
  /{eventId}:
    type: event
/people/{username}/events:
  type: events-collection
  description: Get a calendar for a person
  uriParameters:
    username:
      description: person's unique username
      required: true
      pattern: "[a-z0-9]{3,8}"
      example: vomackar
/rooms/{kosId}/events:
  type: events-collection
  description: Get a calendar for a room
  uriParameters:
    kosId:
      description: |
        Common room identification used by KOS, for details see [the documentation](https://rozvoj.fit.cvut.cz/Main/znaceni-mistnosti#HKOSEDzna10DenED-102).
      required: true
      pattern: "[A-Z0-9]{2}:([A-Z0-9]+-)?[a-z0-9]+"
      example: "TH:A-1333"
/courses/{courseCode}/events:
  type: events-collection
  description: Get events instances for a given course
  uriParameters:
    courseCode:
      description: |
        Course code, faculty specific.
      required: true
      example: BI-PA1
/schedule_exceptions:
  description: Manage schedule exceptions
  is: [ paged ]
  get:
    responses:
      200:
        body:
          application/json:
            example: |
              {
                "schedule_exceptions": [
                  {
                    "id": 1,
                    "type": "CANCEL",
                    "name": "Den české státnosti",
                    "scope": {
                      "starts_at": "2014-09-28T00:00:00.000+02:00",
                      "ends_at": "2014-09-29T00:00:00.000+02:00",
                      "faculty": null,
                      "semester": null,
                      "courses": null,
                      "timetable_slots": null
                    }
                  },
                  {
                    "id": 11,
                    "type": "CANCEL"
                    "name": "Děkanský den FIT",
                    "note": "Výuka odpadá",
                    "scope": {
                      "starts_at": "2015-04-30T00:00:00Z",
                      "ends_at": "2015-05-01T00:00:00Z",
                      "faculty": 18000,
                      "semester": "B142",
                      "courses": null,
                      "timetable_slots": null
                    }
                  }
                ],
                "meta": {
                  "count": 2,
                  "offset": 0,
                  "limit": 20
                }
              }
  /{id}:
    uriParameters:
      id:
        description: ID of the schedule exception
        required: true
    get:
      responses:
        200:
          body:
            application/json:
              example: |
                {
                  "schedule_exceptions": {
                    "id": 7,
                    "type": "ROOM_CHANGE",
                    "name": "MI-MPI - přednáška 24. 9. 2014 přesunuta do T9:105",
                    "scope": {
                      "starts_at": "2014-09-24T00:00:00.000+02:00",
                      "ends_at": "2014-09-25T00:00:00.000+02:00",
                      "faculty": 18000,
                      "semester": "B141",
                      "courses": null,
                      "timetable_slots": [ 392651000 ]
                    },
                    "options": {
                      "room_id": "T9:105"
                    }
                  }
                }
/semesters:
  is: [ paged, secured ]
  get:
    description: Get all semesters per faculties.
    responses:
      200:
        body:
          application/json:
            example: |
              {
                "semesters": [
                  {
                    "id": "18000-B142",
                    "semester": "B142",
                    "faculty": 18000,
                    "starts_at": "2015-02-16",
                    "ends_at": "2015-09-21",
                    "exams_start_at": "2015-05-18",
                    "exams_end_at": "2015-06-27",
                    "teaching_ends_at": "2015-05-16",
                    "first_week_parity": "even",
                    "hour_duration": 45,
                    "hour_starts": [
                      "07:30", "08:15", "09:15", "10:00", "11:00", "11:45",
                      "12:45", "13:30", "14:30", "15:15", "16:15", "17:00",
                      "18:00", "18:45", "19:45"
                    ]
                  }
                ],
                "meta": {
                  "count": 4,
                  "offset": 0,
                  "limit": 1
                }
              }
  /{faculty_semester}:
    is: [ secured ]
    uriParameters:
      faculty_semester:
        description: Faculty code and semester code connected with a dash.
        pattern: "[0-9]{5}-[AB][0-9]{2}[12]"
        example: 18000-B142
        required: true
    get:
      description: Get a semester on a faculty.
      responses:
        200:
          body:
            application/json:
              example: |
                {
                  "semesters": {
                    "id": "18000-B142",
                    "semester": "B142",
                    "faculty": 18000,
                    "starts_at": "2015-02-16",
                    "ends_at": "2015-09-21",
                    "exams_start_at": "2015-05-18",
                    "exams_end_at": "2015-06-27",
                    "teaching_ends_at": "2015-05-16",
                    "first_week_parity": "even",
                    "hour_duration": 45,
                    "hour_starts": [
                      "07:30", "08:15", "09:15", "10:00", "11:00", "11:45",
                      "12:45", "13:30", "14:30", "15:15", "16:15", "17:00",
                      "18:00", "18:45", "19:45"
                    ]
                  }
                }


remove old raml (#122)

remove old raml (#122)

#%RAML 0.8
---
title: Bandwidth Dashboard REST API Documentation
# Use null host here to trigger automatic replacement in javascript
baseUri: https://dashboard.bandwidth.com/api/
version: v1

securedBy: [basic]

securitySchemes:
   - basic:
        type: Basic Authentication

/accounts:
    description: |
        The account is the root resource for many of the operations in the Bandwidth Dashboard API.

        The account is represented by an account id, which is the resource that represents a Bandwidth customer, providing a root resource for all of the customer's attributes and services

        The API calls that are used to manage the details of a customer account, and to manage the resources that a Bandwidth customer has access to or control over, are accessed through the /accounts resource.

    /{accountId}:
        description: This API retrieves and updates an account's information as specified by the given account ID. Access to information pertaining to a specific account will require credentials that have been assigned to that account, preserving the security of a customer’s information.
Note that DELETE is currently unsupported.

        /applications:
            description: |
                The application is internal Catapult resource that will provide Iris with possibility to send and recieve sms to/from outside world.

                The application is represented by an application id.

                The API calls that are used to manage the details of a application and to manage the application that a Bandwidth customer has access to or control over, are accessed through the /accounts/{accountId}/channles/applications resource.

            post:
                description: Create an Application
                body:
                    application/xml:
                        example:
                            <?xml version="1.0"?>
                            <ApplicationProvisioningResponse>
                                <Application>
                                    <AppName>applicationName</AppName>
                                    <CallbackUrl>https://example.com</CallbackUrl>
                                    <CallbackCreds>
                                        <UserId>UserName</UserId>
                                        <Password>Password</Password>
                                    </CallbackCreds>
                                </Application>
                            </ApplicationProvisioningResponse>
                responses:
                    201:
                        body:
                            application/xml:
                                example:
                                    <?xml version="1.0"?>
                                    <ApplicationProvisioningResponse>
                                        <Application>
                                            <AppName>applicationName</AppName>
                                            <AppId>a-pvcirtaqlsgimgirgj37ayi</AppId>
                                            <CallbackUrl>https://example.com</CallbackUrl>
                                            <CallbackCreds>
                                                <UserId>UserName</UserId>
                                                <Password>Password</Password>
                                            </CallbackCreds>
                                        </Application>
                                    </ApplicationProvisioningResponse>
            /{applicationId}:
              get:
                description: Retrieve an Application
                responses:
                    200:
                        body:
                            application/xml:
                                example:
                                    <?xml version="1.0"?>
                                    <ApplicationProvisioningResponse>
                                        <Application>
                                            <AppName>applicationName</AppName>
                                            <AppId>a-pvcirtaqlsgimgirgj37ayi</AppId>
                                            <CallbackUrl>https://example.com</CallbackUrl>
                                            <CallbackCreds>
                                                <UserId>UserName</UserId>
                                                <Password>Password</Password>
                                            </CallbackCreds>
                                        </Application>
                                    </ApplicationProvisioningResponse>

              put:
                description: Update an Application
                body:
                     application/xml:
                         example:
                            <?xml version="1.0"?>
                            <ApplicationProvisioningResponse>
                                <Application>
                                    <AppName>applicationName</AppName>
                                    <CallbackUrl>https://example.com</CallbackUrl>
                                    <CallbackCreds>
                                        <UserId>AnotherName</UserId>
                                        <Password>Password</Password>
                                    </CallbackCreds>
                                </Application>
                            </ApplicationProvisioningResponse>
                responses:
                    200:
                        body:
                            application/xml:
                                example:
                                    <?xml version="1.0"?>
                                    <ApplicationProvisioningResponse>
                                        <Application>
                                            <AppName>applicationName</AppName>
                                            <AppId>a-pvcirtaqlsgimgirgj37ayi</AppId>
                                            <CallbackUrl>https://example.com</CallbackUrl>
                                            <CallbackCreds>
                                                <UserId>AnotherName</UserId>
                                                <Password>Password</Password>
                                            </CallbackCreds>
                                        </Application>
                                    </ApplicationProvisioningResponse>

              patch:
                description: Patch update an Application
                body:
                     application/xml:
                         example:
                            <?xml version="1.0"?>
                            <ApplicationProvisioningResponse>
                                <Application>
                                    <CallbackUrl>https://newUrl.com</CallbackUrl>
                                </Application>
                            </ApplicationProvisioningResponse>
                responses:
                    200:
                        body:
                            application/xml:
                                example:
                                    <?xml version="1.0"?>
                                    <ApplicationProvisioningResponse>
                                        <Application>
                                            <AppName>applicationName</AppName>
                                            <AppId>a-pvcirtaqlsgimgirgj37ayi</AppId>
                                            <CallbackUrl>https://newUrl.com</CallbackUrl>
                                            <CallbackCreds>
                                                <UserId>UserName</UserId>
                                                <Password>Password</Password>
                                            </CallbackCreds>
                                        </Application>
                                    </ApplicationProvisioningResponse>
              delete:
                  description: Delete an Application
                  responses:
                      200:
                          body:
                              application/xml:
                                  example: None

            /{applicationId}/associatedsippeers:
              get:
                description: Retrieve a list of sippeers, associated with application
                responses:
                    200:
                        body:
                            application/xml:
                                example:
                                    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                    <AssociatedSipPeersResponse>
                                        <AssociatedSipPeers>
                                            <AssociatedSipPeer>
                                                <siteId>482</siteId>
                                                <siteName>site_e867f</siteName>
                                                <peerId>500018</peerId>
                                                <peerName>sippeer-e867f</peerName>
                                            </AssociatedSipPeer>
                                            <AssociatedSipPeer>
                                                <siteId>483</siteId>
                                                <siteName>site_e867d</siteName>
                                                <peerId>500019</peerId>
                                                <peerName>sippeer-e867d</peerName>
                                            </AssociatedSipPeer>
                                        </AssociatedSipPeers>
                                    </AssociatedSipPeersResponse>
                    400:
                        body:
                            application/xml:
                                example:
                                    <AssociatedSipPeersResponse>
                                        <ResponseStatus>
                                            <ErrorCode>12103</ErrorCode>
                                            <Description>
                                                Current 1 Account have no Catapult association
                                            </Description>
                                        </ResponseStatus>
                                    </AssociatedSipPeersResponse>
                    404:
                        body:
                            application/xml:
                                example:
                                    <AssociatedSipPeersResponse>
                                        <ResponseStatus>
                                            <ErrorCode>13629</ErrorCode>
                                                <Description>
                                                    Application with id 'non_existing' not found
                                                </Description>
                                        </ResponseStatus>
                                    </AssociatedSipPeersResponse>

        /sites:

            description: |
                Use this method to add or update a site to an existing account.

                Each site creation or update must have the following input parameters:

                        Parameter	Description

                        accountid	The numerical Account ID that you will be adding the site to.

                        Name	The name of the site. Max length restricted to 10 characters.

                        Description	Customer provided description of the site.

                        Address	Service Address for the site.

                        CustomerProvidedID	Customer can provide an optional id (max 10 digits). Note that the customer can use the same id across multiple orders.

                        CustomerName	Customer can provide an optional name

                        UcTrunkingConfiguration	For UC Trunking accounts the UcTrunkingConfiguration element describes the kind of UC trunking that is provided.  The Type parameter is one of Seats, Premise, or Cloud, and the UsageCategory parameter is one of UC250, UC500 or UC1000.

            get:
                description: retrieve a list of all the sites associated with the account
                responses:
                    200:
                        body:
                            application/xml:
                                example: |
                                    <?xml version="1.0"?>
                                    <SitesResponse>
                                        <Sites>
                                            <Site>
                                                <Id>399</Id>
                                                <Name>Testsite</Name>
                                                <Description>NewSite</Description>
                                            </Site>
                                            <Site>
                                                <Id>403</Id>
                                                <Name>GABESITEa</Name>
                                                <Description>Awesomeness</Description>
                                            </Site>
                                        </Sites>
                                    </SitesResponse>
            post:
                description: Add a site to the account
                body:
                    application/xml:
                        example: |
                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                            <Site>
                                <Name>Raleigh</Name>
                                <Description>Test Gateway</Description>
                                <CustomerName>BW</CustomerName>
                                <Address>
                                    <HouseNumber>6300</HouseNumber>
                                    <StreetName>Lee Hall</StreetName>
                                    <City>Raleigh</City>
                                    <StateCode>NC</StateCode>
                                    <Zip>27606</Zip>
                                    <AddressType>Service</AddressType>
                                </Address>
                            </Site>

                            <Site>
                                <Name>Raleigh</Name>
                                <Description>Test Gateway</Description>
                                <CustomerName>BW</CustomerName>
                                <Address>
                                    <HouseNumber>6300</HouseNumber>
                                    <StreetName>Lee Hall</StreetName>
                                    <City>Raleigh</City>
                                    <StateCode>NC</StateCode>
                                    <Zip>27606</Zip>
                                    <AddressType>Service</AddressType>
                                </Address>
                                <UcTrunkingConfiguration>
                                    <Type>Seats</Type>
                                    <UsageCategory>UC500</UsageCategory>
                                </UcTrunkingConfiguration>
                            </Site>
                responses:
                    201:
                        description: The site has been successfully added to the account
                    400:
                        description: Information is missing from the body of the add site request
                        body:
                            application/xml:
                                example: |
                                    <SiteResponse>
                                        <ResponseStatus>
                                            <ErrorCode>1003</ErrorCode>
                                            <Description>Address is required</Description>
                                        </ResponseStatus>
                                    </SiteResponse>

                /{siteId}:
                    description: This method updates or deletes a site based on the id, as well as adds a SIP Peer to the given site.

                    /sippeers:
                        description: |
                            The SIP Peer API is used to display and configure SIP Peers

                            The values for this payload are as follows:

                                    Element
                                    Description
                                    Example

                                    SiteId
                                    The internally allocated SIP Peer ID
                                    12345

                                    PeerName
                                    Mandatory name for the SIP Peer (Max 10 chars)
                                    Downtown Branch

                                    Description
                                    Optional description for the SIP Peer

                                    IsDefaultPeer
                                    Value is True or False. The Default SIP Peer is the default "destination" for any Telephone Numbers that are ordered for the Site in which the SIP Peer resides.  Each site can have only 1 default SIP Peer. You can configure multiple SIP Peers on a Site

                                    ShortMessagingProtocol
                                    Used to specify the protocol used by the endpoints for exchanging SMS messages: allowed values are SIP and SMPP.  The element is optional, with a default of SMPP.  This element can be updated if SMS is enabled on the Account and SIP Peer.

                                    HostName
                                    The IP Address or Host Name of the address to be used for the SmsHosts, VoiceHosts or VoiceHostGroups addresses.

                                    Port
                                    Optional Port Number for Voice and Termination hosts. This is an optional parameter that has default values that are dependent on the Application.  It is not valid for SMS.

                                    VoiceHosts
                                    These addresses, comprised of HostName and optional Port, are used by the Bandwidth network to send calls to for Origination services. The VoiceHosts list of IP addresses used for an active/standby address selection mechanism, where the first address is attempted, followed by the second address and so on.  Except under failure situations the first address in the list is preferred. Maximum of 10 hosts - can be IP address or Fully Qualified Domain Name

                                    VoiceHostGroups
                                    The VoiceHostGroups element is comprised of a list of up to five VoiceHostGroup elements, each of which is used to randomly distribute traffic amongst up to 10 IP addresses.  One of the VoiceHostGroups elements in the group is chosen at random to receive traffic, and then the calls are placed at random amongst the addresses in the group.  Once a group is chose, failover behavior is retained within the group.

                                    VoiceHostGroup
                                    A VoiceHostGroup is a list of IP Addresses (the Host element).  This traffic distribution model distributes traffic in a Random manner amongst the addresses in the group.

                                    SmsHosts
                                    Used for SMS traffic only – can be IP address of Fully Qualified Domain Name

                                    TerminationHosts
                                    These addresses, comprised of IP or Subnet(CIDR format) and optional Port, are used by the Bandwidth network to send calls to for Termination services. Maximum of 10 hosts - can be IP address or subnets. In case of subnet you should specify NetworkAddress of subnet as IP.
                                    135.23.78.145 or

                                    12.45.67.48/29

                                    CustomerTrafficAllowed
                                    A TerminationHost can be configured to allow different customer traffic types.  Allowed values are LITE, DOMESTIC and ALL. This is an optional parameter.

                                    DataAllowed
                                    True or False (Enables or Disables SMS messaging for a TerminationHost). Optional parameter.

                                    Address
                                    Billing or Service Address for the SIP Peer.
                                        This element is optional for accounts except for accounts with the UC
                                        Trunking Product.  If the address element is provided the
                                        following fields can be provided, some of which are Mandatory:

                                            HouseNumber - MANDATORY

                                            HouseSuffix - OPTIONAL

                                            PreDirectional - OPTIONAL

                                            StreetName - MANDATORY

                                            StreetSuffix - OPTIONAL

                                            PostDirectional- OPTIONAL

                                            AddressLine2- OPTIONAL

                                            City - MANDATORY

                                            StateCode - MANDATORY

                                            Zip - MANDATORY

                                            PlusFour - OPTIONAL

                                            County - OPTIONAL

                                            Country - OPTIONAL (Defaults to 'US')

                                            AddressType - MANDATORY (Billing or
                                        Service)

                                  CallingName
                                  Determines whether the Calling Name Displayl service is applied to the Telephone Numbers associates with the SIP Peer

                                  Display
                                  Controls the Display of Calling Name information. If <true> then the calling name information is displayed by default for all calls,

                                  Enforced
                                  Determines whether the Default Display behavior (Display) is enforced for all TNs associated with the SIP Peer.  If <true> then no TN-level overrde is possible

                                  FinalDestinationURI
                                  Last attempt for routing of calls

                        post:
                            description: Create a Sip Peer
                            body:
                                application/xml:
                                    example: |
                                        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                        <SipPeer>
                                            <PeerName>name</PeerName>
                                            <Description>description</Description>
                                            <IsDefaultPeer>false</IsDefaultPeer>
                                            <FinalDestinationUri>uri</FinalDestinationUri>
                                            <ShortMessagingProtocol>SMPP</ShortMessagingProtocol>
                                            <VoiceHosts>
                                                <Host>
                                                    <HostName>10.10.10.1</HostName>
                                                </Host>
                                                <Host>
                                                    <HostName>10.10.10.2</HostName>
                                                </Host>
                                            </VoiceHosts>
                                            <SmsHosts>
                                                <Host>
                                                    <HostName>2.1.1.9</HostName>
                                                </Host>
                                            </SmsHosts>
                                            <TerminationHosts>
                                                <TerminationHost>
                                                    <HostName>2.1.1.9</HostName>
                                                    <Port>0</Port>
                                                    <CustomerTrafficAllowed>DOMESTIC</CustomerTrafficAllowed>
                                                    <DataAllowed>true</DataAllowed>
                                                </TerminationHost>
                                                <TerminationHost>
                                                    <HostName>2.1.1.96/30</HostName>
                                                    <Port>0</Port>
                                                    <CustomerTrafficAllowed>DOMESTIC</CustomerTrafficAllowed>
                                                    <DataAllowed>true</DataAllowed>
                                                </TerminationHost>
                                            </TerminationHosts>
                                              <Address>
                                                  <HouseNumber>1600</HouseNumber>
                                                  <HouseSuffix/>
                                                  <PreDirectional/>
                                                  <StreetName>Pennsylvania Avenue Northwest</StreetName>
                                                  <StreetSuffix/>
                                                  <PostDirectional/>
                                                  <AddressLine2/>
                                                  <City>Washington</City>
                                                  <StateCode>DC</StateCode>
                                                  <Zip>20500</Zip>
                                                  <PlusFour/>
                                                  <County/>
                                                  <Country>United States</Country>
                                                  <AddressType>Service</AddressType>
                                              </Address>
                                            <PremiseTrunks>PremiseTrunks</PremiseTrunks>
                                            <CallingName>
                                                <Display>true</Display>
                                                <Enforced>true</Enforced>
                                            </CallingName>
                                        </SipPeer>

                                        or alternatively, using VoiceHostGroups instead of VoiceHosts
                                        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                        <SipPeer>
                                            <PeerName>name</PeerName>
                                            <Description>description</Description>
                                            <IsDefaultPeer>false</IsDefaultPeer>
                                            <FinalDestinationUri>uri</FinalDestinationUri>
                                            <ShortMessagingProtocol>SMPP</ShortMessagingProtocol>
                                            <VoiceHostGroups>
                                                <VoiceHostGroup>
                                                   <Host>
                                                       <HostName>10.10.10.1</HostName>
                                                   </Host>
                                                   <Host>
                                                       <HostName>10.10.10.2</HostName>
                                                   </Host>
                                                </VoiceHostGroup>
                                            </VoiceHostGroups>
                                            <SmsHosts>
                                                <Host>
                                                    <HostName>2.1.1.9</HostName>
                                                </Host>
                                            </SmsHosts>
                                            <TerminationHosts>
                                                <TerminationHost>
                                                    <HostName>2.1.1.9</HostName>
                                                    <Port>0</Port>
                                                    <CustomerTrafficAllowed>DOMESTIC</CustomerTrafficAllowed>
                                                    <DataAllowed>true</DataAllowed>
                                                </TerminationHost>
                                                <TerminationHost>
                                                    <HostName>2.1.1.96/30</HostName>
                                                    <Port>0</Port>
                                                    <CustomerTrafficAllowed>DOMESTIC</CustomerTrafficAllowed>
                                                    <DataAllowed>true</DataAllowed>
                                                </TerminationHost>
                                            </TerminationHosts>
                                        </SipPeer>
                            responses:
                                201:
                                    description: Sip Peer created
                                    body:
                                        application/xml:
                                            example: None
                                400:
                                    description: |
                                        Bad Request. Possible errors in response:
                                           Possible errors in response:

13569 "A termination host with HostName = 2.1.1.9 is already in use"

13562 "Must have either no hosts or SmsHosts and TerminationHosts"

13509 "'wrong.ip' is not a valid host. Provide valid IP or domain name"

13553 "Duplicate host (and port) in VoiceHosts"

13510 "'wrong.url' is not a valid Destination URI"

13522 "IsDefaultPeer cannot be false right now. The account requires at least one Default Sip Peer"

13552 "A termination host with HostName = %s and Port = %s is already in use"

12024 "Region with state '%s' and country '%s' does not exist"

13576 "Account 9999999 has no CNAM product feature"

13581 "Display option is missing"

13582 "Enforce option is missing"

13590 "The supplied CustomerTrafficAllowed and DataAllowed values on host %s:%s are not allowed for this sippeer"

13591 "Termination Settings at the SIP Peer level are not allowed for accounts with the 'DedicatedPrivateNetworkTopology' product."

13592 "Calling name 'Display' and 'Enforced' values can't be updated for 'DedicatedPrivateNetworkTopology' account.

13593 "%s has invalid mask. Valid mask values: 20-32"

13594 "%s is not valid host"

13595 "The IP address provided: %s contains a non zero subnet portion. An equivalent IP address such as %s with a zero subnet value must be provided."

                                    body:
                                        application/xml:
                                            example: |
                                                <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                <SipPeerResponse>
                                                    <ResponseStatus>
                                                        <ErrorCode>13582</ErrorCode>
                                                        <Description>Enforce option is missing</Description>
                                                    </ResponseStatus>
                                                </SipPeerResponse>
                                409:
                                    description: Conflict - Sip Peer with such name already exists
                                    body:
                                        application/xml:
                                            example: |
                                                <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                <SipPeerResponse>
                                                    <ResponseStatus>
                                                        <ErrorCode>13524</ErrorCode>
                                                        <Description>SipPeer name 'testDocSipPeers1' already exists for Account '9999999' and Site '45'</Description>
                                                    </ResponseStatus>
                                                </SipPeerResponse>
                                503:
                                    description: Service unavailable
                                    body:
                                        application/xml:
                                            example: |
                                                <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                <SipPeerResponse>
                                                    <ResponseStatus>
                                                        <ErrorCode>13566</ErrorCode>
                                                        <Description>Our E911 service is unavaliable</Description>
                                                    </ResponseStatus>
                                                </SipPeerResponse>

                        /{sippeerId}:
                            description:  |
                                The SIPpeerID Resource deals with retrieving or updating a specific identified SIP Peer, identified by the SIP Peer ID.
                                The elements of the payload are described in the /sippeers resource.

                            /products:
                                description:  |
                                    This API will expose products that are associated directly with the SIP Peer.
                                    At this time all of these products are limited to Admin access, and not exposed to the normal user base

                                    The current products that can be associated with a SIP Peer are:

                                    * Termination

                                    * EdgeManagement

                                    * Messaging

                                    * Origination

                                get:
                                    description: list the products associated with a SIP Peer
                                    responses:
                                        200:
                                            description: There is at least one product associated with the SIP Peer. If there is no products associated with Sip Peer, empty list will be displayed.
                                            body:
                                                application/xml:
                                                    example: |
                                                        <SipPeerProductResponse>
                                                            <Products>
                                                                <Product>
                                                                    <Name>Termination</Name>
                                                                </Product>
                                                                <Product>
                                                                    <Name>EdgeManagement</Name>
                                                                </Product>
                                                            </Products>
                                                        </SipPeerProductResponse>

                                /messaging/features/sms:
                                    get:
                                        description: |
                                            Retrieve sms feature settings for sippeer
                                        responses:
                                            200:
                                                description: A successful result that contains the response data
                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <SipPeerSmsFeatureResponse>
                                                                <SipPeerSmsFeature>
                                                                    <SipPeerSmsFeatureSettings>
                                                                        <TollFree>true</TollFree>
                                                                        <ShortCode>true</ShortCode>
                                                                        <Protocol>SMPP</Protocol>
                                                                        <Zone1>true</Zone1>
                                                                        <Zone2>true</Zone2>
                                                                        <Zone3>true</Zone3>
                                                                        <Zone4>true</Zone4>
                                                                        <Zone5>true</Zone5>
                                                                    </SipPeerSmsFeatureSettings>
                                                                    <SmppHosts>
                                                                        <SmppHost>
                                                                            <HostName>54.10.88.146</HostName>
                                                                            <HostId>18</HostId>
                                                                            <Priority>0</Priority>
                                                                            <ConnectionType>RECEIVER_ONLY</ConnectionType>
                                                                        </SmppHost>
                                                                    </SmppHosts>
                                                                </SipPeerSmsFeature>
                                                            </SipPeerSmsFeatureResponse>
                                    post:
                                        description: |

                                            Set sms feature settings

                                        body:
                                            application/xml:
                                                example: |
                                                    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                                                    <SipPeerSmsFeature>
                                                        <SipPeerSmsFeatureSettings>
                                                            <TollFree>true</TollFree>
                                                            <ShortCode>true</ShortCode>
                                                            <Protocol>SMPP</Protocol>
                                                            <Zone1>true</Zone1>
                                                            <Zone2>true</Zone2>
                                                            <Zone3>true</Zone3>
                                                            <Zone4>true</Zone4>
                                                            <Zone5>true</Zone5>
                                                        </SipPeerSmsFeatureSettings>
                                                        <SmppHosts>
                                                            <SmppHost>
                                                                <HostName>54.10.88.146</HostName>
                                                                <Priority>0</Priority>
                                                                <ConnectionType>RECEIVER_ONLY</ConnectionType>
                                                            </SmppHost>
                                                        </SmppHosts>
                                                    </SipPeerSmsFeature>
                                        responses:
                                            201:
                                                description: setting were successfully added
                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <SipPeerSmsFeatureResponse>
                                                                <SipPeerSmsFeature>
                                                                    <SipPeerSmsFeatureSettings>
                                                                        <TollFree>true</TollFree>
                                                                        <ShortCode>true</ShortCode>
                                                                        <Protocol>SMPP</Protocol>
                                                                        <Zone1>true</Zone1>
                                                                        <Zone2>true</Zone2>
                                                                        <Zone3>true</Zone3>
                                                                        <Zone4>true</Zone4>
                                                                        <Zone5>true</Zone5>
                                                                    </SipPeerSmsFeatureSettings>
                                                                    <SmppHosts>
                                                                        <SmppHost>
                                                                            <HostName>54.10.88.146</HostName>
                                                                            <HostId>18</HostId>
                                                                            <Priority>0</Priority>
                                                                            <ConnectionType>RECEIVER_ONLY</ConnectionType>
                                                                        </SmppHost>
                                                                    </SmppHosts>
                                                                </SipPeerSmsFeature>
                                                            </SipPeerSmsFeatureResponse>
                                            400:
                                                description: |
                                                    Bad Request. Possible errors in response:

Account level settings don`t exist

                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <SipPeerSmsFeatureResponse>
                                                                <ResponseStatus>
                                                                    <ErrorCode>13609</ErrorCode>
                                                                    <Description>Can't create sip peer http protocol sms feature without account level http settings.</Description>
                                                                </ResponseStatus>
                                                            </SipPeerSmsFeatureResponse>
                                    put:
                                        description: update sms feature settings
                                        body:
                                            application/json:
                                                example: |
                                                    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                                                    <SipPeerSmsFeature>
                                                        <SipPeerSmsFeatureSettings>
                                                            <TollFree>false</TollFree>
                                                            <ShortCode>true</ShortCode>
                                                            <Protocol>SMPP</Protocol>
                                                            <Zone1>true</Zone1>
                                                            <Zone2>false</Zone2>
                                                            <Zone3>false</Zone3>
                                                            <Zone4>false</Zone4>
                                                            <Zone5>false</Zone5>
                                                        </SipPeerSmsFeatureSettings>
                                                        <SmppHosts>
                                                            <SmppHost>
                                                                <HostName>235.133.23.79</HostName>
                                                                <HostId>6</HostId>
                                                                <Priority>0</Priority>
                                                                <ConnectionType>TRANSCEIVER</ConnectionType>
                                                            </SmppHost>
                                                        </SmppHosts>
                                                    </SipPeerSmsFeature>

                                        responses:
                                            200:
                                                description: settings were successfully updated
                                    delete:
                                        description: delete sms settings
                                        responses:
                                            200:
                                                description: settings were deleted
                                            404:
                                                description: sms settings were not found

                                /messaging/features/mms:
                                    get:
                                        description: |
                                            Retrieve mms feature settings for sippeer
                                        responses:
                                            200:
                                                description: A successful result that contains the response data
                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <MmsFeatureResponse>
                                                              <MmsFeature>
                                                                <MmsSettings>
                                                                  <protocol>HTTP</protocol>
                                                                </MmsSettings>
                                                                <Protocols>
                                                                  <HTTP>
                                                                    <HttpSettings>
                                                                      <proxyPeerId>500017</proxyPeerId>
                                                                    </HttpSettings>
                                                                  </HTTP>
                                                                </Protocols>
                                                              </MmsFeature>
                                                            </MmsFeatureResponse>
                                    post:
                                        description: |

                                            Set mms feature settings

                                        body:
                                            application/xml:
                                                example: |
                                                    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                                                    <MmsFeature>
                                                      <MmsSettings>
                                                        <protocol>MM4</protocol>
                                                      </MmsSettings>
                                                      <Protocols>
                                                        <MM4>
                                                          <MmsMM4TermHosts>
                                                            <TermHosts>
                                                              <TermHost>
                                                                <HostName>206.107.248.58</HostName>
                                                              </TermHost>
                                                            </TermHosts>
                                                          </MmsMM4TermHosts>
                                                          <MmsMM4OrigHosts>
                                                            <OrigHosts>
                                                              <OrigHost>
                                                                <HostName>30.239.72.55</HostName>
                                                                <Port>8726</Port>
                                                                <Priority>0</Priority>
                                                              </OrigHost>
                                                            </OrigHosts>
                                                          </MmsMM4OrigHosts>
                                                        </MM4>
                                                      </Protocols>
                                                    </MmsFeature>
                                        responses:
                                            201:
                                                description: setting was successfully added
                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <MmsFeatureResponse>
                                                              <MmsFeature>
                                                                <MmsSettings>
                                                                  <protocol>MM4</protocol>
                                                                </MmsSettings>
                                                                <Protocols>
                                                                  <MM4>
                                                                    <MmsMM4TermHosts>
                                                                      <TermHosts>
                                                                        <TermHost>
                                                                          <HostId>1</HostId>
                                                                          <HostName>206.107.248.58</HostName>
                                                                        </TermHost>
                                                                      </TermHosts>
                                                                    </MmsMM4TermHosts>
                                                                    <MmsMM4OrigHosts>
                                                                      <OrigHosts>
                                                                        <OrigHost>
                                                                          <HostName>30.239.72.55</HostName>
                                                                          <Port>8726</Port>
                                                                          <HostId>1</HostId>
                                                                          <Priority>0</Priority>
                                                                        </OrigHost>
                                                                      </OrigHosts>
                                                                    </MmsMM4OrigHosts>
                                                                  </MM4>
                                                                </Protocols>
                                                              </MmsFeature>
                                                            </MmsFeatureResponse>
                                            400:
                                                description: |
                                                    Bad Request. Possible errors in response:

Pauload contains two protocol

                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <MmsFeatureResponse>
                                                              <ResponseStatus>
                                                                <ErrorCode>13606</ErrorCode>
                                                                <Description>Messaging feature may have only one protocol assigned.</Description>
                                                              </ResponseStatus>
                                                            </MmsFeatureResponse>
                                    put:
                                        description: update mms feature settings
                                        body:
                                            application/json:
                                                example: |
                                                    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                                                    <MmsFeature>
                                                      <MmsSettings>
                                                        <protocol>HTTP</protocol>
                                                      </MmsSettings>
                                                      <Protocols>
                                                        <HTTP>
                                                          <HttpSettings>
                                                            <proxyPeerId>500017</proxyPeerId>
                                                          </HttpSettings>
                                                        </HTTP>
                                                      </Protocols>
                                                    </MmsFeature>
                                        responses:
                                            200:
                                                description: settings were successfully updated
                                    delete:
                                        description: delete mms settings
                                        responses:
                                            200:
                                                description: settings were deleted
                                            404:
                                                description: mms settings were not found
                                    /settings:
                                      get:
                                          description: |
                                              Retrieve mms feature settings for sippeer
                                          responses:
                                              200:
                                                  description: A successful result that contains the response data
                                                  body:
                                                      application/xml:
                                                          example: |
                                                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                              <MmsFeatureMmsSettingsResponse>
                                                                <MmsSettings>
                                                                  <protocol>MM4</protocol>
                                                                </MmsSettings>
                                                              </MmsFeatureMmsSettingsResponse>
                                /messaging/applicationSettings:
                                    get:
                                        description: |
                                            Retrieve sipper application settings
                                        responses:
                                            200:
                                                description: A successful result that contains the response data
                                                body:
                                                    application/xml:
                                                        example: |
                                                            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                            <ApplicationsSettingsResponse>
                                                              <ApplicationsSettings>
                                                                <HttpMessagingV2AppId>4a4ca6c1-156b-4fca-84e9-34e35e2afc32</HttpMessagingV2AppId>
                                                              </ApplicationsSettings>
                                                            </ApplicationsSettingsResponse>
                                    put:
                                        description: create/update/delete application settings for sippeer (use value 'REMOVE' to unassing application)
                                        body:
                                            application/json:
                                                example: |
                                                    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
                                                    <ApplicationsSettings>
                                                      <HttpMessagingV2AppId>c3b0f805-06ab-4d36-8bf4-8baff7623398</HttpMessagingV2AppId>
                                                    </ApplicationsSettings>
                                        responses:
                                            200:
                                                description: settings were successfully created/updated
                                                body:
                                                  application/xml:
                                                      example: |
                                                          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                                                          <ApplicationsSettingsResponse>
                                                            <ApplicationsSettings>
                                                              <HttpMessagingV2AppId>c3b0f805-06ab-4d36-8bf4-8baff7623398</HttpMessagingV2AppId>
                                                            </ApplicationsSettings>
                                                          </ApplicationsSettingsResponse>