Skip to content

Unexpected 400 Bad Request (DATA10005) on unique_device_connections_list endpoint despite valid payload structure #1295

Description

@Zot-Willie

Documentation link

[]
(https://pan.dev/access/api/insights/post-insights-v-3-0-resource-query-users-agent-unique-device-connections-list/)

Describe the problem

I am encountering a persistent 400 Bad Request error when trying to fetch data from the Prisma Access Insights API v3.0, specifically the unique_device_connections_list endpoint.

Endpoint:
POST https://api.sase.paloaltonetworks.com/insights/v3.0/resource/query/users/agent/unique_device_connections_list

The Issue:
Even when providing the filter parameters, the API constantly returns a 400 error.

Request Payload Tested:

JSON
{
"filter": {
"rules": [
{
"property": "event_time",
"operator": "last_n_days",
"values": [7]
}
]
}
}
(Note: I have also tried other parameter configurations, but the result is the same.)

Error Response Received:

JSON
{
"errorCode": "DATA10005",
"message": "Invalid Resource information name",
"details": "No value present"
}
Additional Context (Troubleshooting done):
To isolate the issue, I tested the exact same base JSON structure (e.g., {"filter": {"rules": []}}) on another endpoint: connected_user_count. That endpoint processed the request successfully and returned a 200 OK with the correct data. This indicates that my payload structure and authentication are completely valid.

The DATA10005 error implies that the unique_device_connections_list endpoint does not recognize the property names being passed, and unfortunately, the official API documentation does not clearly list the supported/required property fields specifically for this endpoint.

Request:
Could you please clarify the exact JSON payload schema required for this endpoint? Specifically, what are the exact valid property values supported by the unique_device_connections_list filter rules?

Thank you for your assistance.

Suggested fix

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions