Skip to content
One2Five Developer Portal

Knowledge Hub

  • One2Five Platform Overview
  • Concepts
  • Fundamentals
  • Path of a Review
  • Review Verification
  • Authenticity
  • Badges
  • Best Practices
  • One2Five Shopify App
  • One2Five WooCommerce Plugin
  • Additional Resources

API Reference

  • API Introduction
  • Full API Reference
  • Submission
    • Authentication
    • Submit Review
    • Submit Feedback
    • Submit Review Answer
    • Submit Answer
    • Submit Question
    • Submit PIE-feed
    • Submit PIE-feed-interaction
  • Display
    • Fetch Reviews
    • Get Reviews
    • Get Review Answers
    • Display Reviews HTML
    • Get Review Exists
    • Get Questions
  • Home
  • One2Five developer pages
  • Knowledge Hub
  • Review Verification

Review Verification

The aim is to enhance consumer protection by reducing the prevalence of false, misleading, and deceptive reviews in online commerce. This involves ensuring that reviews come from genuine customers who have actually purchased or used the product, rather than from fake accounts, bots, or incentivized sources. By implementing stricter verification mechanisms and review authenticity checks, the goal is to foster a more trustworthy and transparent online shopping environment.

Such efforts not only help consumers make better-informed decisions but also support fair competition among sellers. Reliable review systems can build consumer confidence and reduce the risk of manipulation or fraud, ultimately leading to a healthier and more accountable e-commerce ecosystem.

Components #

The following table summarizes the components you will need to understand in order to implement the review verification flow. These components will be referenced throughout the rest of this documentation. Familiarizing yourself with them will make understanding the One2Five review verification easier.

ComponentDescriptionOwner
Submission FormThis is a web form you build and host. Authors will use it to submit contentClient/One2Five
Verification pageThis page is designed and hosted by the client, or if the client does not have the feasibility, then One2Five provides a default to which the user gets redirected to on clicking the verification link got on emailClient/One2Five
Authentication emailThis email, which is typically sent by One2Five, asks the user to confirm they submitted the content by clicking on a link including a unique auth token.  Clicking on the link opens a URL to your verification service.One2Five
TokenThis is a web form you build and host. Authors will use it to submit contentOne2Five

Walk Through #

How it works

  • Submit Content
    • The process starts with a content submission to the One2Five platform
  • Verification mail sent to the content author
    • After the review submission, the One2five platform triggers an email to the user who submitted the content.
  • The author clicks the verification link in the email
    • The verification email contains a link with a token, which will redirect to the page referenced by the hostedAuthentication_CallbackURL provided while content submission.
  • Updating review status
    • on clicking the verification link which we shared to the user, the review status is now changed from not verified to verified/open.

Process and different options for verification setup #

  • hosted authentication on the client side
  • hosted authentication on the One2Five side
  • No authentication required (PIE, signed in user on client side)

Hosted authentication on the client side

In this process, authentication and verification of the content submitted is done at the client side, while submitting the content, One2Five will need two parameters HostedAuthentication_AuthenticationEmail and HostedAuthentication_CallbackURL.

HostedAuthentication_AuthenticationEmail: This parameter tells the One2Five platform where to send the email containing the authentication link.

HostedAuthentication_CallbackURL: This URL will be used as the front-end to your authentication service. This hostedAuthentication_CallbackURL is the page where the verification API will get triggered. However, One2Five needs a dedicated hosted verification page from the client side that triggers our authentication API for the verification step itself.

Here is an example of submitreview.json POST request.

parameters used for example should look like:

1. hostedAuthentication_AuthenticationEmail = someuseremail@domain.com

2. hostedAuthentication_CallbackURL = URL where the client has hosted the page or has a mechanism to call our authentication API.

3. isAuthenticationRequired = true

Hosted authentication on the One2Five side

In this process, One2Five platform has provides a verification page is hosted at One2Five platform side, and the url provided by our platform should be used as a value for hostedAuthentication_CallbackURL.

Whenever a content is submitted using the callback url provided by One2Five platform, the user gets an email with the link to redirect to the provided url where the verification page is hosted , which internally call the authentication api to authenticate and verify the content.

Here is an example of submitreview.json POST request.

parameters used for example should look like:

default call back urls:

test environment : http://authentication-test.one2five-reviews.com/verification.html

production environment : http://authentication.one2five-reviews.com/verification.html
1. hostedAuthentication_AuthenticationEmail = someuseremail@domain.com

2. hostedAuthentication_CallbackURL = call back url provided by one2five platform.

3. isAuthenticationRequired = true

No authentication required (PIE, signed in user on client side)

One2Five offers its customers the capability to request reviews via email, collectively termed as Post Interaction Emails (PIE). In this process, an email is sent to users that redirects them to the PIE submission form. These mechanisms ensure the reviews are collected from earlier purchasers of the product. This form can be customised as per the client. Once the review is submitted, no authentication or verification is required

Pie review submission through pie mail sendout:
Here is an example of submitreview.json POST request.
Request:

apiversion : 5.4

passKey : ibmgltgs-fhlc-ntxo-fzkz-etnkhwmihpwj

DisplayCode : msm-de_de

action : submit

FP : 0400R9HVeoYv

productId : 3005

userId : 75847785871

rating : 5

title : Fantastic Device – Exceeded My Expectations!

reviewText : I recently purchased this Refrigerator and couldn’t be happier with my decision! The build quality is excellent, and it feels durable yet sleek. The performance is outstanding—fast, efficient, and exactly as advertised. The battery life is impressive, lasting much longer than I expected, and the user interface is incredibly intuitive. Setup was a breeze, and it has quickly become an essential part of my daily routine. I highly recommend this to anyone looking for a high-quality and reliable gadget. Worth every penny!

contextDataValue_Competition : No

isRecommended : true

AgreedToTermsAndConditions : true

UserNickname : Kunal

rating_Design : 5

rating_Features : 5

rating_Quality : 5

SendEmailAlertWhenPublished : True

isAuthenticationRequired : false

contextdatavalue_VerifiedPurchaser : true

format : json

Link to API Reference

For detailed API documentation and usage instructions, please refer to the API Reference.

Updated on May 27, 2025
Table of Contents
  • Components
  • Walk Through
  • Process and different options for verification setup