MTN Group Incident ticket API

The Incident ticket API from MTN Group — 1 operation(s) for incident ticket.

Operations 2

POST /incident Create a new ticket
PUT /incident Modify an existing ticket

Documentation

📖
Documentation
https://developers.mtn.com/products/account-decisioning
📖
APIReference
https://developers.mtn.com/products/account-decisioning
📖
Documentation
https://developers.mtn.com/products/tmf-customer-bill-management
📖
APIReference
https://developers.mtn.com/products/tmf-customer-bill-management
📖
Documentation
https://developers.mtn.com/products/mtn-customer-loans-api-v1
📖
APIReference
https://developers.mtn.com/products/mtn-customer-loans-api-v1
📖
Documentation
https://developers.mtn.com/products/subscriber-details
📖
APIReference
https://developers.mtn.com/products/subscriber-details
📖
Documentation
https://developers.mtn.com/products/subscriber-type
📖
APIReference
https://developers.mtn.com/products/subscriber-type
📖
Documentation
https://developers.mtn.com/products/provisioning
📖
APIReference
https://developers.mtn.com/products/provisioning
📖
Documentation
https://developers.mtn.com/products/unified-balance-v1
📖
APIReference
https://developers.mtn.com/products/unified-balance-v1
📖
Documentation
https://developers.mtn.com/products/tmf-resourceinventorymanagement-tmf639
📖
APIReference
https://developers.mtn.com/products/tmf-resourceinventorymanagement-tmf639
📖
Documentation
https://developers.mtn.com/products/sales-management
📖
APIReference
https://developers.mtn.com/products/sales-management
📖
Documentation
https://developers.mtn.com/products/service-activation-and-configuration
📖
APIReference
https://developers.mtn.com/products/service-activation-and-configuration
📖
Documentation
https://developers.mtn.com/products/service-ordering
📖
APIReference
https://developers.mtn.com/products/service-ordering
📖
Documentation
https://developers.mtn.com/products/bss-tt-oauth-v1
📖
APIReference
https://developers.mtn.com/products/bss-tt-oauth-v1
📖
Documentation
https://developers.mtn.com/products/balance-management-v1
📖
APIReference
https://developers.mtn.com/products/balance-management-v1
📖
Documentation
https://developers.mtn.com/products/callmeback-v1
📖
APIReference
https://developers.mtn.com/products/callmeback-v1
📖
Documentation
https://developers.mtn.com/products/callmeback-v2
📖
APIReference
https://developers.mtn.com/products/callmeback-v2
📖
Documentation
https://developers.mtn.com/products/rcs-communication
📖
APIReference
https://developers.mtn.com/products/rcs-communication
📖
Documentation
https://developers.mtn.com/products/communication-management-v1
📖
APIReference
https://developers.mtn.com/products/communication-management-v1
📖
Documentation
https://developers.mtn.com/products/tmf681-communication-management
📖
APIReference
https://developers.mtn.com/products/tmf681-communication-management
📖
Documentation
https://developers.mtn.com/products/ayo-preapproval
📖
APIReference
https://developers.mtn.com/products/ayo-preapproval
📖
Documentation
https://developers.mtn.com/products/content-push
📖
APIReference
https://developers.mtn.com/products/content-push
📖
Documentation
https://developers.mtn.com/products/mtn-customer-bill-management
📖
APIReference
https://developers.mtn.com/products/mtn-customer-bill-management
📖
Documentation
https://developers.mtn.com/products/customer-billing-token-v1
📖
APIReference
https://developers.mtn.com/products/customer-billing-token-v1
📖
Documentation
https://developers.mtn.com/products/mtn-nigeria-data-gifting-v1
📖
APIReference
https://developers.mtn.com/products/mtn-nigeria-data-gifting-v1
📖
Documentation
https://developers.mtn.com/products/mtn-nigeria-customer-datashare
📖
APIReference
https://developers.mtn.com/products/mtn-nigeria-customer-datashare
📖
Documentation
https://developers.mtn.com/products/customer-delivery-booking
📖
APIReference
https://developers.mtn.com/products/customer-delivery-booking
📖
Documentation
https://developers.mtn.com/products/customer-identification-v1
📖
APIReference
https://developers.mtn.com/products/customer-identification-v1
📖
Documentation
https://developers.mtn.com/products/kyc-consent
📖
APIReference
https://developers.mtn.com/products/kyc-consent
📖
Documentation
https://developers.mtn.com/products/customer-loyalty-management
📖
APIReference
https://developers.mtn.com/products/customer-loyalty-management
📖
Documentation
https://developers.mtn.com/products/customer-management-coe-za-preprod
📖
APIReference
https://developers.mtn.com/products/customer-management-coe-za-preprod
📖
Documentation
https://developers.mtn.com/products/customer-pin-management-v2
📖
APIReference
https://developers.mtn.com/products/customer-pin-management-v2
📖
Documentation
https://developers.mtn.com/products/customer-promotion
📖
APIReference
https://developers.mtn.com/products/customer-promotion
📖
Documentation
https://developers.mtn.com/products/customer-survey
📖
APIReference
https://developers.mtn.com/products/customer-survey
📖
Documentation
https://developers.mtn.com/products/customer-data-transfer-ng-prod
📖
APIReference
https://developers.mtn.com/products/customer-data-transfer-ng-prod
📖
Documentation
https://developers.mtn.com/products/mtn-customer-datatransfer
📖
APIReference
https://developers.mtn.com/products/mtn-customer-datatransfer
📖
Documentation
https://developers.mtn.com/products/device-swap-v1
📖
APIReference
https://developers.mtn.com/products/device-swap-v1
📖
Documentation
https://developers.mtn.com/products/tmf-720-digital-identity-management
📖
APIReference
https://developers.mtn.com/products/tmf-720-digital-identity-management
📖
Documentation
https://developers.mtn.com/products/digital-partner-management
📖
APIReference
https://developers.mtn.com/products/digital-partner-management
📖
Documentation
https://developers.mtn.com/products/document-managment
📖
APIReference
https://developers.mtn.com/products/document-managment
📖
Documentation
https://developers.mtn.com/products/tmf-document-management-tmf667
📖
APIReference
https://developers.mtn.com/products/tmf-document-management-tmf667
📖
Documentation
https://developers.mtn.com/products/tmf688-event-management
📖
APIReference
https://developers.mtn.com/products/tmf688-event-management
📖
Documentation
https://developers.mtn.com/products/eec-token-management
📖
APIReference
https://developers.mtn.com/products/eec-token-management
📖
Documentation
https://developers.mtn.com/products/insurance
📖
APIReference
https://developers.mtn.com/products/insurance
📖
Documentation
https://developers.mtn.com/products/iot-device-management
📖
APIReference
https://developers.mtn.com/products/iot-device-management
📖
Documentation
https://developers.mtn.com/products/hcm-v1
📖
APIReference
https://developers.mtn.com/products/hcm-v1
📖
Documentation
https://developers.mtn.com/products/logback-v1
📖
APIReference
https://developers.mtn.com/products/logback-v1
📖
Documentation
https://developers.mtn.com/products/tmf-loyalty-management-tmf658
📖
APIReference
https://developers.mtn.com/products/tmf-loyalty-management-tmf658
📖
Documentation
https://developers.mtn.com/products/rcs-capability
📖
APIReference
https://developers.mtn.com/products/rcs-capability
📖
Documentation
https://developers.mtn.com/products/medallia-sms-v2
📖
APIReference
https://developers.mtn.com/products/medallia-sms-v2
📖
Documentation
https://developers.mtn.com/products/advertising-v2
📖
APIReference
https://developers.mtn.com/products/advertising-v2
📖
Documentation
https://developers.mtn.com/products/mtn-advertising-api-v1
📖
APIReference
https://developers.mtn.com/products/mtn-advertising-api-v1
📖
Documentation
https://developers.mtn.com/products/mobile-customer-information
📖
APIReference
https://developers.mtn.com/products/mobile-customer-information
📖
Documentation
https://developers.mtn.com/products/withdrawals-v1
📖
APIReference
https://developers.mtn.com/products/withdrawals-v1
📖
Documentation
https://developers.mtn.com/products/momo-verification
📖
APIReference
https://developers.mtn.com/products/momo-verification
📖
Documentation
https://developers.mtn.com/products/ayoaccountholderinfo
📖
APIReference
https://developers.mtn.com/products/ayoaccountholderinfo
📖
Documentation
https://developers.mtn.com/products/agent-profile
📖
APIReference
https://developers.mtn.com/products/agent-profile
📖
Documentation
https://developers.mtn.com/products/customer-account-management-v1
📖
APIReference
https://developers.mtn.com/products/customer-account-management-v1
📖
Documentation
https://developers.mtn.com/products/mtn-customer-kyc-api-v1-product
📖
APIReference
https://developers.mtn.com/products/mtn-customer-kyc-api-v1-product
📖
Documentation
https://developers.mtn.com/products/customer-kyc-verification
📖
APIReference
https://developers.mtn.com/products/customer-kyc-verification
📖
Documentation
https://developers.mtn.com/products/loans-v2
📖
APIReference
https://developers.mtn.com/products/loans-v2
📖
Documentation
https://developers.mtn.com/products/mtn-customer-locations-api-v1
📖
APIReference
https://developers.mtn.com/products/mtn-customer-locations-api-v1
📖
Documentation
https://developers.mtn.com/products/customer-management
📖
APIReference
https://developers.mtn.com/products/customer-management
📖
Documentation
https://developers.mtn.com/products/mtn-customer-plans-api-v2
📖
APIReference
https://developers.mtn.com/products/mtn-customer-plans-api-v2
📖
Documentation
https://developers.mtn.com/products/mtn-customer-profiles-api-v2-product
📖
APIReference
https://developers.mtn.com/products/mtn-customer-profiles-api-v2-product
📖
Documentation
https://developers.mtn.com/products/risk-management
📖
APIReference
https://developers.mtn.com/products/risk-management
📖
Documentation
https://developers.mtn.com/products/mtn-customer-score
📖
APIReference
https://developers.mtn.com/products/mtn-customer-score
📖
Documentation
https://developers.mtn.com/products/simverification
📖
APIReference
https://developers.mtn.com/products/simverification
📖
Documentation
https://developers.mtn.com/products/mtn-subscription-api-v2
📖
APIReference
https://developers.mtn.com/products/mtn-subscription-api-v2
📖
Documentation
https://developers.mtn.com/products/g2m
📖
APIReference
https://developers.mtn.com/products/g2m
📖
Documentation
https://developers.mtn.com/products/oauth-v1
📖
APIReference
https://developers.mtn.com/products/oauth-v1
📖
Documentation
https://developers.mtn.com/products/merchant-provisioning-v1
📖
APIReference
https://developers.mtn.com/products/merchant-provisioning-v1
📖
Documentation
https://developers.mtn.com/products/mtn-sms-api-v1
📖
APIReference
https://developers.mtn.com/products/mtn-sms-api-v1
📖
Documentation
https://developers.mtn.com/products/ussd
📖
APIReference
https://developers.mtn.com/products/ussd
📖
Documentation
https://developers.mtn.com/products/mtn-product-offering-api-v2
📖
APIReference
https://developers.mtn.com/products/mtn-product-offering-api-v2
📖
Documentation
https://developers.mtn.com/products/mtn-product-offering-api-v3
📖
APIReference
https://developers.mtn.com/products/mtn-product-offering-api-v3
📖
Documentation
https://developers.mtn.com/products/mtn-ng-retailer-productivity-tracking-v1
📖
APIReference
https://developers.mtn.com/products/mtn-ng-retailer-productivity-tracking-v1
📖
Documentation
https://developers.mtn.com/products/tmf633-shopping-cart-management
📖
APIReference
https://developers.mtn.com/products/tmf633-shopping-cart-management
📖
Documentation
https://developers.mtn.com/products/siebel
📖
APIReference
https://developers.mtn.com/products/siebel
📖
Documentation
https://developers.mtn.com/products/tmf-party-management
📖
APIReference
https://developers.mtn.com/products/tmf-party-management
📖
Documentation
https://developers.mtn.com/products/tmf-usage-management-tmf635
📖
APIReference
https://developers.mtn.com/products/tmf-usage-management-tmf635
📖
Documentation
https://developers.mtn.com/products/usage-management
📖
APIReference
https://developers.mtn.com/products/usage-management
📖
Documentation
https://developers.mtn.com/products/mtnid-getinfo
📖
APIReference
https://developers.mtn.com/products/mtnid-getinfo
📖
Documentation
https://developers.mtn.com/products/notification-production
📖
APIReference
https://developers.mtn.com/products/notification-production
📖
Documentation
https://developers.mtn.com/products/notification-v2
📖
APIReference
https://developers.mtn.com/products/notification-v2
📖
Documentation
https://developers.mtn.com/products/order-fulfillment
📖
APIReference
https://developers.mtn.com/products/order-fulfillment
📖
Documentation
https://developers.mtn.com/products/tmf-party-interaction-tmf683
📖
APIReference
https://developers.mtn.com/products/tmf-party-interaction-tmf683
📖
Documentation
https://developers.mtn.com/products/mtn-party-management
📖
APIReference
https://developers.mtn.com/products/mtn-party-management
📖
Documentation
https://developers.mtn.com/products/rwanda-party-management
📖
APIReference
https://developers.mtn.com/products/rwanda-party-management
📖
Documentation
https://developers.mtn.com/products/payment-methods-management-sa
📖
APIReference
https://developers.mtn.com/products/payment-methods-management-sa
📖
Documentation
https://developers.mtn.com/products/payments-v1
📖
APIReference
https://developers.mtn.com/products/payments-v1
📖
Documentation
https://developers.mtn.com/products/tmf-prepay-balance-management-tmf654
📖
APIReference
https://developers.mtn.com/products/tmf-prepay-balance-management-tmf654
📖
Documentation
https://developers.mtn.com/products/product-catalog-coe
📖
APIReference
https://developers.mtn.com/products/product-catalog-coe
📖
Documentation
https://developers.mtn.com/products/product-catalog-management-v1
📖
APIReference
https://developers.mtn.com/products/product-catalog-management-v1
📖
Documentation
https://developers.mtn.com/products/product-catalogue-management
📖
APIReference
https://developers.mtn.com/products/product-catalogue-management
📖
Documentation
https://developers.mtn.com/products/tmf-product-catalog-tmf620
📖
APIReference
https://developers.mtn.com/products/tmf-product-catalog-tmf620
📖
Documentation
https://developers.mtn.com/products/product-ordering-coe
📖
APIReference
https://developers.mtn.com/products/product-ordering-coe
📖
Documentation
https://developers.mtn.com/products/tmf-product-ordering-tmf622
📖
APIReference
https://developers.mtn.com/products/tmf-product-ordering-tmf622
📖
Documentation
https://developers.mtn.com/products/resource-config-v1
📖
APIReference
https://developers.mtn.com/products/resource-config-v1
📖
Documentation
https://developers.mtn.com/products/tmf-resource-ordering-tmf652
📖
APIReference
https://developers.mtn.com/products/tmf-resource-ordering-tmf652
📖
Documentation
https://developers.mtn.com/products/tmf-service-activation-tmf678
📖
APIReference
https://developers.mtn.com/products/tmf-service-activation-tmf678
📖
Documentation
https://developers.mtn.com/products/job-card-management
📖
APIReference
https://developers.mtn.com/products/job-card-management
📖
Documentation
https://developers.mtn.com/products/ticket
📖
APIReference
https://developers.mtn.com/products/ticket
📖
Documentation
https://developers.mtn.com/products/mtn-sms-interface
📖
APIReference
https://developers.mtn.com/products/mtn-sms-interface
📖
Documentation
https://developers.mtn.com/products/sms-v3-api
📖
APIReference
https://developers.mtn.com/products/sms-v3-api
📖
Documentation
https://developers.mtn.com/products/sim-management-staging
📖
APIReference
https://developers.mtn.com/products/sim-management-staging
📖
Documentation
https://developers.mtn.com/products/sim-swap-verification-v1
📖
APIReference
https://developers.mtn.com/products/sim-swap-verification-v1
📖
Documentation
https://developers.mtn.com/products/subscriber-management
📖
APIReference
https://developers.mtn.com/products/subscriber-management
📖
Documentation
https://developers.mtn.com/products/taxation-v1
📖
APIReference
https://developers.mtn.com/products/taxation-v1
📖
Documentation
https://developers.mtn.com/products/tmf-trouble-ticket-tmf621
📖
APIReference
https://developers.mtn.com/products/tmf-trouble-ticket-tmf621
📖
Documentation
https://developers.mtn.com/products/tmf629-customer-management
📖
APIReference
https://developers.mtn.com/products/tmf629-customer-management
📖
Documentation
https://developers.mtn.com/products/tmf637-product-inventory
📖
APIReference
https://developers.mtn.com/products/tmf637-product-inventory
📖
Documentation
https://developers.mtn.com/products/account-management-coe
📖
APIReference
https://developers.mtn.com/products/account-management-coe
📖
Documentation
https://developers.mtn.com/products/tmf-payment-management-tmf676
📖
APIReference
https://developers.mtn.com/products/tmf-payment-management-tmf676
📖
Documentation
https://developers.mtn.com/products/resource-pool-management
📖
APIReference
https://developers.mtn.com/products/resource-pool-management
📖
Documentation
https://developers.mtn.com/products/tmf-usage-consumption-tmf677
📖
APIReference
https://developers.mtn.com/products/tmf-usage-consumption-tmf677
📖
Documentation
https://developers.mtn.com/products/usage-consumption
📖
APIReference
https://developers.mtn.com/products/usage-consumption

