Get a channel communication

get

/crmRestApi/resources/11.13.18.05/serviceRequests/{SrNumber}/child/messages/{MessageId}/child/channelCommunication/{ViaId}

Request

Path Parameters
  • The unique identifier of the service request message.
  • The unique number that is used to identify a service request. You can configure the service request number to a format that is best suitable to your organizational requirements. For example, service request may have the formats service request0000012345, service request_000_12345, 12345_00_service request, and so on depending on your requirements.
  • The unique identifier of the service request channel communication record.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : serviceRequests-messages-channelCommunication-item-response
Type: object
Show Source
  • Title: Account Name
    Read Only: true
    Maximum Length: 400
    The account name associated with the channel. For example, for email, an account name would be the inbound mailbox for support like support@abc.com.
  • Title: Display Name
    Maximum Length: 400
    The display name of the channel.
  • Title: Channel ID
    The unique identifier of the channel.
  • Title: Channel Short Name
    Maximum Length: 450
    The public unique identifier of the channel.
  • Title: Channel Type
    Read Only: true
    Maximum Length: 30
    The code indicating the channel type. For example, email, phone, social, and so on. A list of accepted values is defined in the lookup ORA_SVC_CHANNEL_TYPE_CD.
  • Title: Collaboration ID
    Read Only: true
    Maximum Length: 255
    The unique identifier of the collaboration network user in the corresponding network. An example of this is the slack user Id. of a user.
  • Title: Resource Name
    Read Only: true
    Maximum Length: 400
    The user name of the external user on the collaboration network.
  • Title: Collaboration Resource Identifier
    The unique identifier of the collaboration network user that the internal users are communicating with.
  • Title: Contact Point ID
    The unique identifier of the contact point record of the contact who is being communicated with. A contact point is a contact's identifier for a specific channel of communication. For example, the contact point for the email channel would be an email address and the contact point of a person for twitter would be the twitter handle.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the communication channel.
  • Title: Creation Date
    Read Only: true
    The date and time when the communication channel was created.
  • Title: Inbound Message Object Identifier
    The unique identifier of the inbound object that resulted in the creation of the service request message.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the communication channel was last updated.
  • Title: Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the communication channel.
  • Title: Update Login
    Read Only: true
    Maximum Length: 32
    The session login associated to the user who last updated the communication channel.
  • Links
  • Title: Message Number
    Read Only: true
    Maximum Length: 30
    The public unique identifier of the service request message.
  • Title: Network
    Read Only: true
    Maximum Length: 30
    The code indicating the social network of the post. For example, Facebook, Twitter. A list of accepted values is defined in the lookup HZ_INSTANT_MESSENGER_TYPE.
  • Title: Object ID
    The unique identifier of the object. Depending on the object type, indicates the service request id or the service request message id associated with the channel communication.
  • Title: Object Type
    Read Only: true
    Maximum Length: 30
    Default Value: SVC_SR_MESSAGES
    The code indicating whether the channel communication record is associated to the service request or the service request message. A list of accepted values is defined in the lookup ORA_SVC_CHANNEL_OBJECT_TYPE_CD.
  • Title: Party ID
    The unique party identifier of the person who is being communicated with.
  • Title: Party Name
    Read Only: true
    Maximum Length: 360
    The party name of the person who is being communicated with. The user can be an internal resource or a customer contact.
  • Title: Party Number
    Read Only: true
    Maximum Length: 30
    The public unique identifier of the contact associated with the service request message.
  • Title: Party Endpoint
    Maximum Length: 1000
    The endpoint used to communicate with the Party_ID owner. For example, email address, phone number, and so on. When Party_ID is NULL and PartyViaEndPoint is not NULL, the endpoint belongs to an adhoc party.
  • Title: Person ID
    The unique identifier of the person who is a contact on the service request.
  • Title: Post Identifier
    Maximum Length: 1000
    The unique identifier of the social media post record that was used to create the service request or the service request message.
  • Title: Resource ID
    Read Only: true
    The unique identifier of the resource associated with the service request. This is a foreign key that can identify the collaboration network user the internal users are communicating with.
  • Title: Resource Type
    Read Only: true
    Maximum Length: 30
    The code indicating the type of the collaborative network user, such as USER, PUBLIC_CHANNEL, or PRIVATE_CHANNEL. A list of accepted values is defined in the lookup ORA_SVC_COLLAB_RES_TYPE_CD.
  • Title: Routing Code
    Maximum Length: 30
    The code indicating how the message was routed through the endpoint. For example, if the endpoint is email address the field indicates if the recipient was a TO, a CC, or a BCC recipient. A list of accepted values is defined in the lookup ORA_SVC_CHANNEL_ROUTING_CD.
  • Title: ID
    Read Only: true
    The unique identifier of the channel communication.
Back to Top