Update a communication response row

patch

/fscmRestApi/resources/11.13.18.05/communicationResponses/{ResponseToken}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Response Page Content
    The content to be used by the consent page based on the action taken by the recipient. The content can have multiple sections like Header, Message, Confirmation and Button.
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 : communicationResponses-item-response
Type: object
Show Source
  • Links
  • Title: Message Response Code
    Read Only: true
    The response provided by the recipient to an actionable email. For example, values can be ORA_HEY_COMM_ACTION_ACCEPT and ORA_HEY_COMM_ACTION_DENY. A list of accepted values is defined in the lookup type ORA_HEY_COMM_ACTION_TYPE.
  • Title: Response Page Content
    The content to be used by the consent page based on the action taken by the recipient. The content can have multiple sections like Header, Message, Confirmation and Button.
  • Title: Response Token
    Read Only: true
    Maximum Length: 64
    The unique identifier for a communication response row.
Back to Top