Install Jentic One Beta

Connect the Documentation of Opencart Rest Admin Api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Documentation of Opencart Rest Admin 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%2Fopencart-api.com%2Fopencart-admin-api" | 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%2Fopencart-api.com%2Fopencart-admin-api" | 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 Documentation of Opencart Rest Admin Api.

Create, update, and delete products, including variants, options, and image assets

Manage category trees with parent, child, level, and extended pagination operations

Maintain manufacturer records and attach manufacturer images for catalogue branding

Create and update customers, customer groups, and addresses for B2B segmentation

GET STARTED

Start building with Documentation of Opencart Rest Admin Api

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Documentation of Opencart Rest Admin Api for, with concrete tasks.

★ Headless Catalogue Sync

Sync products, categories, manufacturers, and stock levels between OpenCart and an external PIM, ERP, or marketplace channel. The /products, /categories, and /manufacturers endpoints provide the CRUD surface needed to keep the OpenCart admin database aligned with a single source of truth, removing the need to maintain custom database scripts.

POST /products with title, model, price, and category_ids, then PUT /products/{id} once the marketplace returns its external SKU.

Order Fulfilment Automation

Pull new orders into a 3PL or warehouse management system, push back tracking updates, and progress order statuses through the OpenCart admin lifecycle. The order endpoints expose order, order_status, and history operations to drive multi-step fulfilment without operators logging into the OpenCart admin UI.

Poll the orders list filtered by status 'Processing', POST tracking number into the order history, and update order_status to 'Shipped'.

Merchandising and Personalisation

Drive personalised storefront sections by reading the latest, featured, and bestseller product lists from the admin API and combining them with customer-group context. The /products/latest, /products/featured, and merchandising endpoints expose the same lists used by the OpenCart admin so external storefronts and apps can render consistent recommendations.

GET /products/latest/limit/12 and render the response as a 'New Arrivals' section on a custom storefront.

AI Agent Storefront Operations

Through Jentic, an AI agent can manage an OpenCart store administratively without learning the OpenCart admin UI or the 140-endpoint surface. The agent searches for the right operation, loads its schema, and submits the request with the X-Oc-Restadmin-Id header injected from your Jentic One instance. This unlocks agent-driven catalogue maintenance, price changes, and stock adjustments for OpenCart merchants.

Through Jentic, search for 'create an OpenCart product', load POST /products, and execute it with the supplied product payload.

Key Endpoints

140 endpoints — jentic publishes the only available openapi specification for documentation of opencart rest admin api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/categories

List categories

POST

/categories

Create a category

DELETE

/categories

Delete categories

GET

/categories/{id}

Read a category

POST

/manufacturers

Create a manufacturer

POST

/manufacturers/{id}/images

Upload a manufacturer image

GET

/manufacturers/limit/{limit}/page/{page}

Paginate manufacturers

GET

/categories

List categories

POST

/categories

Create a category

DELETE

/categories

Delete categories

GET

/categories/{id}

Read a category

POST

/manufacturers

Create a manufacturer

POST

/manufacturers/{id}/images

Upload a manufacturer image

GET

/manufacturers/limit/{limit}/page/{page}

Paginate manufacturers

Why Jentic?

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

Setup

Wiring the OpenCart REST Admin API by hand means managing the admin secret key, setting the X-Oc-Restadmin-Id header on every call, and navigating a 140-endpoint admin surface yourself. Through Jentic you install once, import the OpenCart Admin API from the API Directory, store the secret key once, and your agent calls it.

Permission scoping

The API puts the resource id in the URL path (/categories/{id}, /manufacturers/{id}/images), so a rule can pin your agent to per-resource work: it can read a category or add a manufacturer image. You choose the operations it may call, so category deletion is not included unless you add it.

Credential isolation

