Skip to main content

Catalog Data

What is Catalog Data?​

Entrupy's Catalog Data refers to the set of information collected and organized about items submitted to Entrupy, whether processed via an SDK-integrated application or directly using the Entrupy App. This data goes beyond simple authentication results and can include detailed product information, condition assessments and links to marketplace listings for similar items.

The Entrupy API is the primary way to access this catalog data, typically using the customer_item_id you assigned to the item during its processing (either through the SDK flow or when inputted into the Entrupy App).

What It Includes​

Catalog Data typically encompasses:

  • Item Identification: Brand, model, style, customer_item_id (your identifier).
  • High-Quality Imagery: Images captured during the authentication process form a part of the catalog data for an item.
  • Detailed Characteristics: Materials, colors, dimensions, unique identifiers (serial numbers where applicable).
  • Condition Assessment: Information related to the item's condition, which can be captured during the authentication process.
  • Marketplace Data (Contextual): In some cases, and with appropriate integrations, Catalog Data might link to or include information from public marketplace listings where an item has appeared. This helps in understanding an item's provenance and market presence. Note that pricing information within marketplace listings may be localized to specific regions.

Accessing Item Images and Catalog Data​

You can retrieve catalog data (which may include images if requested) using the GET /v2/authentications/{entrupy_id} endpoint. You would typically know the {entrupy_id} by first looking up an item using its customer_item_id if you don't already have the Entrupy-specific ID.

To include images in the response, use the include_images=true query parameter. To ensure catalog data is included, use include_catalog=true.

Refer to the OpenAPI Specification for /v2/authentications/{entrupy_id} for the detailed response structure including the catalog object and images array.

Data Structure​

Product Details​

Contains detailed information about the specific item:

  • brand: The brand name (e.g., "Louis Vuitton")
  • category: The specific product type or category (e.g., "Tote Bag")
  • style: The actual product style name (e.g., "Neverfull MM") - an important component for precise product identification
  • material: The primary material (e.g., "Monogram Canvas")
  • colorway: The color description (e.g., "Beige/Brown")
  • description: A detailed textual description of the product

Condition Assessment​

Provides an evaluation of the item's current condition:

  • score: Numerical condition score (0-10 scale)
  • rating: Textual condition rating ("Poor", "Fair", "Good", "Very Good", "Excellent")
  • issues: Array of identified condition issues (e.g., ["Minor wear on handles"])
  • details: Component-specific assessment with detailed breakdown (e.g., exterior vs. interior condition)

Marketplace Listings​

Array of relevant marketplace listings found for similar items:

  • platform: Name of the marketplace (e.g., "The RealReal")
  • title: Title of the listing
  • price: Formatted price string (e.g., "$1,200") (Note: pricing information may be localized to specific regions)
  • extracted_price: Numerical price value (e.g., 1200.0)
  • currency: Currency code (e.g., "USD")
  • confidence: Confidence level of the match ("High", "Medium", "Low")
  • link: URL to the listing
  • image_url: URL of the product image on the listing
  • platform_logo: URL of the platform's logo
  • stock_information: Stock availability (e.g., "In Stock")
  • thumbnail: URL of the thumbnail image

Availability and Configuration​

The availability and display of specific catalog data elements can also be configured based on your integration. We are continuously working to enhance this data, which is generated for all items processed by Entrupy.

Contact your Entrupy representative to discuss specific catalog data configurations for your use case.

Important Considerations for Pricing Data​

  • Regional Pricing: Pay attention to the regional_pricing array for localized price information. Marketplace pricing data aims to be geographically relevant.
  • Data Freshness: Marketplace pricing data is frequently refreshed to maintain accuracy, with a target freshness of 1-2 days. However, this information should be used as a reference, as market values can fluctuate. Do not assume prices are real-time or guaranteed.
  • Data Accuracy: While Entrupy strives to provide accurate catalog data, including pricing, this information should be used as a reference. Market values can fluctuate, and specific item conditions may impact actual pricing.
  • Availability: The availability of specific pricing fields may vary.

How Integrators Can Use Catalog Data​

Integrators can use Catalog Data from items processed via SDK or the Entrupy App in various ways:

  • Automate Listing Creation: Reduce manual data entry by populating product images, details, descriptions, and condition information directly from the API, using customer_item_id to fetch the data.
  • Enhance Product Displays: Provide richer, more detailed information to potential buyers on your platform.
  • Inform Pricing Strategies: Use marketplace listing data as an input for pricing decisions.
  • Internal Analytics: Analyze product trends and condition patterns across your entire inventory of Entrupy-processed items.

Exposing Data to Your Users:

You have flexibility in how you present this data. For example:

  • Display comprehensive details to your internal teams or for operational purposes.
  • Show curated information to your sellers to help them accurately list items, potentially with marketplace platform names anonymized or hidden if you prefer to use the pricing data as a general market reference.
  • Use the item images and detailed descriptions to enrich the content on your platform.