Ometria Data API

Name: Ometria Data API
Brand: Ometria Data API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey34 EndpointsREST

For Agents

Push customer, product, order, and event data into Ometria's marketing platform and pull back segments, profiles, and unsubscribes for downstream campaigns.

Install Jentic One Beta

Connect the Ometria Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ometria Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fometria.com%2Fometria" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fometria.com%2Fometria" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ometria Data API.

Push customer, product, order, and custom event records via the bulk /push endpoint

Inspect /push-errors to diagnose rejected records from the last bulk import

Retrieve products and orders by ID for downstream catalogue sync

GET STARTED

Start building with Ometria Data API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Ometria Data API, keeping it validated and agent-ready. The Ometria Data API is the integration layer for Ometria's customer data and marketing platform, enabling brands to push customer, product, order, and event records into Ometria and to retrieve segmented data for downstream use. It exposes 34 endpoints covering bulk push, products, orders, contact collections, custom events, profile management with a profile-merge job system, list (segment) export, transactional email send, and unsubscribes/data-deletion request lookup. Authentication uses the X-Ometria-Auth header.

Use Cases

Patterns agents use Ometria Data API for, with concrete tasks.

★ Order and Customer Sync from E-Commerce

An e-commerce platform pipes new orders, customers, and product updates into Ometria using POST /push as the single ingestion endpoint, then polls GET /push-errors to surface rejected records back to the data team. This keeps the marketing platform in sync without bespoke per-resource endpoints.

POST a batch of 200 mixed records (customers, orders, products) to /push, then GET /push-errors to inspect any failures and re-push corrected records.

Segment Activation for Email Campaigns

Marketing teams build segments (lists) inside Ometria and use GET /lists/{list_id}/contacts/export to download segment membership for activation in adjacent channels (paid social audiences, direct mail). The export endpoint is built for scale and returns the full membership rather than a paginated trickle.

GET /lists to find the 'cart-abandoners' segment ID, then GET /lists/{list_id}/contacts/export to pull the full membership.

Profile Deduplication via Merge Jobs

When the same customer appears under two profiles (different emails, same person), POST /merge-profile schedules a merge job that consolidates them. GET /merge-profile lists running jobs and GET /merge-profile/{job_id} returns the status of a specific job. This is the recommended path over manual SQL fixups in the underlying data.

POST /merge-profile with two profile IDs, then poll GET /merge-profile/{job_id} until status is complete.

AI Agent Marketing Operations

An AI agent integrated through Jentic can ingest a CSV of new customers from a one-off campaign, push them via /push, monitor /push-errors, and then trigger a transactional welcome email - all without seeing the X-Ometria-Auth header. Jentic stores the credential and returns scoped operation handles only.

Search Jentic for 'push customers to ometria', load /push, ingest 500 records, then call /transactional-email/send to dispatch a welcome email to each.

Key Endpoints

34 endpoints — jentic publishes the only available openapi specification for ometria data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/push

Bulk-push records (customers, orders, products, events)

GET

/push-errors

List rejected records from recent pushes

GET

/lists/{list_id}/contacts/export

Export segment membership

POST

/merge-profile

Run a profile-merge job

POST

/transactional-email/send

Send a transactional email

GET

/unsubscribes

List unsubscribes for compliance

POST

/push

Bulk-push records (customers, orders, products, events)

GET

/push-errors

List rejected records from recent pushes

GET

/lists/{list_id}/contacts/export

Export segment membership

POST

/merge-profile

Run a profile-merge job

POST

/transactional-email/send

Send a transactional email

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Ometria Data API by hand means setting up its X-Ometria-Auth header, targeting the api.ometria.com/v2 host, and navigating 34 endpoints across data push, segment export, and transactional sends yourself. Through Jentic you install once, import Ometria from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Ometria puts the list id in the URL path (/lists/{list_id}/contacts/export), so a rule can pin your agent to exporting one list, and across the wider surface you limit it to the operations it needs, such as reading push errors or unsubscribes. You choose the operations it may call, so a data push or transactional send is not included unless you add it.

Credential isolation

Your Ometria API key is stored once, encrypted, by your own Jentic One instance and injected into the X-Ometria-Auth header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'push customers to Ometria' or 'export a segment', and Jentic returns the matching operation, often /push or /lists/{list_id}/contacts/export, with its full input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Ometria Data API through Jentic.

Why is there no official OpenAPI spec for Ometria Data API?

Ometria does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ometria Data API via structured tooling. It is validated against the live API and kept up to date. get started with Jentic One, the self-hosted execution layer.

What authentication does the Ometria Data API use?

Every request must include the X-Ometria-Auth header carrying an API key issued from the Ometria UI. Jentic stores this key encrypted in your Jentic One instance and injects it on each call, so agents never see the raw header.

Can I send transactional emails through the Ometria Data API?

Yes. POST /transactional-email/send dispatches a one-off transactional email using a template configured in Ometria. This is separate from the campaign system and is intended for receipts, password resets, and order confirmations.

What are the rate limits for the Ometria Data API?

Rate limits are not declared in the OpenAPI spec but Ometria recommends pushing data in batches of up to 1,000 records per /push call. Use /push-errors to detect rejections rather than retrying full batches blindly.

How do I dedupe two customer profiles through Jentic?

Search Jentic for 'merge ometria profiles', load POST /merge-profile, and pass the two profile IDs. Then poll GET /merge-profile/{job_id} to confirm completion.

Is the Ometria Data API rate-limited per endpoint?

The spec does not differentiate per-endpoint limits. The /push endpoint is built for bulk ingestion (preferred for high-volume writes) while individual /products/{id} and /orders/{id} reads are intended for low-frequency lookups.

Ometria Data API

Connect the Ometria Data API to your agent

Capabilities

Start building with Ometria Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs