Jump to Content
Ometria developer docs
HomeGuidesRecipesAPI Reference
Log InOmetria developer docs
Guides
Log In
HomeGuidesRecipesAPI Reference

Ometria data API

  • Ometria API introduction
  • Ometria data architecture
  • Push endpoint
    • List validation errors
  • Products
    • Products, product listings and product variants
  • Orders
  • Contacts
  • GDPR data anonymisation
  • Merge profiles

Transactional email API

  • Transactional email API
    • Transactional API payload examples
    • Transactional API HTML examples
    • Transactional API data sets

JavaScript tracking

  • JavaScript tracker
    • Setting tags for overlays
  • Debugging JavaScript tracking
  • Google tag manager

Website personalisation

  • Getting started with website personalisation
    • Elements
    • Best practices
    • Front end integration overview
  • Website personalisation: Sending data to Ometria
  • Website personalisation: JavaScript integration
    • CORS
    • Website personalisation tag options
    • Autocomplete API
    • Query API
    • Product detail page
    • Tracking API
    • Privacy and GDPR
  • Website personalisation: Headless API integration
    • Access and authentication
    • Headless Query API reference
    • Headless Query API examples
    • Headless Query API JSON response
    • Headless tracking API reference
  • Website personalisation: Templating
    • Website personalisation template functions
    • Templating objects
    • Templating tags
    • Templating filters
Powered by 

Push endpoint

Suggest Edits

We recommend reading the following pages before integrating with Ometria:

  • Ometria API introduction
  • Ometria data architecture

The push endpoint of Ometria's API passes:

  • contacts, orders,
  • products, and;
  • custom events.

The push endpoint is the simplest way to send eCommerce data to Ometria.

To use the push endpoint you send an HTTP POST request to the push endpoint containing a JSON formatted array of objects.

Updated almost 4 years ago