MTN Group Accessible to 3PP API

openapi: 3.2.0
info:
  title: MTN Messaging USSD Accessible to 3PP API
  version: 1.0.0
  description: Provides a RESTful API to expose USSD capability.
servers:
- url: https://api.mtn.com/v1/
tags:
- name: Accessible to 3PP
  description: Accessible to Client APP (3PP) - ApiKeyAuth, to subscribe (MO/MT), unsubscribe and push/send message.
  externalDocs:
    url: https://#
paths:
  /messages/ussd/subscription:
    post:
      description: This function enables 3PP to subscribe to receive MO-generated messages from MADAPI.
      summary: The 3PP subscribes/registers to receive USSD MO-generated messages via MADAPI
      tags:
      - Accessible to 3PP
      operationId: ussdNotificationStart
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubscriptionResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Invalid access token. Please try with a valid token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: 'Authorization credentials passed and accepted but account does forbidden to send USSD

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '415':
          description: API does not support the requested content type
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '501':
          description: 'The HTTP method being used has not yet been implemented for

            the requested resource

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: The service requested is currently unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SubscriptionRequest'
        description: request body
        required: true
  /messages/ussd/subscription/{subscriptionId}:
    delete:
      description: This function enables 3PP to unsubscribe from receiving MO-generated messages from MADAPI.
      summary: The 3PP unsubscribes/de-registers from receiving/sending USSD MO/MT messages via MADAPI
      tags:
      - Accessible to 3PP
      parameters:
      - in: path
        name: subscriptionId
        required: true
        description: It is the subscriptionId that is used to delete existing USSD subscription .
        x-example: '123456'
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubscriptionResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Invalid access token. Please try with a valid token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: 'Authorization credentials passed and accepted but account does forbidden to send USSD

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '415':
          description: API does not support the requested content type
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '501':
          description: 'The HTTP method being used has not yet been implemented for

            the requested resource

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: The service requested is currently unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /messages/ussd/outbound:
    post:
      description: This function is used to send/push USSD MT Message to USSDGW for 3PPs with subscription on MADAPI.
      summary: The 3PP sends USSD MT Message to mobile subscriber through MADAPI
      tags:
      - Accessible to 3PP
      operationId: sendUSSDRequest
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutboundResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Invalid access token. Please try with a valid token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: 'Authorization credentials passed and accepted but account does forbidden to send USSD

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '415':
          description: API does not support the requested content type
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '501':
          description: 'The HTTP method being used has not yet been implemented for

            the requested resource

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: The service requested is currently unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/OutboundRequest'
        description: request body
        required: true
components:
  schemas:
    OutboundRequest:
      type: object
      required:
      - sessionId
      - messageType
      - msisdn
      - serviceCode
      - ussdString
      properties:
        sessionId:
          type: string
          description: Unique identifier of the session.
          example: '01235'
        messageType:
          type: string
          description: Message type. 0-Begin|1-Continue|2-End|3-Notification|4-Cancel|5-Timeout.
          example: '0'
        msisdn:
          type: string
          description: Mobile number of the message recipient.
          example: '2252312345'
        serviceCode:
          type: string
          example: '321123'
        ussdString:
          type: string
          description: USSD message content. If messageType is of type 4-Abort, this attribute will contain the abort reason or message.
          example: Please vote for xxx.
    OutboundResponse:
      type: object
      required:
      - statusCode
      - statusMessage
      - transactionId
      - data
      - _link
      properties:
        statusCode:
          type: string
          example: '0000'
        statusMessage:
          type: string
          example: ''
        transactionId:
          type: string
          example: ''
        data:
          type: object
          required:
          - outboundResponse
          - sessionId
          - msisdn
          properties:
            outboundResponse:
              type: string
              description: Value 0 indicates success.
              example: '0000'
            sessionId:
              type: string
              description: Unique identifier of the session.
              example: '01235'
            msisdn:
              type: string
              description: Mobile user msisdn.
              example: '2341234567'
        _link:
          $ref: '#/components/schemas/Links'
    SubscriptionRequest:
      type: object
      required:
      - serviceCode
      - callbackUrl
      - targetSystem
      properties:
        serviceCode:
          type: string
          example: '*1234*356#'
        callbackUrl:
          type: string
          description: URL from which the 3PP will receive MO-generated USSD message.
          example: http://10.138.40.69:11400/xportal/services/NetworkNotify
        targetSystem:
          type: string
          description: Name of the destined system for the callback url.
          example: AYO
    Links:
      type: object
      required:
      - self
      properties:
        self:
          type: object
          required:
          - href
          description: ''
          properties:
            href:
              type: string
              description: ''
              example: https://api.mtn.com/v1/messages/ussd/send
    SubscriptionResponse:
      type: object
      required:
      - data
      - statusCode
      - statusMessage
      - transactionId
      - _link
      properties:
        statusCode:
          type: string
          example: '0000'
        statusMessage:
          type: string
          example: Created
        transactionId:
          type: string
          example: xyz-0hij0hjh0-9y6
        data:
          type: object
          properties:
            subscriptionId:
              type: string
              description: The value is a random number defined by MADAPI and must be unique. Associated with the registered USSD.
              example: 123-xyz-456
        _link:
          $ref: '#/components/schemas/Links'
    Error:
      type: object
      required:
      - statusCode
      - statusMessage
      - transactionId
      properties:
        statusCode:
          type: string
          description: This is the MADAPI Canonical Response Code (it is 4 characters long and it is not the HTTP Status Code which is 3 characters long). Back-end system errors are mapped to specific Canonical Response Codes which are returned. More information on these mappings can be found on the MADAPI Confluence Page 'Response Codes'
          example: '3001'
        statusMessage:
          type: string
          description: More details on the returned status code which can be shown to a client
          example: A system error has occured
        supportMessage:
          type: string
          description: Internal message meant for consumers of the API to troubleshoot the error (could possible include the back-end system error code in the message if it would be useful)
          example: 400 Bad Request
        transactionId:
          type: string
          description: MADAPI generated Id to include for tracing requests
          example: xyz-t960-tuy
        timestamp:
          type: string
          format: date-time
          description: Timestamp that the error occurred
          example: 2020-08-01T12:34
        path:
          type: string
          description: The path that caused the error
          example: https://api.mtn.com/v1/<path>
        method:
          type: string
          description: The HTTP method type that was used
          example: POST
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key