The first query retrieves only the entity's first name and last name in the response. The second query retrieves all the entity's attributes.

For example, select=uri,label,attributes._lookupCodes,attributes._lookupValues.

• sendHidden: Entities with hidden attributes. Default is disabled.
• ovOnly: Only attribute values that have the ov=true flag.
• nonOvOnly: Only attribute values that have the ov=false flag. If you have a nested or reference attribute value, where ov=true, but subattributes, where ov=false, then these subattributes won’t appear in the response.
• serializeInitialSourcesInCrosswalks: URIs of initial sources in crosswalks.
• cleanEntity- Set this option to true to get entities without certain properties. Here's what you get in the response:
  • URI is null.
  • Type of entity is available.
  • createdBy, createdTime, updatedBy, and updatedTime are included.
  • Simple and nested attributes are displayed without the uri, ov, type, and label parameters.
  • For refEntity and refRelation, the uri, type, createDate,updateDate, attributeURIs, startRefPinned, endRefPinned, startRefIgnored, endRefIgnored, and objectURI are included.
  • Field crosswalks type is updated with its short name, reltioLoadDate, createDate, and updateDate.
  • Field attributes for crosswalk block contains only short URIs.
  • singleAttributeUpdateDates field for crosswalk block is empty.
  • analyticsAttributes is not included.
• showAppliedSurvivorshipRules: Returns the survivorship determination logic used to determine the OV value of an attribute, down to the lowest level (the primary and fallback strategies in order they were applied) for each attribute and each value of an attribute. A sample response is given below:

  {
    "ovDetails": {
      "appliedSurvivorshipRules": {
        "Aggregation": [
          "Aggregation ",
          "LUD"
        ]
      },
      "appliedSurvivorshipGroup": "default",
      "participationStatus": "strategy",
      "matchedFilters": [
        {
          "and": [
            {
              "uri": "configuration/entityTypes/HCO/attributes/MultipleFilters",
              "value": "unmatchedValue",
              "operator": "ne"
            }
          ]
        }
      ],
      "unmatchedFilters": [
        {
          "uri": "configuration/entityTypes/HCO/attributes/MultipleFilters",
          "value": "matchedValue",
          "operator": "ne"
        }
      ]
    }
  }

  Note: The new ovParticipationStatus property indicates how an attribute value participates in OV calculation. It explicitly represents values that are excluded or handled differently during OV processing. This property supports the following enum values: ignored, pinned, end-dated-crosswalk, not-participated, and strategy.
• showEndDatedReferenceAttributes: Includes reference attributes with an expired relationship end date. This option is displayed only when the tenant has skipEndDatedReferenceAttributes enabled.
• explainOv: returns additional survivorship diagnostics in the ovDetails section, including matched and unmatched filters as defined in the business configuration. It also includes all fields returned by showAppliedSurvivorshipRule. A sample response is given below:

{
  "ovDetails": {
    "appliedSurvivorshipRules": {
      "Aggregation": [
        "Aggregation ",
        "LUD"
      ]
    },
    "appliedSurvivorshipGroup": "default",
    "participationStatus": "strategy",
    "matchedFilters": [
      {
        "and": [
          {
            "uri": "configuration/entityTypes/HCO/attributes/MultipleFilters",
            "value": "unmatchedValue",
            "operator": "ne"
          }
        ]
      }
    ],
    "unmatchedFilters": [
      {
        "uri": "configuration/entityTypes/HCO/attributes/MultipleFilters",
        "value": "matchedValue",
        "operator": "ne"
      }
    ]
  }
}

reverseTranscodeLookups=Salesforce

For example, when you run the GET endpoint GET /reltio/api/{tenantId}/entities/{id} with sendMasked=True, the UI sends the parameter for masked data. If you run it with sendMasked=False, the UI executes GET https://<env>.reltio.com/nui/reltioAPI/api/<tenant_id>/entities/<entity_id>/attributes/<attribute>/<?>/<subattribute>/<?>. If you want the masked data again, the UI clears the plain text values and gets the masked version.