The Reevoo customer_order and customer_orders functionality for submitting orders/sales via an API is being deprecated along with the Reevoo brand. The functionality to allow you to continue to submit orders/sales via an API is supported on Feefo through our EnterSaleRemotely API.

The Feefo EnterSaleRemotely API allows POST requests of single order-product lines to be submitted to your Feefo account, further combining follow up POST requests of multiple products, automatically batching the order together if the requests contain the same order reference, merchant identifier, and future feedback date.

Feefo provide multiple methods of uploading order/sale information which are detailed on our knowledgebase, but the direct replacement for your previous implementation is our EnterSaleRemotelyAPI, which is also detailed on our knowledgebase.

API endpoint

The EnterSaleRemotely API endpoint is https://api.feefo.com/api/20/entersaleremotely

POST requests made against this endpoint will return a 200 response, 500 response, or 400 response.

Specifying account

On Feefo, your account is specified against a parameter called a merchant identifier, which can be found within your Feefo accounts business details page. Your account structure on Feefo may contain a group-level account. If it does, any request sent to that group-level account which specifies a merchant identifier within that account structure will automatically be accepted and submitted to the correct account within the structure, specified by that merchant identifier.

Authentication

Unlike the Reevoo customer_order API, the Feefo EnterSaleRemotely API authenticates against an Oauth 2.0 bearer token, generated by secure credentials stored on your Feefo accounts App Keys. Details on how to generate and provide a bearer token are stored on our knowledgebase.

The resulting token should be applied as a Authorization header in your request, with the value being Bearer TOKENGENERATED.

Parameters/order information

Once the POST request to the EnterSaleRemotely endpoint has a valid Feefo App Key Oauth 2.0 generated and applied as a header, the order/sale information can be added through the Body as raw JSON or x-www-form-urlencoded content.

The old customer_order API parameters and their applicable new parameters, and subsequent information, has been provided below.

Feefo provides many new parameters. Most of these parameters are Product parameters which are optional, being ingested by Feefo through your product feed, product catalogue, and/or Google shopping feed connection. While orderref and feedbackdate are not mandatory for the upload to be successful, we strongly recommend they are provided where possible.

Old parameter
New parameter
Requirement
Description
Example
Old parameter
New parameter
Requirement
Description
Example
trkref
merchantidentifier
Mandatory
The merchant’s unique Feefo identifier.
best-fridge-uk
email
email
Mandatory
The customer's email address.
john.smith@email.com
first_name
name
Mandatory
The customer's name.
John Smith
sku
productsearchcode
Mandatory
The product identifier.
FRESH222
order_date
date
Mandatory
The date of the sale.
01/01/2023
order_ref
orderref
Recommended
The merchant’s order reference number.
FRE22JHSM23
customer_ref
customerref
Optional
The merchant’s customer reference number.
JS02
locale
locale
Optional
The language of the emails that are sent to the customer.
en_GB
price
amount
Optional
The price paid for the item purchased.
300.00
currency
currency
Optional
Currency for the amount.
GBP

 

feedbackdate
Recommended
A specific date on which the feedback for this order should be sent out.
01/02/2023

 

tags
Optional
Used for filtering data by sales or product attributes for further analysis.

 

 

description
Optional
The description of the item purchased.

 

 

parentsearchcode
Optional
The product's parent identifier.

 

 

gtin
Optional
The product’s Global Trade Item Number (GTIN)

 

 

mpn
Optional
The product’s Manufacturer Part Number (MPN)

 

 

productlink
Optional
The URL to the product page for the product.

 

 

productattributes
Optional
Product qualities requiring targeted feedback through separate feedback form questions.

 

fulfilment_date
N/A
N/A
N/A

 

language
N/A
N/A
N/A

 

title
N/A
N/A
N/A

 

order_items
N/A
N/A
N/A

 

metadata
N/A
N/A
N/A

 

key_with_underscore
N/A
N/A
N/A

 

An example request with POST raw JSON BODY is below:

Endpoint:
POST: https://api.feefo.com/api/20/entersaleremotely
HEADER: Authorization:Bearer TOKEN-GENERATED
BODY:

{
"merchantidentifier": "adam-tech-test",
"email": "john.smith@feefo.com",
"name": "John",
"description": "JSONPOST",
"orderref": "POSTJSON01",
"date": "01/01/2000",
"vendorref": "JSONPOST"
}