Omnia 2.0 API (0.0.7168)

This is the API powering Omnia 2.0 and Pricemonitor, containing operations that can also be used directly by customers from their own systems.

The Omnia 2.0 API is RESTful and provides access to the backend of Omnia 2.0 and Pricemonitor. It is used to manage products, offers, contracts, and more.

This API supports both public endpoints for customer integration and internal endpoints for platform management. All endpoints are authenticated using either Basic Authentication or JWT Bearer tokens.

Download OpenAPI description
Languages
Servers
Mock server

https://api-docs.omniaretail.dev/_mock/api/omnia/

Production API

https://api.patagona.de/

Overview

Overview, explanation and pointers to the API documentation.

Products Management

Operations to manage your products.

Operations

Price Recommendations

Operations to get price recommendations calculated by our system.

Operations

Offers

Operations to get and manage offers.

Operations

Feeds Management

Manage your data-feeds.

Operations

Logs Management

Operations to store log messages in the system.

You can integrate this API into your own system and publish integration logs to the system so that Omnia Retail can analyze them.

Operations

Company Management

Operations for managing company entities, including creation, retrieval, and contract management.

Operations

Orders Management

Operations for managing orders, including bulk order imports and order tracking.

Operations

Settings Management

Operations to manage the settings of contracts. Only a limited number of these operations are available to customers directly.

Operations

Tasks Management

Operations to view and manage the tasks running in the platform. Customers can only view tasks.

Operations

Strategies Management

Operations to view and manage pricing strategies.

Operations

Get all strategy versions metadata for contract

Request

Retrieves a list of metadata for all pricing strategy versions associated with a specific contract.

This endpoint provides version history information including creation dates, modification timestamps, and strategy metadata for tracking changes over time.

Security
BasicAuth or BearerAuth
Path
contractIdstringnon-emptyrequired

Unique identifier of the contract

Example: qbcxvb
curl -i -X GET \
  -u <username>:<password> \
  https://api-docs.omniaretail.dev/_mock/api/omnia/api/v3/vendor/contracts/qbcxvb/settings/pricingstrategies/history

Responses

List of metadata of all strategy versions

Bodyapplication/json
dataobject(com.patagona.pricemonitor.share.api.GetPricingStrategyHistoryResponse)required

Version history of all strategies

data.​historyArray of objects(com.patagona.pricemonitor.share.api.StrategyMetadataResponseV3)required

contains metadata of all strategies

data.​history[].​documentVersionintegerrequired

strategy version per contract

data.​history[].​documentVersionMessagestring

message provided by user when saving new strategy

data.​history[].​versionstringrequired

schema version of the strategy

data.​history[].​updateDatestring(date-time)

timestamp of last strategy update. It needs to be an option to ensure old strategies can be read.

data.​history[].​updatedBystring

user email of the account that updated the strategy. It needs to be an option to ensure old strategies can be read.

Response
application/json
{ "data": { "history": [] } }

Domains

Operations to view all supported domains.

A domain is an external datasource or website that contains information about offers for products for sale. Information like product characteristics and sales characterics like price, stock level and delivery times and costs.

Operations

Plugin Registration

Operations to view and manage registered plugins for system integration.

Operations