Get a relationship type

get

/crmRestApi/resources/11.13.18.05/relationshipTypes/{relationshipTypesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- RelationshipTypeId, LookupType and LookupCode ---for the Relationship Types resource and used to uniquely identify an instance of Relationship Types. The client should not generate the hash key value. Instead, the client should query on the Relationship Types collection resource with a filter on the primary key values in order to navigate to a specific instance of Relationship Types.

    For example: relationshipTypes?q=RelationshipTypeId=<value1>;LookupType=<value2>;LookupCode=<value3>
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 : relationshipTypes-item-response
Type: object
Show Source
  • Title: Circular
    Read Only: true
    Maximum Length: 1
    Indicates whether the circular relationships are allowed using this relationship type.
  • Read Only: true
    Maximum Length: 30
    The backward relationship code used to describe relationships like SUPPLIER_OF.
  • Read Only: true
    Maximum Length: 150
    The application module that created the record. It is defaulted to value HZ_WS for all web service based creation. A list of valid certification level codes is defined in the lookup HZ_CREATED_BY_MODULES. Review and update the codes using the Setup and Maintenance task, Manage Trading Community Common Lookups.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    The description of the relationship role.
  • Read Only: true
    Maximum Length: 30
    The direction code validated by DIRECTION_CODE lookup type. P for Parent, C for Child, and N for Not Directional.
  • Read Only: true
    The date when the relationship role ends.
  • Read Only: true
    Maximum Length: 30
    The forward relationship code used to describe relationships like CUSTOMER_OF.
  • Read Only: true
    Maximum Length: 30
    The relationship role lookup language.
  • Links
  • Read Only: true
    Maximum Length: 30
    The relationship role code.
  • Read Only: true
    Maximum Length: 30
    The role lookup code HZ_RELATIONSHIP_ROLE.
  • Read Only: true
    Maximum Length: 80
    The meaning of the relationship role.
  • Title: Object Type
    Read Only: true
    Maximum Length: 30
    The object type of the relationship type.
  • Title: Relationship Type
    Read Only: true
    Maximum Length: 30
    The name of the relationship type like CUSTOMER_SUPPLIER.
  • Read Only: true
    The unique identifier of the relationship type.
  • Read Only: true
    Maximum Length: 30
    The unique relationship role lookup code based on relationship type and phrase. In the HZ_RELATIONSHIP_ROLE lookup type meaning is the plural role and description is the singular role.
  • Read Only: true
    The unique identifier of the set, value 0.
  • Read Only: true
    Maximum Length: 4
    The source language of the relationship role.
  • Read Only: true
    The date when the relationship role starts.
  • Read Only: true
    Maximum Length: 1
    Indicates whether the relationship type is inactive or active with values like I for Inactive, A for Active.
  • Title: Subject Type
    Read Only: true
    Maximum Length: 30
    The subject type of the relationship type. You can't use this attribute as a finder, because this is a transient field. The response will return an error if you use this attribute as a finder.
  • Read Only: true
    Maximum Length: 150
    The role tag of the relationship.
  • Read Only: true
    Maximum Length: 2
    The territory code of the relationship role.
  • Read Only: true
    The unique identifier of the view application of the relationship role lookup code.
Back to Top