Retrieving Entity or sObject Logs

Use this API to retrieve logs using Salesforce sObject ID or Reltio Entity ID, grouped under track IDs.

Customers, Partners, or Reltio Professional Services team can search and retrieve request/response logs using the Reltio entity or Salesforce sObject IDs. These logs are grouped under a track ID that contains all the messages for an operation, performed on the entity or sObject. Each operation (for example, create, update, and so on) consists of several requests and responses between Reltio and Salesforce.

The response to the API call is a list of track IDs, which consist of the logs for an operation performed on the sObject ID or Entity ID. You must have the following roles to retrieve entity or sObject logs:

ROLE_SFDC_CONNECTOR

You can view the logs by using the Salesforce Connector Monitoring API.

To retrieve an entity or sObject log using a track ID.

Note: This endpoint is only available on Google Cloud Platform (GCP).

Request

GET {SFDCConnectorURL}\{tenant}\{profile}logging\object\{id}

Table 1. Parameters
Parameter		Required	Description
Headers	`Authorization`	Yes	Access Token in the format `Bearer <accessToken>` (for more information, see Authentication API).
Headers	`Content-Type`	Yes	Should be `Content-Type: application/json`
Path	`tenant`	Yes	Tenant ID
	`Profile`	Yes	Profile ID
	`id`	Yes	Entity or Salesforce object ID
Query	`tenantId`	Yes	Tenant ID
Query	`logLevel`	No	If this parameter is not specified, then records with the following log levels are returned: `DEBUG`, `INFO`, `WARNING`, `ERROR`, `CRITICAL`. Example: If the `logLevel` parameter is set to `DEBUG`, then records with the following levels are returned: `DEBUG`, `INFO`, `WARNING`, `ERROR`, `CRITICAL`. If the `logLevel` is set to `INFO`, then records with the following levels are returned: `INFO`, `WARNING`, `ERROR`, `CRITICAL`.
Query	`from`	No	This parameter allows to filter logs by time. By setting this parameter, only records with time later than `from` value are returned. A string in RFC 3339 format. For example: 2019-10-02T15:01:23.045Z. In filter expressions, `timestamp`s can specify a timezone with `Z` or `±hh:mm`. Timestamps are represented to nanosecond accuracy. Default value: Start of the current day. For example: 2019-10-02T00:00:00.000Z.
Query	`to`	No	This parameter allows to filter logs by time. By setting this parameter, only records with time earlier than `to` value are returned. A string in RFC 3339 format. For example: 2019-10-02T15:01:23.045Z. In filter expressions, timestamps can specify a timezone with `Z` or `±hh:mm`. Timestamps are represented to nanosecond accuracy. Default value: Start of the current day. For example: 2019-10-02T00:00:00.000Z.

Note: The maximum time range between from and to parameters is 7 days.

Response

Success: 200:
Body:
{
  "trackId #1": [
    {
      "timestamp": "2020-07-10T11:00:00.000Z",
      "severity": "INFO",
      "message": "env:tst-01<tenant+profile> <w1>: CNR_I062 Event 'updated' of 'Account' [00000000000000AAAA] processed"
    }
  ],
  "trackId #2": [
    {
      "timestamp": "2020-07-11T11:00:00.000Z",
      "severity": "INFO",
      "message": "env:tst-01<tenant+profile> <w1>: CNR_I062 Event 'updated' of 'Account' [00000000000000AAAA] processed"
    }
  ]
}
 
 
 
Error:   400, 403
Body:    { errors : [], warnings: [] }

Accelerate the Value of Data

Retrieving Entity or sObject Logs

Footer