Programmatic Access to Session Data

The Entrupy Android SDK provides authentication data through its built-in UI — the Detail View Controller for individual item details — and through the Entrupy API from your backend.

Overview

Authentication data flows through two primary channels:

• SDK UI (client-side): The Detail View displays authentication results and item details scoped to the logged-in user.
• Entrupy API (server-side): Your backend receives authentication results and status updates via webhooks, and can query the API for cross-user reporting and data synchronization.

1. SDK UI Components

Detail View

For individual item details, launch the Detail View using an Entrupy ID:

import com.entrupy.sdk.app.EntrupyApp

fun showItemDetails(entrupyId: String) {
    EntrupyApp.sharedInstance().displayDetailViewForItem(entrupyId)
}

The Detail View displays:

• Authentication result (Authentic, Unknown, Not Supported, etc.)
• Item metadata (brand, item type, style)
• Processing status and timeline
• Certificate access (for authentic items)
• Flag status and support features

2. Authentication Data Model

The SDK uses the AuthenticationItem data class to represent authentication records. Key properties include:

Property	Description
authenticationId	Unique Entrupy identifier for the authentication
properties	Item metadata — brand, model, function
status	Current status — result (ResultStatusId), flag (FlagStatusId)
images	Captured images (thumbnails, uploaded images)
eventTimes	Processing timeline events
timestamp	Submission timestamp
textFields	Custom text fields (e.g., customer_item_id)

Result Status Values

The ResultStatusId enum represents the possible authentication outcomes:

import com.entrupy.core.partner.data.model.ResultStatusId

Value	Description
NEEDS_REVIEW	Pending manual review
RECEIVED	Submission received, processing
REGISTERED	Item registered in the system
NOT_AVAILABLE	Result not available
INVALID	Invalid submission
AUTHENTIC	Item authenticated as genuine
UNKNOWN	Unable to determine authenticity
NOT_SUPPORTED	Item type not supported for authentication
NO_MATCH	No match found in reference data
MATCH	Match found in reference data
ANALYZED	Analysis complete
CANCELED	Authentication canceled
DATA_REQUIRED	Additional data required
REGISTRATION_INVALID	Registration is invalid
REGISTRATION_NOT_SUPPORTED	Registration type not supported
MATCH_FOUND	Match found
NO_MATCH_FOUND	No match found

3. Server-Side Data Access

For backend data access, reporting, and cross-user queries, use the Entrupy API:

• Webhooks: Receive real-time notifications for result updates, flag changes, and other events.
• API queries: Retrieve authentication details, search across users, and synchronize with your internal systems.
• Data mapping: Use customer_item_id to map Entrupy authentications to your internal records.

Refer to Essential Backend Integration Tasks for setup details.

Best Practices

• Use SDK UI for user-facing features. The Detail View provides a maintained, consistent experience.
• Use the API for backend operations. Reporting, cross-user search, and data synchronization should go through your backend.
• Map IDs consistently. Store the authenticationId alongside your customer_item_id for reliable cross-referencing.

Next Steps

• See Searching SDK Authentications for detail view and backend search.
• Review Customer Support Integration for flag and support features.
• Set up backend webhooks for server-side data flow.