--- title: LexisNexis DDP Query node description: The LexisNexis DDP Query node queries the LexisNexis Dynamic Decision Platform for a policy decision about a user session for fraud risk assessment in Advanced Identity Cloud and PingAM journeys. component: auth-node-ref version: latest page_id: auth-node-ref:cloud:lexis-ddp-query canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/lexis-ddp-query.html llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-09-17T14:22:55Z keywords: ["Nodes & Trees", "Journeys", "Authentication", "LexisNexis DDP", "Device Intelligence"] page_aliases: ["threat-metrix-query.adoc"] section_ids: example: Example availability: Availability inputs: Inputs dependencies: Dependencies configuration: Configuration outputs: Outputs callbacks: Callbacks outcomes: Outcomes errors: Errors --- # LexisNexis DDP Query node The LexisNexis DDP Query node makes a DDP API request to either the session query API or the attribute query API. The session query API requires the LexisNexis DDP Profiler node to collect device intelligence, whereas the attribute query API doesn't involve device intelligence. Attribute query is useful in situations where a LexisNexis product such as Emailage or InstantID can be invoked for a risk assessment without device intelligence. This node: * Queries the DDP * Retrieves a policy decision about the user session * Stores the configured query parameters in shared state ## Example Read the [Example LexisNexis DDP journey](lexis-ddp.html#lexis-ddp-example). ## Availability | Product | Available? | | ---------------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes | | Ping Advanced Identity Software (self-managed) | Yes | ## Inputs This node reads the following from the shared state, depending on the Attribute Source configuration: * `username`: the user's username string. Required to resolve the desired identity when Attribute Source is `User Directory`. * `objectAttributes`: the user parameters for the attribute mapping. Required when Attribute Source is `Shared State`. ## Dependencies You must set up integration with the LexisNexis DDP portal before using this node in a journey. If the query type is session query, the journey must include the [LexisNexis DDP Profiler node](lexis-ddp-profiler.html) to collect device intelligence before this node. ## Configuration | Property | Usage | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Org ID | The unique ID associated with DDP for your organization. | | API Key | The unique API key generated by the DDP portal and associated with the Org ID. | | Policy | The policy to use for the query. The policy is configured in the DDP portal and is a set of decision policy rules that together generate the risk assessment policy score and outcome. | | Base URL | The domain URL for the DDP region where API requests are sent. The default is the global region. | | Service Type | Defines the API response output fields returned from the API request. The default is `session-policy`. | | Event Type | The type of transaction or event. The default is the login event. | | Query Type | The query type to send as the DDP API request.- `Session Query` requires device intelligence collected previously by the LexisNexis DDP Profiler node. - `Attribute Query` doesn't require device profile information. | | Add additional attributes to API Request | Enable this property to add additional parameters to the DDP API request. In general, add as much data as possible to the API requests to improve the fidelity of the risk assessment. | | Attribute Source | Where additional attributes are fetched at runtime. Either `User Directory` (looks for attributes in the identity store) or `Shared State` (looks in the shared memory of the authentication journey). | | Query Attributes | A list of key-value pairs. The key is a DDP attribute and the value is an attribute in the authentication journey. The Attribute Source configuration defines where the values are fetched. If the values can't be fetched, the API request doesn't include the DDP attribute. | ## Outputs This node writes the following to the shared state: * `ddp.query_api_response`: the full API response. This value is further processed by the [LexisNexis DDP Review Status node](lexis-ddp-review-status.html) or the [LexisNexis DDP Reason Code node](lexis-ddp-reason-code.html). * `ddp.failure_reason`: text associated with the error condition, if an error outcome is triggered. This node removes the `ddp.session_id` value from the shared state after the query succeeds, as the value is no longer needed for integration. ## Callbacks This node doesn't send any callbacks. ## Outcomes * `Next` The DDP query API completed successfully. * `Error` The API resulted in a non-success, or there is an integration error. Check the debug log files for any integration issues. If the configuration looks accurate, open a support case with LexisNexis. ## Errors This node doesn't log any error or warning messages of its own.