Documentation of Opencart Rest Admin Api

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

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey140 EndpointsREST

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.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Documentation of Opencart Rest Admin Api, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Documentation of Opencart Rest Admin Api 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 MAXsystem. 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The OpenCart admin secret key is stored encrypted in the Jentic MAXsystem vault and injected into the X-Oc-Restadmin-Id header at request time. Agents receive operation-scoped access only — the secret never enters prompt context or logs.

Intent-based discovery

Agents search by intent (e.g., 'create an OpenCart product' or 'list orders from the last week') and Jentic returns the matching operation across the 140-endpoint surface with its parameter schema, so the agent does not need to navigate the OpenCart admin docs.

Time to first call

Direct OpenCart Admin integration: 2-3 days for header auth, response parsing, and error handling across 140 endpoints. Through Jentic: under an hour to set up the search-load-execute pattern.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify API

Hosted commerce platform with a similar admin surface and broader app ecosystem.

Choose Shopify when the merchant runs on Shopify rather than self-hosted OpenCart, or when hosted SLAs and apps matter more than self-hosting.

Alternative

Magento API

Adobe Commerce/Magento admin REST API for enterprise self-hosted commerce.

Choose Magento when the store runs on Adobe Commerce/Magento and needs comparable catalogue, customer, and order operations.

Complementary

Stripe API

Payment processing alongside catalogue and order management.

Choose Stripe when the agent needs to handle payments or refunds — OpenCart only configures payment methods, it does not process card transactions.

FAQs

Specific to using Documentation of Opencart Rest Admin Api 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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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 MAXsystem. 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.