IBM Support

QRadar: API queries to the log_source_management endpoint returns "null" results



When an API is used to query a log source, it can display "null" values in the JSON response. Null data in most fields of the API queries can indicate a lack of permissions to pull all of the data from the /config/event_sources/log_source_management/log_sources endpoint. It is not uncommon for a user with incorrect permissions to receive only the log source ID and the name, with the rest of the parameters returned as null. If most values are null, review the permissions for the user or authorized service token permissions.


The common cause for this issue is incorrect permissions for the user or token.

Diagnosing The Problem

To diagnose this issue, you can either use the Interactive API for Developers page, or you can log in on the Console CLI.
  1. Log in to the QRadar Console.
  2. Click the Admin tab, Log Sources icon.
  3. Retrieve the Log Source ID for the log source. In this example, the log source ID is 512.
  4. In the Interactive API for Developers, navigate to the /config/event_sources/log_source_management/log_sources/{id} endpoint.
  5. In the Parameters, type your log source ID and click Try it Out.

    As all fields are null, except for the name, id, and description, the user or authorized token does not have the correct permissions to poll for all data.
    Optionally, administrators familiar with the command line can use curl to verify the results. For example,
    curl -S -X GET -H 'SEC:<token>' -H 'Range: items=0-49' -H 'Version: 16.0' -H 'Accept: application/json' 
    'https://<console-IP>/api/config/event_sources/log_source_management/log_sources' | grep <Log source ID>
    Response output,

Resolving The Problem

Create an authorized services token with the required permissions.


  1. To create an Authorized Services token, you must configure:
    • User role: The User Role must have either "System Administrator", "Security Admin" or "Manage Log Sources" permissions to retrieve all fields of a log source. If we do not have those permissions, we can still call the GET endpoints, but we get the ID and name fields only, and none of the configuration details. For more information, see User roles
    • Security profile: Security profiles define which networks, log sources, and domains that a user can access. The user role is relevant, but not the security profile for this permission issue. For more information, see Security profiles.
  2. Verify sure the User Role has the following permissions:
    • Delegated Administration
    • Manage Log Source
    • Log Activity (managing Log Sources requires Log Activity)
      Note: Other QRadar API endpoints also exhibit the same behavior of 'null' values when the particular user or token does not have correct permission.

      After the authentication token or user is configured with the correct permissions, the JSON response displays all values for the log source. For example, the interactive API response is 200 and includes all configured fields for the log source.

      Example curl output:
      [{"severity":"ERROR","text":"Events have not been received from this Log Source in over 720 


Document Location


[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwsyAAA","label":"Admin Tasks"}],"ARM Case Number":"TS008111064","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
27 February 2023