Ominity Assistant

Your business, understood. Create content, uncover insights, and take action with AI. Discover the assistant

Content and commerce.
Through a clear interface.

Connect your frontend to pages, products, carts, and supported business operations on your Ominity instance.

Read the guideBrowse developers
Your frontend. A clear API.
Server-side integration
GET /api/v1/cms/pages

Instance → Content pages
title: A summer worth sharing
Response shape
Use your instance reference for the full schema.
01

The instance is the boundary

Requests go to your own instance under /api/v1. Authentication and authorization apply to the operation and the context in which it runs.

02

Read the records you need

Use GET /cms/pages for pages and GET /commerce/products for products. Compose the frontend around the returned data rather than exposing privileged integration credentials to the browser.

03

Work with cart items

POST /commerce/carts/{cartId}/items adds an item. PATCH /commerce/carts/{cartId}/items/{id} updates an item, and DELETE on the same item path removes it. Consult the instance’s reference for required payloads.

04

Make failure a first-class state

A request can fail because of authentication, permission, validation, or business rules. Present the result clearly and inspect the execution context when an action is rejected.

Common operations

Paths below are relative to /api/v1. Request schemas and authentication configuration belong to your instance reference.

GET/cms/pagesList pages
GET/commerce/productsList products
POST/commerce/carts/{cartId}/itemsAdd a cart item
PATCH/commerce/carts/{cartId}/items/{id}Update a cart item
DELETE/commerce/carts/{cartId}/items/{id}Remove a cart item

Keep exploring

Authentication & access Traceability & audit trails

Let’s talk about
your next project.

Three quick questions to start the conversation.

What’s your name?
Your email app opens a draft at the final step. Nothing is sent automatically.