Skip to main content

Entrupy Certificate

What are Entrupy Certificates?​

Entrupy Certificates are secure digital records that verify the authenticity of an item. Once an item is authenticated using Entrupy's technology—whether through an SDK-integrated application or via the Entrupy App—an Entrupy Certificate is generated and associated with that specific item. Certificates provide verifiable proof that an item has been assessed by Entrupy, increasing confidence and trust for buyers and sellers.

An Entrupy Certificate includes:

  • A unique certificate ID (Entrupy ID).
  • Photos of the item.
  • Date of authentication.
  • Metadata such as brand, date code, style code and serial number.
  • Optionally, the provided customer_item_id: this field is hidden by default, but can be enabled on a per-user or per-account basis by request.

Integrating with Entrupy Certificates​

  • SDK-Integrated Applications: The Mobile SDKs can directly display the certificate and its details within your application's user interface.
  • Entrupy App Users: Business users can manage certificates directly within the Entrupy App and use the API (with customer_item_id) to pull certificate data into their backend systems for broader operational integration.
  • API (Universal Access): The API is the core tool for backend systems to fetch certificate data and verify status for items processed by either SDK flows or the Entrupy App. API endpoints for managing certificate transfers are planned for future release.

Refer to the API Reference and specific SDK guides (Mobile SDKs) for detailed technical implementation.

Certificate Transfers​

Entrupy supports the ability to transfer the certificate to a buyer, allowing the record of authenticity to follow the item if it changes ownership. This is an important feature for maintaining the chain of trust throughout an item's lifecycle. The process will be primarily driven by the Entrupy API, and the updated certificate holder information will then be reflected where the certificate is displayed (e.g., in the SDK's Detail View if applicable, or when a new holder views it).

Planned Feature

Certificate transfer functionality via the API is planned for future release. Once available, the following capabilities will be provided:

Planned API Functionality:

  • Initiation: Certificate transfers will be initiated via the API. Refer to the API v2.0 Reference for details once available. This will allow a platform (acting on behalf of the current certificate holder) to initiate the transfer. The request body will typically include details of the recipient.
  • Querying Transfer Status & Details: The API will allow you to query the current status of a certificate, including who the current holder is. If an item's certificate has been transferred, the original authentication record will typically indicate this and may link to the new certificate details or holder information.
  • Management: The API will provide the necessary tools to manage the transfer process as an integrator.