REST API Event Type

REST API events contain details about REST-specific requests.

For details about event monitoring, see the Trailhead Event Monitoring module or REST API Developer’s Guide.

  • Type: String
  • Description: The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from AppExchange) is shown as “Salesforce.com IP”.
  • Example: 96.43.144.26
  • Type: String
  • Description: The name of the client that’s using Salesforce services. This field is an optional parameter that can be passed in API calls.
  • Type: Reference
  • Description: The 15-character ID of the connected app associated with the API call.
  • Example: 0H4RM00000000Kr0AI
  • Type: Number
  • Description: The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.
  • Type: Number
  • Description: Indicates how much activity is occurring in the database. A high value for this field suggests that adding indexes or filters on your queries would benefit performance.
  • Type: Number
  • Description: The CPU time in milliseconds to complete the request. Indicates the amount of activity taking place in the database layer during the request.
  • Type: Number
  • Description: The time in nanoseconds for a database round trip. Includes time spent in the JDBC driver, network to the database, and DB_CPU_TIME. Compare this field to CPU_TIME to determine whether performance issues are occurring in the database layer or in your own code.
  • Type: Set
  • Description: The name of the object accessed by the API request.
  • Examples: Account, Opportunity, Contact, and so on
  • Type: String
  • Description: The type of event. The value is always RestApi.
  • Type: String
  • Description: The returned exception message, used to debug issues. Provide this message when seeking support.
  • Type: String
  • Description: The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring.
  • Example: GeJCsym5eyvtEK2I
  • Type: String
  • Description: The media type of the response.
  • Type: String
  • Description: The HTTP method of the request.
  • Examples: GET, POST, PUT, and so on
  • Type: Number
  • Description: The number of fields or columns, where applicable.
  • Type: Id
  • Description: The 15-character ID of the organization.
  • Example: 00D000000000123
  • Type: String
  • Description: The data that was queried.
  • Type: Number
  • Description: The size of the callout request body, in bytes.
  • Type: String

  • Description: The status of the request for a page view or user interface action. This field can have a blank value.

  • Possible values:

    • S - Success. Salesforce handled the request successfully. If an Apex controller throws an exception, this status is also returned.
    • F - Failure. Typically 4xx or 5xx HTTP codes, such as no permission to view page, page took too long to render, page is read-only.
    • U - Undefined
    • A - Authorization Error
    • R - Redirect. Typically a 3xx HTTP code, possibly initiated by an Apex controller in a Visualforce page.
    • N - Not Found. 404 error.
  • Type: String
  • Description: The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.
  • Example: 3nWgxWbDKWWDIk0FKfF5DV
  • Type: Number
  • Description: The size of the callout response, in bytes.
  • Type: Number
  • Description: The number of rows that were processed in the request.
  • Example: 150
  • Type: Number
  • Description: The amount of time that the request took in milliseconds.
  • Type: String
  • Description: The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started.
  • Example: d7DEq/ANa7nNZZVD
  • Type: Number
  • Description: The HTTP response status code for the request.
  • Type: String
  • Description: The access time of Salesforce services in GMT.
  • Example: 20130715233322.670
  • Type: DateTime
  • Description: The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). The timezone is GMT.
  • Example: 2015-07-27T11:32:59.555Z
  • Type: String
  • Description: The URI of the page that’s receiving the request.
  • Example: /home/home.jsp
  • Type: ID
  • Description: The 18-character case-insensitive ID of the URI of the page that’s receiving the request.
  • Type: Number
  • Description: The numeric code for the type of client used to make the request (for example, the browser, application, or API).
  • Type: Id
  • Description: The 15-character ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00530000009M943
  • Type: Id
  • Description: The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00590000000I1SNIA0
  • Type: String

  • Description: The category of user license.

  • Possible values:

    • CsnOnly - Users whose access to the application is limited to Chatter. This user type includes Chatter Free and Chatter moderator users.
    • CspLitePortal - CSP Lite Portal license. Users whose access is limited because they’re organization customers and access the application through a customer portal or an Experience Cloud site.
    • CustomerSuccess - Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal.
    • Guest - Users whose access is limited so that your customers can view and interact with your site without logging in.
    • PowerCustomerSuccess - Power Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal. Users with this license type can view and edit data they directly own or data owned by or shared with users below them in the customer portal role hierarchy.
    • PowerPartner - Power Partner license. Users whose access is limited because they’re partners and typically access the application through a partner portal or site.
    • SelfService - Users whose access is limited because they’re organization customers and access the application through a self-service portal.
    • Standard - Standard user license. This user type also includes Salesforce Platform and Salesforce Platform One user licenses, and admins for this org.