KT-CT-1113: Disabled GraphQL field requested.
KT-CT-7618: Unable to process message.
KT-CT-7620: Channel not supported.
KT-CT-7621: Attachment not found.
KT-CT-7622: Attachment bucket is invalid.
KT-CT-7623: Attachment path is invalid.
KT-CT-7625: Invalid email address.
KT-CT-7627: The 'email' object is missing from the payload.
KT-CT-7628: The 'generic' object is missing from the payload.
KT-CT-7629: The 'post' object is missing from the payload.
KT-CT-7630: Message with this message ID has already been processed.
KT-CT-7632: The text content of the Ink Inbound Generic Message is too long.
KT-CT-7653: Account numbers on the message and message type must match if both are supplied.
KT-CT-7654: An account number was provided, but no corresponding account could be found.
KT-CT-7899: An internal error occurred.

Allowed Viewers

Customer

Partner User

Third party

Required Permissions

Can create ink inbound messages

Query Complexity

Examples

The example data in the variables and responses below are autogenerated values designed to resemble real inputs. They do not represent actual customer data, and in some cases may require additional validation.

Query

mutation CreateInkInboundMessage($input: CreateInkInboundMessageInput) {
  createInkInboundMessage(input: $input) {
    message {
      ... on InkEmail {
        ...InkEmailFragment
      }
      ... on InkGenericMessage {
        ...InkGenericMessageFragment
      }
      ... on InkLine {
        ...InkLineFragment
      }
      ... on InkLiveChatMessage {
        ...InkLiveChatMessageFragment
      }
      ... on InkPost {
        ...InkPostFragment
      }
      ... on InkSMS {
        ...InkSMSFragment
      }
      ... on InkTwilioWhatsApp {
        ...InkTwilioWhatsAppFragment
      }
      ... on InkWhatsApp {
        ...InkWhatsAppFragment
      }
    }
  }
}

Variables

{
  "input": CreateInkInboundMessageInput
}

Response

{
  "data": {
    "createInkInboundMessage": {
      "message": InkEmail
    }
  }
}