Get a Student Management organization name

get

/fscmRestApi/resources/11.13.18.05/hedOrganizationContacts/{ContactPartyId}/child/names/{namesUniqID}

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=
  • This is the hash key of the attributes which make up the composite key for the Student Management Organization Contact Names resource and used to uniquely identify an instance of Student Management Organization Contact Names. The client should not generate the hash key value. Instead, the client should query on the Student Management Organization Contact Names collection resource in order to navigate to a specific instance of Student Management Organization Contact Names to get the hash key.
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 : hedOrganizationContacts-names-item-response
Type: object
Show Source
  • Title: First Name
    Maximum Length: 150
    The first name of a person.
  • Title: Full Name
    Maximum Length: 360
    The first and last name of the person displayed as a single string.
  • Title: Last Name
    Maximum Length: 150
    The last name of a person.
  • Links
  • Title: Middle Name
    Maximum Length: 60
    The middle name of a person.
  • Title: Name Suffix
    Maximum Length: 30
    The name suffix of a person such as junior or senior.
  • Title: Name Type
    Maximum Length: 30
    The type of the name. It's a value defined by the Additional Party Name and Identifier Type entity. A list of accepted values is defined in the lookup type ORA_HEY_NAME_TYPE.
  • Title: Name Type
    Read Only: true
    Maximum Length: 80
    The meaning of the name type code. A list of accepted values is defined in the lookup type ORA_HEY_NAME_TYPE.
  • Title: Party Name ID
    Read Only: true
    The unique identifier for a name.
  • Title: Preferred
    Indicates that this name record contains the person's preferred name.
  • Title: Only One Name
    Maximum Length: 1
    Default Value: false
    Indicates if the person has single name, typically a last name only, and that other names such as first name and middle name are intentionally blank.
  • Title: Title
    Maximum Length: 60
    The title of the person, such as Mr or Mrs.
Back to Top