Skip to content

Add to Cart

The add-to-cart notification is to be sent with a ticket when a visitor adds an eSales product to their cart. The ticket is a unique string for an object generated by eSales.


Request method


Request URL


Request parameters

Name Type Description Example
market string The visitor market. Must match the corresponding market identifier in the data feed.
customerKey string A key that uniquely identifies the current visitor.
Using UUIDs as keys are recommended.
sessionKey string A unique key, identifying the session.
Using UUIDs as keys are recommended.
ticket string Unique ticket for the eSales object.

Request headers

All request headers are optional, but recommended when eligible.

  • Content-Type - application/json. To prevent automatic browser preflight requests, text/plain is also supported.
  • Accept-Encoding - gzip. Allows responses to be compressed using Gzip.
  • User-Agent - User agent. Enables internal tracking.

Request body

    "ticket": "string"

Request example

An add-to-cart notification example is demonstrated using cURL below.


    "ticket": "Oy9keW5hbWljLXBhZ2VzL3N0YXJ0L2VzYWxlcy1zdGFydC0xOyM7cHJvZHVjdF9rZXk7UF8xMjUzODMtMDAxNF9VSzsjOztOT05FOk5PTkU7NjE7"


curl -i \
-T request-body.json \
-H "Content-Type: text/plain" \
-H "Accept-Encoding: gzip" \
-H "User-Agent: {client user agent}" \


Response headers


Response content-type

HTTP response code

Response codes

Response Description
204 Notifications was received successfully.
400 Invalid or missing required arguments.
5xx Server error such as cluster unavailable or busy. The response body may contain more information about the error.

Response objects

Response example
HTTP/1.1 204 No Content

Last update: June 18, 2021

This online publication is intellectual property of Apptus Technologies. Its contents can be duplicated in part or whole, provided that a copyright label is visibly located on each copy and the copy is used in conjunction with the product described within this document.

All information found in these documents has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither Apptus Technologies nor the authors shall be held liable for possible errors or the consequences thereof.

Software and hardware descriptions cited in these documents might be registered trademarks. All trade names are subject to copyright restrictions and may be registered trademarks. Apptus Technologies essentially adheres to the manufacturer’s spelling. Names of products and trademarks appearing in this document, with or without specific notation, are likewise subject to trademark and trade protection laws and may thus fall under copyright restrictions.