Specifications

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/mtn-group-incident-ticket-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

mtn-group-incident-ticket-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Mtn Group Incident ticket API
  version: v1.0
  description: 'Operations tagged Incident ticket across 2 of this provider''s published API definitions: mtn-group-job-card-management.yml, mtn-group-ticket.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: http://localhost:8080
- url: https://api.mtn.com/
tags:
- name: Incident ticket
paths:
  /incident:
    post:
      tags:
      - Incident ticket
      summary: Create a new ticket
      description: Create a new ticket by specifying the 'originIncidentNumber'.
      responses:
        201:
          description: Incident created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ticketResponse'
        401:
          description: Not authenticated
        404:
          description: Not found
        407:
          description: Proxy system not authenticated
        500:
          description: Internal Server Error
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/newTicket'
        description: Request body
        required: true
    put:
      tags:
      - Incident ticket
      summary: Modify an existing ticket
      description: This call is used to update a ticket that already exists by using the 'targetIncidentNumber'.
      responses:
        200:
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ticketResponse'
        401:
          description: Not authenticated
        404:
          description: Not found
        407:
          description: Proxy system not authenticated
        500:
          description: Internal Server Error
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/updateTicket'
        description: Request body
        required: true
    servers:
    - url: http://localhost:8080
components:
  schemas:
    newTicket:
      type: object
      required:
      - targetSystem
      - originSystem
      - transactionId
      - callerId
      - originIncidentNumber
      - shortDescription
      properties:
        targetSystem:
          type: string
          description: System receiving the request
          example: REMEDYSA
          enum:
          - REMEDYSA
          - SERVICENOW
        originSystem:
          type: string
          description: System originating the request
          example: SERVICENOW
          enum:
          - REMEDYSA
          - SERVICENOW
        transactionId:
          type: string
          description: Transaction identifier used by client
          example: 123ABC
        callerId:
          type: string
          description: User from calling system
          example: a.gonzalez.bogaz@accenture.com
        originIncidentNumber:
          type: string
          description: Origin ticket identifier, this is the id of the ticket at the originating system
          example: INC0011558
        shortDescription:
          type: string
          description: Brief description about the ticket
          example: Superman is sick
        detailedDescription:
          type: string
          description: More detailed description of the ticket
          example: Superman is sick because he was exposed to Kryptonite
        impact:
          type: string
          description: Level of impact
          example: '1'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        urgency:
          type: string
          description: Level of urgency
          example: '3'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        interface:
          type: string
          description: interface applicable to requests for RemedySA
          example: interface
        signalName:
          type: string
          description: signalName applicable to requests for RemedySA
          example: signalName
        attachmentFilename:
          type: string
          description: Name of file being attached
          example: image1.png
        attachmentData:
          type: string
          format: base64
          description: Attachment data encoded in base64
          example: fdgrdvh22dhv2dhtdt3h35th4
    ticketResponse:
      type: object
      required:
      - targetIncidentNumber
      - statusCode
      - statusMessage
      - originTransactionId
      - targetTransactionId
      properties:
        targetIncidentNumber:
          type: string
          description: Target ticket identifier, this is the id of the ticket at the target system
        statusCode:
          type: string
          description: Status code from target system to indicate transaction status
        statusMessage:
          type: string
          description: Status response description
          example: processed
        originTransactionId:
          type: string
          description: Transaction identifier generated by system originating the request
          example: MTN123456
        targetTransactionId:
          type: string
          description: Transaction identifier generated by target
          example: 17af7d89db62885072fa83305b961972
    updateTicket:
      type: object
      required:
      - transactionId
      - originSystem
      - targetSystem
      - targetIncidentNumber
      properties:
        transactionId:
          type: string
          description: Transaction identifier used by client
          example: 123ABC
        originSystem:
          type: string
          description: System originating the request
          example: SERVICENOW,REMEDYSA
        targetSystem:
          type: string
          description: System receiving the request
          example: REMEDYSA,SERVICENOW
        targetIncidentNumber:
          type: string
          description: Incident number at the target system
          example: INC0011964
        shortDescription:
          type: string
          description: Brief description about the ticket
          example: Superman is sick
        detailedDescription:
          type: string
          description: More detailed description of the ticket
          example: Superman is sick because he was exposed to Kryptonite
        impact:
          type: string
          description: Level of impact
          example: '1'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        urgency:
          type: string
          description: Level of urgency
          example: '3'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        attachmentFilename:
          type: string
          description: Name of file being attached
          example: image1.png
        attachmentData:
          type: string
          format: base64
          description: Attachment data encoded in base64
          example: fdgrdvh22dhv2dhtdt3h35th4
        state:
          type: string
          description: Only applicable for values 2,3,6,7,8. Value 1 is set when an incident is created. Value 2 can only be set if the ticket 'assignedTo' field was prevously set
          example: '3'
          enum:
          - '2'
          - '3'
          - '6'
          - '7'
          - '8'
        assignedTo:
          type: string
          description: Who the incident is assigned to
          example: integration.mtn.sa.remedy
        closeCode:
          type: string
          description: Applicable when setting 'state' to 6. This value is used to indicate the code for resolution.
          enum:
          - Not Resolved – Not Reproducible
          - Not Resolved – Problem Raised
          - Not Resolved – Resolved by Vendor
          - Resolved - Workaround Applied
          - Resolved – Fixed by Caller
          - Resolved – Fixed Without Action
          - Resolved – Permanent Fix Applied
          example: Resolved – Permanent Fix Applied
        closeNotes:
          type: string
          description: Custom notes for closing ticket.
          example: All done!
        comments:
          type: string
          description: Comments to incident
          example: My comments
        workNotes:
          type: string
          description: Work notes to incident
          example: My notes
        subcategory:
          type: string
          description: Incident category
          example: database
        interface:
          type: string
          description: interface applicable to requests for RemedySA
          example: interface
        signalName:
          type: string
          description: signalName applicable to requests for RemedySA
          example: signalName
        summary:
          type: string
          description: summary applicable to requests for RemedySA
          example: summary
        detailedSummary:
          type: string
          description: detailedSummary applicable to requests for RemedySA
          example: detailedSummary
    TicketCreateData:
      type: object
      properties:
        referenceNumber:
          type: string
          description: Ticket reference number
        estimatedResolutionTime:
          type: string
          description: Estimated resolition time for the ticket created
        urgency:
          type: string
          description: Urgency / priority of the created ticket
        docketRefNumber:
          type: string
        incidentReopenCount:
          type: number
          description: Number of times the ticket has been re-opened
    MediumCharacteristic:
      type: object
      description: Describes the contact medium characteristics that could be used to contact a party (an individual or an organization)
      properties:
        contact:
          type: string
          description: Person's phone number or email
        buildingNumber:
          type: string
          description: Building number
        city:
          type: string
          description: The city
        contactType:
          type: string
          description: 'The type of contact, for example: phone number such as mobile, fixed home, fixed office. postal address such as shipping instalation…'
        addressType:
          type: string
          description: Type of address such as residential address, office address etc.
        placeName:
          type: string
          description: Name of village or town or place etc.
        sectorName:
          type: string
          description: Name of sector or relevant etc.
        cellName:
          type: string
          description: Name of cell number or town or place etc.
        districtName:
          type: string
          description: Name of village or town or place etc.
        street1:
          type: string
          description: Describes the street
        state:
          type: string
        region:
          type: string
          description: Region of the complainant
        street:
          type: string
        street2:
          type: string
        postCode:
          type: string
          description: Postcode
        stateOrProvince:
          type: string
          description: State or province
        country:
          type: string
          description: The country
        emailAddress:
          type: string
          description: Full email address in standard format
        faxNumber:
          type: string
          description: The fax number of the contact
        phoneNumber:
          type: string
          description: The primary phone number of the contact
        alternateNumber:
          type: array
          items:
            type: string
            description: List of alternate phone/contact numbers of the customer
            example:
            - '2507865432'
        socialNetworkId:
          type: string
          description: Identifier as a member of a social network
        '@baseType':
          type: string
          description: When sub-classing, this defines the super-class
        '@schemaLocation':
          type: string
          description: A URI to a JSON-Schema file that defines additional attributes and relationships
          format: uri
        '@type':
          type: string
          description: When sub-classing, this defines the sub-class entity name
    ContactMedium:
      type: object
      description: Indicates the contact medium that could be used to contact the party.
      properties:
        mediumType:
          type: string
          description: 'Type of the contact medium, such as: physicalAdress,postalAddress,contactPerson etc.'
        preferred:
          type: boolean
          description: If true, indicates that is the preferred contact medium
        characteristic:
          $ref: '#/components/schemas/MediumCharacteristic'
          description: Any additional characteristic(s) of this contact medium
        '@baseType':
          type: string
          description: When sub-classing, this defines the super-class
        '@schemaLocation':
          type: string
          description: A URI to a JSON-Schema file that defines additional attributes and relationships
          format: uri
        '@type':
          type: string
          description: When sub-classing, this defines the sub-class entity name
    ticketResponse_2:
      type: object
      required:
      - targetIncidentNumber
      - statusCode
      - statusMessage
      - originTransactionId
      - targetTransactionId
      properties:
        targetIncidentNumber:
          type: string
          description: Target ticket identifier, this is the id of the ticket at the target system
        statusCode:
          type: string
          description: Status code from target system to indicate transaction status
        statusMessage:
          type: string
          description: Status response description
          example: processed
        originTransactionId:
          type: string
          description: Transaction identifier generated by system originating the request
          example: MTN123456
        targetTransactionId:
          type: string
          description: Transaction identifier generated by target
          example: 17af7d89db62885072fa83305b961972
        data:
          $ref: '#/components/schemas/TicketCreateData'
    updateTicket_2:
      type: object
      required:
      - transactionId
      - originSystem
      - targetSystem
      - targetIncidentNumber
      properties:
        transactionId:
          type: string
          description: Transaction identifier used by client
          example: 123ABC
        originSystem:
          type: string
          description: System originating the request
          example: SERVICENOW,REMEDYSA
        targetSystem:
          type: string
          description: System receiving the request
          example: REMEDYSA,SERVICENOW
        targetIncidentNumber:
          type: string
          description: Incident number at the target system
          example: INC0011964
        shortDescription:
          type: string
          description: Brief description about the ticket
          example: Superman is sick
        detailedDescription:
          type: string
          description: More detailed description of the ticket
          example: Superman is sick because he was exposed to Kryptonite
        impact:
          type: string
          description: Level of impact
          example: '1'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        urgency:
          type: string
          description: Level of urgency
          example: '3'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        attachmentFilename:
          type: string
          description: Name of file being attached
          example: image1.png
        attachmentData:
          type: string
          format: base64
          description: Attachment data encoded in base64
          example: fdgrdvh22dhv2dhtdt3h35th4
        state:
          type: string
          description: Only applicable for values 2,3,6,7,8. Value 1 is set when an incident is created. Value 2 can only be set if the ticket 'assignedTo' field was prevously set
          example: '3'
          enum:
          - '2'
          - '3'
          - '6'
          - '7'
          - '8'
        assignedTo:
          type: string
          description: Who the incident is assigned to
          example: integration.mtn.sa.remedy
        closeCode:
          type: string
          description: Applicable when setting 'state' to 6. This value is used to indicate the code for resolution.
          enum:
          - Not Resolved – Not Reproducible
          - Not Resolved – Problem Raised
          - Not Resolved – Resolved by Vendor
          - Resolved - Workaround Applied
          - Resolved – Fixed by Caller
          - Resolved – Fixed Without Action
          - Resolved – Permanent Fix Applied
          example: Resolved – Permanent Fix Applied
        closeNotes:
          type: string
          description: Custom notes for closing ticket.
          example: All done!
        comments:
          type: string
          description: Comments to incident
          example: My comments
        workNotes:
          type: string
          description: Work notes to incident
          example: My notes
        subcategory:
          type: string
          description: Incident category
          example: database
        interface:
          type: string
          description: interface applicable to requests for RemedySA
          example: interface
        signalName:
          type: string
          description: signalName applicable to requests for RemedySA
          example: signalName
        summary:
          type: string
          description: summary applicable to requests for RemedySA
          example: summary
        detailedSummary:
          type: string
          description: detailedSummary applicable to requests for RemedySA
          example: detailedSummary
        status:
          type: string
          description: Status of the ticket
        statusUpdateTime:
          type: string
          format: datetime
        commentsUpdateTime:
          type: string
          format: datetime
          description: Time when a new comment is being submitted
        statusUpdateStaffCode:
          type: string
          description: Staff number of the individual submitting the update
        commentsUpdateStaffCode:
          type: string
          description: Comment of the individual submitting the update
    newTicket_2:
      type: object
      required:
      - targetSystem
      - originSystem
      - transactionId
      - callerId
      - originIncidentNumber
      - shortDescription
      properties:
        targetSystem:
          type: string
          description: System receiving the request
          example: REMEDYSA
          enum:
          - REMEDYSA
          - SERVICENOW
          - CLM
        originSystem:
          type: string
          description: System originating the request
          example: SERVICENOW
          enum:
          - REMEDYSA
          - SERVICENOW
        transactionId:
          type: string
          description: Transaction identifier used by client
          example: 123ABC
        callerId:
          type: string
          description: User from calling system
          example: a.gonzalez.bogaz@accenture.com
        originIncidentNumber:
          type: string
          description: Origin ticket identifier, this is the id of the ticket at the originating system
          example: INC0011558
        shortDescription:
          type: string
          description: Brief description about the ticket
          example: Superman is sick
        detailedDescription:
          type: string
          description: More detailed description of the ticket
          example: Superman is sick because he was exposed to Kryptonite
        impact:
          type: string
          description: Level of impact
          example: '1'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        urgency:
          type: string
          description: Level of urgency
          example: '3'
          enum:
          - '1'
          - '2'
          - '3'
          - '4'
        interface:
          type: string
          description: interface applicable to requests for RemedySA
          example: interface
        signalName:
          type: string
          description: signalName applicable to requests for RemedySA
          example: signalName
        attachmentFilename:
          type: string
          description: Name of file being attached
          example: image1.png
        attachmentData:
          type: string
          format: base64
          description: Attachment data encoded in base64
          example: fdgrdvh22dhv2dhtdt3h35th4
        customerId:
          type: string
          description: Mobile number of the entity reporting the incident
        entityType:
          type: string
          description: Categorisation of the entity that has created the ticket. P -> Profile Level S -> Single Service Level I -> Individual Level
          enum:
          - P
          - S
          - I
        ticketCategoryCode:
          type: string
          description: Represents code of the Trouble ticket Category created
        destinationNumber:
          type: string
          description: Represents destination number
        ticketCategory:
          type: string
          description: Ticket category
        ticketSubCategory:
          type: string
          description: Ticket level 2 category
        subscriberName:
          type: string
          description: Subscriber Name
        contactMedium:
          $ref: '#/components/schemas/ContactMedium'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      name: X-API-Key
      in: header
    OAuth2:
      type: oauth2
      flows:
        clientCredentials:
          scopes: {}
          tokenUrl: https://api.mtn.com/v1/oauth/access_token
x-refined-from:
- mtn-group-job-card-management.yml
- mtn-group-ticket.yml