Jump to

• Request
• Response

Create a set of email contact points for the user profile

post

/fscmRestApi/resources/11.13.18.05/publicSectorProfileContactEmails

Request

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.
• Upsert-Mode:
  When set to true, the server will perform an Upsert operation instead of a Create. In an Upsert operation the server attempts to find an existing resource that matches the payload. If found, the server updates the existing resource instead of creating a new one. If not found, or when set to false (the default), a Create is performed.

Supported Media Types

• application/json

Request Body - application/json ()

The following table describes the body parameters in the request for this task.

Root Schema : schema

Type: object

Show Source

• ContactPointPurpose: string
  Title: Type

  The email type. Valid values are BUSINESS for work and PERSONAL for home.
• ContactPtId: integer (int64)
  The unique identifier for the email contact point.
• EmailAddress: string
  Title: Email

  The email address for the email contact point.
• PrimaryFlag: string
  Title: Primary

  Maximum Length: 1

  Indicates whether an email is the primary email for the profile. Valid values are Y for yes and N for no.
• ProfileId: integer (int64)
  The unique identifier for the profile that is associated with the email contact point.
• Status: string
  The status of the email contact point. Valid values are A for active and I for inactive.

{
    "type":"object",
    "properties":{
        "ProfileId":{
            "type":"integer",
            "description":"The unique identifier for the profile that is associated with the email contact point.",
            "format":"int64",
            "nullable":false,
            "x-hints":{
                "precision":18
            }
        },
        "Status":{
            "type":"string",
            "description":"The status of the email contact point. Valid values are A for active and I for inactive.",
            "nullable":false,
            "x-queryable":false
        },
        "PrimaryFlag":{
            "title":"Primary",
            "maxLength":1,
            "type":"string",
            "description":"Indicates whether an email is the primary email for the profile. Valid values are Y for yes and N for no.",
            "nullable":false
        },
        "ContactPtId":{
            "type":"integer",
            "description":"The unique identifier for the email contact point.",
            "format":"int64",
            "nullable":false,
            "x-hints":{
                "precision":18,
                "fnd:GLOBALLY_UNIQUE":"true"
            }
        },
        "ContactPointPurpose":{
            "title":"Type",
            "type":"string",
            "description":"The email type. Valid values are BUSINESS for work and PERSONAL for home.",
            "nullable":true,
            "x-queryable":false
        },
        "EmailAddress":{
            "title":"Email",
            "type":"string",
            "description":"The email address for the email contact point.",
            "nullable":true,
            "x-queryable":false
        }
    }
}

Back to Top

Response

Supported Media Types

• application/json

Default Response

The following table describes the default response for this task.

Headers

• Metadata-Context(required):
  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(required):
  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 : publicSectorProfileContactEmails-item-response

Type: object

Show Source

• ContactPointPurpose: string
  Title: Type

  The email type. Valid values are BUSINESS for work and PERSONAL for home.
• ContactPtId: integer (int64)
  The unique identifier for the email contact point.
• EmailAddress: string
  Title: Email

  The email address for the email contact point.
• links: array Links
  Title: Links

  The link relations associated with the resource instance.
• PrimaryFlag: string
  Title: Primary

  Maximum Length: 1

  Indicates whether an email is the primary email for the profile. Valid values are Y for yes and N for no.
• ProfileId: integer (int64)
  The unique identifier for the profile that is associated with the email contact point.
• Status: string
  The status of the email contact point. Valid values are A for active and I for inactive.

{
    "type":"object",
    "properties":{
        "ProfileId":{
            "type":"integer",
            "description":"The unique identifier for the profile that is associated with the email contact point.",
            "format":"int64",
            "nullable":false,
            "x-hints":{
                "precision":18
            },
            "x-queryable":true
        },
        "Status":{
            "type":"string",
            "description":"The status of the email contact point. Valid values are A for active and I for inactive.",
            "nullable":false,
            "x-queryable":false
        },
        "PrimaryFlag":{
            "title":"Primary",
            "maxLength":1,
            "type":"string",
            "description":"Indicates whether an email is the primary email for the profile. Valid values are Y for yes and N for no.",
            "nullable":false,
            "x-queryable":true
        },
        "ContactPtId":{
            "type":"integer",
            "description":"The unique identifier for the email contact point.",
            "format":"int64",
            "nullable":false,
            "x-hints":{
                "precision":18,
                "fnd:GLOBALLY_UNIQUE":"true"
            },
            "x-queryable":true
        },
        "ContactPointPurpose":{
            "title":"Type",
            "type":"string",
            "description":"The email type. Valid values are BUSINESS for work and PERSONAL for home.",
            "nullable":true,
            "x-queryable":false
        },
        "links":{
            "title":"Links",
            "type":"array",
            "description":"The link relations associated with the resource instance.",
            "items":{
                "$ref":"#/components/schemas/link"
            }
        },
        "EmailAddress":{
            "title":"Email",
            "type":"string",
            "description":"The email address for the email contact point.",
            "nullable":true,
            "x-queryable":false
        }
    }
}

Nested Schema : Links

Type: array

Title: Links

The link relations associated with the resource instance.

Show Source

• Array of: object link

{
    "title":"Links",
    "type":"array",
    "description":"The link relations associated with the resource instance.",
    "items":{
        "$ref":"#/components/schemas/link"
    }
}

Nested Schema : link

Type: object

Show Source

• href: string
  Title: hyperlink reference

  The URI to the related resource.
• kind: string
  Title: kind

  Allowed Values: [ "collection", "item", "describe", "other" ]

  The kind of the related resource.
• name: string
  Title: name

  The name of the link to the related resource.
• properties: object properties
• rel: string
  Title: relation

  Allowed Values: [ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]

  The name of the relation to the resource instance. Example: self.

{
    "type":"object",
    "properties":{
        "kind":{
            "title":"kind",
            "type":"string",
            "description":"The kind of the related resource.",
            "enum":[
                "collection",
                "item",
                "describe",
                "other"
            ]
        },
        "rel":{
            "title":"relation",
            "type":"string",
            "description":"The name of the relation to the resource instance.  Example: self.",
            "enum":[
                "self",
                "lov",
                "parent",
                "canonical",
                "child",
                "enclosure",
                "action",
                "custom"
            ]
        },
        "name":{
            "title":"name",
            "type":"string",
            "description":"The name of the link to the related resource."
        },
        "href":{
            "title":"hyperlink reference",
            "type":"string",
            "description":"The URI to the related resource."
        },
        "properties":{
            "type":"object",
            "properties":{
                "changeIndicator":{
                    "type":"string",
                    "description":"Change indicator or the ETag value of the resource instance."
                }
            }
        }
    }
}

Nested Schema : properties

Type: object

Show Source

• changeIndicator: string
  Change indicator or the ETag value of the resource instance.

{
    "type":"object",
    "properties":{
        "changeIndicator":{
            "type":"string",
            "description":"Change indicator or the ETag value of the resource instance."
        }
    }
}

Back to Top