Your OpenCart admin secret key is stored once, encrypted, by your own Jentic One instance and injected into the X-Oc-Restadmin-Id header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an OpenCart product' or 'list categories', and Jentic returns the matching operation across the admin surface with its parameter schema so the agent calls the right endpoint without navigating the OpenCart admin docs.

FAQs

Specific to using Documentation of Opencart Rest Admin Api through Jentic.

Why is there no official OpenAPI spec for Documentation of Opencart Rest Admin API?

The OpenCart REST Admin extension publishes its documentation in HTML rather than as an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OpenCart over 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 OpenCart Admin API use?

The spec defines an API key scheme called ApiKeyAuth where the secret key is sent in the X-Oc-Restadmin-Id HTTP header on every request. Through Jentic, the secret key is stored encrypted in your Jentic One instance and injected into the header at request time, so the OpenCart admin secret never enters the agent's context.

Can I create products with images and options through this API?

Yes. POST /products creates the base product record, and the related image and option endpoints (such as POST /manufacturers/{id}/images for brand imagery and the product option endpoints listed in the spec) attach assets and variant attributes. The full catalogue surface is exposed across roughly 140 endpoints covering products, categories, manufacturers, attributes, and options.

What are the rate limits for the OpenCart Admin API?

The OpenCart REST Admin extension does not advertise hard rate limits in the spec - limits depend on the underlying OpenCart hosting and any web application firewall in front of it. For production loads, batch CRUD calls and avoid tight loops on /products/limit/{limit}/page/{page} pagination to prevent saturating the storefront database.

How do I list categories through Jentic?

Search Jentic for 'list OpenCart categories', load GET /categories or GET /categories/level/{level}, and execute it with the X-Oc-Restadmin-Id header injected from your Jentic One instance. Jentic returns the parsed response so an agent can iterate over categories without writing HTTP client code.

Is the OpenCart Admin API free?

OpenCart itself is open source and free to self-host, but the REST Admin extension that exposes this 140-endpoint surface is a paid commercial extension distributed via opencart-api.com. Once installed on a self-hosted OpenCart store, there are no per-call charges from OpenCart itself.

Can I limit what my agent is allowed to do with the OpenCart Admin API?

Yes. Because you run Jentic One yourself, your own rules decide which of the roughly 140 OpenCart admin operations the agent may call and which credentials it may use. Since the API puts the resource id in the URL path, such as /categories/{id} and /manufacturers/{id}/images, you can pin the agent to per-resource work like reading a category or adding a manufacturer image. Destructive operations such as DELETE /categories are excluded unless you explicitly grant them.

Opencart Api Documentation of Opencart Rest Admin Api

Name: Documentation of Opencart Rest Admin Api
Brand: Documentation of Opencart Rest Admin API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceStorefrontapiKey140 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage an OpenCart 3.x store administratively over REST - products, categories, customers, orders, options, and store-wide settings - using a per-store secret key.

Use for: Create a new product with options, images, and category assignments, Update inventory quantity for a specific product variant, List all categories at a given level for a storefront menu, Search for orders placed in the last 7 days by status

Not supported: Does not handle storefront rendering, payment capture, or shipping label generation - use for OpenCart 3.x administrative catalogue, customer, and order operations only.

Jentic publishes the only available OpenAPI specification for Documentation of Opencart Rest Admin API, keeping it validated and agent-ready. The OpenCart REST Admin API exposes the administrative surface of an OpenCart 3.x storefront for headless and integration use cases. It covers the full catalogue (products, categories, manufacturers, options, attributes), customer and customer-group management, order processing, payment and shipping methods, store and language settings, and merchandising lists such as latest, featured, and bestseller products. Authentication is performed with a per-store secret key passed in the X-Oc-Restadmin-Id header.

Jentic One on Github View OpenAPI Document

Connect the Documentation of Opencart Rest Admin Api to your agent

Capabilities

Start building with Documentation of Opencart Rest Admin Api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Opencart Api Documentation of Opencart Rest Admin Api