Update an email address
patch
/fscmRestApi/resources/11.13.18.05/personProfiles/{PartyId}/child/emails/{EmailId}
Request
Path Parameters
-
EmailId(required): integer(int64)
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=
-
PartyId(required): integer(int64)
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
-
Metadata-Context:
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".
-
REST-Framework-Version:
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
- application/json
Root Schema : schema
Type:
Show Source
object-
EmailAddress: string
Title:
EmailMaximum Length:320The email address of the person. -
PreferredFlag: boolean
Title:
PreferredMaximum Length:1Default Value:falseIndicates the preferred email address.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
Root Schema : personProfiles-emails-item-response
Type:
Show Source
object-
EmailAddress: string
Title:
EmailMaximum Length:320The email address of the person. -
EmailId: integer
(int64)
Title:
Email IDRead Only:trueThe unique identifier for an email address. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
PreferredFlag: boolean
Title:
PreferredMaximum Length:1Default Value:falseIndicates the preferred email address. -
PurposeCode: string
Title:
PurposeMaximum Length:30The type of purpose for email contact, such as work, emergency, and home. A list of accepted values is defined in the lookup type ORA_HEY_EMAIL_CONTACT_PURPOSE. -
PurposeMeaning: string
Title:
PurposeRead Only:trueMaximum Length:80The meaning of the purpose code. A list of accepted values is defined in the lookup type ORA_HEY_EMAIL_CONTACT_PURPOSE.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- EmailPurposeLOV
-
Parameters:
- finder:
LookupTypeFinder%3BLookupType%3DCONTACT_POINT_PURPOSE%2CLookupCode%3D{PurposeCode}
The following properties are defined on the LOV link relation:- Source Attribute: PurposeCode; Target Attribute: LookupCode
- Display Attribute: Meaning
- finder: