Get all missing person contacts

get

/fscmRestApi/resources/11.13.18.05/hedPersonProfiles/{PartyId}/child/missingPersonContacts

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=
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
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds the missing person contact that matches the primary key criteria specified.
      Finder Variables
      • MissingPersonContactId; integer; Unique identifier for missing person contact.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AdditionalEmail; string; The additional email for a missing person contact.
    • AdditionalEmailTypeCode; string; The additional email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • AdditionalEmailTypeMeaning; string; The meaning of the additional email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • AdditionalPhoneAreaCode; string; The area code for additional phone of a missing person contact.
    • AdditionalPhoneCountryCode; string; The country code for additional phone of a missing person contact.
    • AdditionalPhoneExtension; string; The extension for additional phone of a missing person contact.
    • AdditionalPhoneNumber; string; The additional phone number for a missing person contact.
    • AdditionalPhoneTypeCode; string; The additional phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • AdditionalPhoneTypeMeaning; string; The meaning of the additional phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • ContactTypeCode; string; The missing person contact type of the person, such as Spouse, Parent, and Grandparent. A list of accepted values is defined in the lookup type ORA_HEY_EMERGENCY_CONTACT_TYPE.
    • ContactTypeMeaning; string; The meaning of missing person contact type. A list of accepted values is defined in the lookup type ORA_HEY_EMERGENCY_CONTACT_TYPE.
    • Email; string; The email for a missing person contact.
    • EmailTypeCode; string; The email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • EmailTypeMeaning; string; The meaning of the email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • FirstName; string; The first name of a person.
    • LastName; string; The last name of a person.
    • MiddleName; string; The middle name of the person.
    • MissingPersonContactId; integer; The unique identifier of a missing person contact.
    • NameSuffix; string; The suffix can be junior or senior.
    • PhoneAreaCode; string; The area code within a country code.
    • PhoneCountryCode; string; The country code for phone of a missing person contact.
    • PhoneExtension; string; The extension number for a phone number.
    • PhoneNumber; string; The phone number formatted in the local format. The number should not include area code, country code, or extension.
    • PhoneTypeCode; string; The phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • PhoneTypeMeaning; string; The meaning of the phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
    • PreferredFlag; boolean; Indicates the preferred emergency contact.
    • SingleNameFlag; boolean; Indicates if the person has single name.
    • Title; string; The title of the person, such as Mr or Mrs.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : hedPersonProfiles-missingPersonContacts
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : hedPersonProfiles-missingPersonContacts-item-response
Type: object
Show Source
  • Title: Additional Email
    Maximum Length: 1000
    The additional email for a missing person contact.
  • Title: Additional Email Type Code
    Maximum Length: 30
    The additional email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Additional Email Type Name
    Read Only: true
    Maximum Length: 80
    The meaning of the additional email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Additional Phone Area Code
    Maximum Length: 10
    The area code for additional phone of a missing person contact.
  • Title: Additional Phone Country Code
    Maximum Length: 10
    The country code for additional phone of a missing person contact.
  • Title: Additional Phone Extension
    Maximum Length: 10
    The extension for additional phone of a missing person contact.
  • Title: Additional Phone Number
    Maximum Length: 40
    The additional phone number for a missing person contact.
  • Title: Additional Phone Type Code
    Maximum Length: 30
    The additional phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Additional Phone Type Name
    Read Only: true
    Maximum Length: 80
    The meaning of the additional phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Relationship Type
    Maximum Length: 30
    The missing person contact type of the person, such as Spouse, Parent, and Grandparent. A list of accepted values is defined in the lookup type ORA_HEY_EMERGENCY_CONTACT_TYPE.
  • Title: Relationship Type
    Read Only: true
    Maximum Length: 80
    The meaning of missing person contact type. A list of accepted values is defined in the lookup type ORA_HEY_EMERGENCY_CONTACT_TYPE.
  • Title: Email
    Maximum Length: 1000
    The email for a missing person contact.
  • Title: Email Type Code
    Maximum Length: 30
    The email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Email Type Name
    Read Only: true
    Maximum Length: 80
    The meaning of the email type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: First Name
    Maximum Length: 150
    The first name of a person.
  • Title: Last Name
    Maximum Length: 150
    The last name of a person.
  • Links
  • Title: Middle Name
    Maximum Length: 60
    The middle name of the person.
  • Title: Missing Person Contact ID
    Read Only: true
    The unique identifier of a missing person contact.
  • Title: Name Suffix
    Maximum Length: 30
    The suffix can be junior or senior.
  • Title: Area Code
    Maximum Length: 10
    The area code within a country code.
  • Title: Phone Country Code
    Maximum Length: 10
    The country code for phone of a missing person contact.
  • Title: Phone Extension
    Maximum Length: 10
    The extension number for a phone number.
  • Title: Phone Number
    Maximum Length: 40
    The phone number formatted in the local format. The number should not include area code, country code, or extension.
  • Title: Phone Type Code
    Maximum Length: 30
    The phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Phone Type Name
    Read Only: true
    Maximum Length: 80
    The meaning of the phone type code. A list of accepted values is defined in the lookup type CONTACT_POINT_PURPOSE.
  • Title: Preferred
    Maximum Length: 1
    Default Value: false
    Indicates the preferred emergency contact.
  • Title: Only One Name
    Maximum Length: 1
    Default Value: false
    Indicates if the person has single name.
  • Title: Title
    Maximum Length: 60
    The title of the person, such as Mr or Mrs.
Back to Top