Jumpseller API

Name: Jumpseller API
Brand: Jumpseller API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontbasic, apiKey, oauth2165 EndpointsREST

For Agents

Run a Jumpseller storefront from code: create and update products, fulfil orders, register webhooks, and install JSApps across 165 REST endpoints.

Install Jentic One Beta

Connect the Jumpseller API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jumpseller 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Jumpseller API.

Create and update products including options and category assignments through /products.json and /products/{id}/options.json

Filter products by status or category and count them server-side via /products/status/{status}.json and /products/category/{category_id}.json

Search the product catalogue and paginate results up to 100 per page with /products/search.json

GET STARTED

Start building with Jumpseller API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Jumpseller API for, with concrete tasks.

★ Catalog Sync From PIM to Storefront

Brands managing product data in a PIM or spreadsheet need their Jumpseller catalog to mirror it. A nightly job uses POST /products.json to add new SKUs, PUT /products/{id}.json to update price and stock, and DELETE /products/{id}.json to retire discontinued lines. With 800 requests per minute as the headline limit, a 5,000-product catalog can sync in under 10 minutes.

For each row in the PIM export, call PUT /products/{id}.json to update the price and stock fields, respecting Jumpseller's 20 requests per second rate limit.

Order Webhook Pipeline

Operations teams want every new order to trigger downstream automations such as ERP entry, label printing, and customer SMS. POST /hooks.json registers a webhook for the order-created event pointing at the team's intake URL. Jumpseller then pushes JSON callbacks for every order, replacing manual CSV exports.

Call POST /hooks.json with event 'order_created' and url 'https://ops.example.com/jumpseller/orders' to start streaming new-order events.

Storefront Customisation via JSApps

Agencies deploying customised storefronts use JSApps to inject vetted JavaScript without editing themes directly. POST /jsapps.json creates the app entry and returns a code; GET /jsapps/{code}.json verifies installation. This lets the agency push fixes across many merchant stores in minutes.

Create a JSApp via POST /jsapps.json with name 'cart-recovery-banner' and the bundled JS source, then call GET /jsapps/{code}.json to confirm it is active.

Agent-Driven Catalog Edits

An AI merchandising assistant can update prices, statuses, and category placements through Jentic. The agent searches 'update a product', loads PUT /products/{id}.json, and executes the call with the merchant's auth held in Jentic's vault. This pushes everyday catalog tweaks behind an LLM without exposing the merchant's API token.

Through Jentic, search 'update a product', load PUT /products/{id}.json, and execute with id 4321 and a 10% price reduction on price.

Key Endpoints

165 endpoints — the jumpseller api powers programmatic management of online stores hosted on jumpseller.

METHOD

PATH

DESCRIPTION

GET

/products.json

Retrieve all products, paginated

POST

/products.json

Create a new product

PUT

/products/{id}.json

Update an existing product

GET

/products/search.json

Search products by query

GET

/products/category/{category_id}.json

List products in a category

POST

/hooks.json

Create a webhook for a store event

POST

/jsapps.json

Create a JSApp to inject storefront JavaScript

GET

/store/info.json

Retrieve store metadata

GET

/products.json

Retrieve all products, paginated

POST

/products.json

Create a new product

PUT

/products/{id}.json

Update an existing product

GET

/products/search.json

Search products by query

GET

/products/category/{category_id}.json

List products in a category

Why Jentic?

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

Credential isolation

Jumpseller login plus auth token (or OAuth 2 access tokens) are held in Jentic's vault. Agents execute against /products.json and /hooks.json using scoped session access without ever seeing the raw 32-character token.

Intent-based discovery

Agents search by intent (e.g. 'update a product price' or 'register an order webhook') and Jentic returns the matching Jumpseller operation with its input schema, so the agent skips browsing the 165-endpoint reference.

Time to first call

Direct Jumpseller integration: 3-5 days to wire auth, pagination, hooks, and rate-limit handling across the catalog endpoints. Through Jentic: under 1 hour to search, load schema, and execute the first product update.

FAQs

Specific to using Jumpseller API through Jentic.

What authentication does the Jumpseller API use?

The Jumpseller API supports HTTP Basic auth with a login and 32-character auth token (recommended), deprecated login/authtoken query-string parameters, and OAuth 2 for Jumpseller Apps. Through Jentic, credentials are stored in the encrypted vault and passed at execution time.

Can I create and update products with the Jumpseller API?

Yes. POST /products.json creates a product, PUT /products/{id}.json updates name, price, and other fields, and DELETE /products/{id}.json removes it. Product options are managed via /products/{id}/options.json.

What are the rate limits for the Jumpseller API?

Jumpseller enforces 800 requests per minute and 20 requests per second, scoped per IP and store. Limit headroom is exposed via response headers Jumpseller-PerMinuteRateLimit-Remaining and Jumpseller-PerSecondRateLimit-Remaining, and persistent abuse triggers a temporary ban with a Jumpseller-BannedByRateLimit-Reset header.

How do I register a webhook with the Jumpseller API through Jentic?

Search Jentic for 'register a webhook on jumpseller', load POST /hooks.json, and execute with the event name and target URL. Jentic resolves the merchant's stored credentials and returns the created hook's id.

How does pagination work on Jumpseller list endpoints?

List endpoints return 50 objects per page by default with a maximum of 100 via the limit query parameter. Use page=2, page=3 and so on to walk through results until an empty response is returned.

Can I install JavaScript on the storefront via the API?

Yes. POST /jsapps.json creates a JSApp entry that injects JavaScript into the storefront. The returned code is then used with GET, DELETE, and PUT variants of /jsapps/{code}.json.

Jumpseller API

Connect the Jumpseller API to your agent

Capabilities

Start building with Jumpseller API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs