A customer needs to access profile data using /access/entities endpoint.

To retrieve specific profile information programmatically via the Adobe Experience PlatformReal-Time Customer Profile API, developers must use the /access/entities endpoint. Because the profile store is a NoSQL environment designed for high-speed lookups, the system requires specific coordinates to locate a profile fragment or a merged profile. These required parameters are theEntity Identity(the actual value of the ID, such as "user@example.com") and theEntity ID Namespace(the context of that ID, such as "email").

When making a GET request to this endpoint, the id and namespace parameters are mandatory because a single identity value might exist in multiple namespaces (e.g., the numeric string "12345" could be a CRM_ID for one person and a Loyalty_ID for another). Providing both ensures the API returns the correct entity. Option A is incorrect as timestamps are used for filtering or auditing but not for primary entity retrieval. Option C is incorrect because names and dates of birth are attributeswithina profile, not the unique lookup keys used by the API's identity-based indexing system. Mastery of these parameters is essential for developers building custom integrations or troubleshooting profile data within the platform.