BeezUP Merchant API

Name: BeezUP Merchant API
Brand: BeezUP Merchant API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey248 EndpointsREST

For Agents

Manage multi-channel product catalogs, configure marketplace exports, and harvest orders from connected marketplaces. Supports rule-based optimisation and cross-channel performance reporting.

Install Jentic One Beta

Connect the BeezUP Merchant API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BeezUP Merchant 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 BeezUP Merchant API.

Import product catalogs and schedule automatic catalog refreshes

Configure category and column mappings between catalogs and marketplace channels

Harvest orders from connected marketplaces and synchronise their status

GET STARTED

Start building with BeezUP Merchant API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BeezUP Merchant API for, with concrete tasks.

★ Multi-Marketplace Order Sync

Pull orders from every connected marketplace into a single normalised stream so a back office or fulfilment system can process them uniformly. The BeezUP order endpoints expose harvest triggers, light and full order lists, and per-order status transitions, allowing a merchant to reconcile and ship without logging into each marketplace. Initial integration with order list, harvest, and status update endpoints typically takes 2 to 3 days for a working pipeline.

Call POST /orders/v3/harvest to fetch new orders, then iterate the response and POST /orders/v3/{marketplaceTechnicalCode}/{accountId}/{beezUPOrderId}/changeOrderState to mark each as shipped

Catalog Import Automation

Automate periodic ingestion of a master product feed into BeezUP so downstream channel exports always reflect the latest pricing and stock. The catalog endpoints support manual import triggers, scheduled auto-imports, importation process status tracking, and replication of channel-specific overrides. A typical setup with a daily import cron, status polling, and error handling takes around a day to wire up.

POST a new catalog file, then GET the importation process endpoint until status is Done and surface any row-level validation errors

Channel Performance Reporting

Pull analytics breakdowns by day, channel, category, and product to identify which marketplace listings drive revenue and which need price or content adjustments. The reporting endpoints expose aggregated metrics that can drive bid rules, exclusion filters, or stock allocation decisions. Building an internal dashboard against these endpoints is typically a 1 to 2 day effort.

Query the channel reporting endpoint for the last 30 days and return the top 10 SKUs by clicks per channel

AI Agent for E-Commerce Operations

An AI agent uses Jentic to discover and call BeezUP endpoints that monitor catalog imports, surface order anomalies, and trigger reharvests when a marketplace lags. The agent searches Jentic for the relevant operation, loads its schema, and executes against BeezUP without browsing the 248-endpoint surface manually. Integration via Jentic takes under an hour because credential storage, schema loading, and execution are handled by the SDK.

Search Jentic for 'harvest marketplace orders' and execute the returned BeezUP operation on a customer account, then summarise new orders by marketplace

Key Endpoints

248 endpoints — the beezup merchant api gives multi-channel sellers programmatic access to product catalog imports, marketplace channel configuration, order harvesting across marketplaces, and performance reporting.

METHOD

PATH

DESCRIPTION

POST

/orders/v3/harvest

Trigger order harvesting across connected marketplaces

POST

/orders/v3/list/full

List orders with full detail and filters

GET

/orders/v3/{marketplaceTechnicalCode}/{accountId}/{beezUPOrderId}

Retrieve a specific marketplace order

GET

/orders/v3/{marketplaceTechnicalCode}/{accountId}/{beezUPOrderId}/history

Get the change history for an order

POST

/orders/v3/batches/changeOrders

Apply a batch of order state changes

GET

/orders/v3/status

Check the current order management service status

POST

/orders/v3/harvest

Trigger order harvesting across connected marketplaces

POST

/orders/v3/list/full

List orders with full detail and filters

GET

/orders/v3/{marketplaceTechnicalCode}/{accountId}/{beezUPOrderId}

Retrieve a specific marketplace order

GET

/orders/v3/{marketplaceTechnicalCode}/{accountId}/{beezUPOrderId}/history

Get the change history for an order

POST

/orders/v3/batches/changeOrders

Apply a batch of order state changes

Why Jentic?

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

Credential isolation

BeezUP subscription keys are stored encrypted in the Jentic vault. Agents receive scoped execution rights — the Ocp-Apim-Subscription-Key header is injected at execution time and never appears in the agent's context window.

Intent-based discovery

Agents search Jentic by intent such as 'harvest marketplace orders' or 'import product catalog' and Jentic returns the matching BeezUP operation with its parameter schema, removing the need to read the 248-endpoint reference manually.

Time to first call

Direct BeezUP integration: 2 to 5 days to handle auth, catalog state polling, and order harvesting flows. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using BeezUP Merchant API through Jentic.

What authentication does the BeezUP Merchant API use?

The BeezUP Merchant API uses an API key passed in the Ocp-Apim-Subscription-Key request header. Public endpoints under /v2/public are unauthenticated, while user endpoints require the token visible at https://go.beezup.com/Account/MyAccount. When called via Jentic, the subscription key is stored encrypted in the Jentic vault and never enters the agent context.

Can I harvest orders from multiple marketplaces with one call?

Yes. POST /orders/v3/harvest triggers harvesting across every marketplace connected to the account, and POST /orders/v3/list/full returns the resulting normalised orders. Per-marketplace variants such as /orders/v3/{marketplaceTechnicalCode}/{accountId}/harvest let you scope to a single channel when needed.

What are the rate limits for the BeezUP Merchant API?

BeezUP limits the REST API to 100 calls per minute per account. Bulk operations such as batch order state changes via /orders/v3/batches/changeOrders should be preferred over per-order loops to stay within the budget.

How do I import a product catalog through Jentic?

Run pip install jentic, then search Jentic for 'import product catalog beezup'. Jentic returns the catalog import operation, the agent loads its input schema, and executes with the feed URL and store identifier. Poll the importation process endpoint until status is Done before triggering channel exports.

Is the BeezUP Merchant API free to use?

Access to the API requires an active BeezUP merchant subscription; the public registration and login endpoints under /v2/public are open but the catalog, channel, order, and reporting endpoints require an authenticated account on a paid plan. Pricing tiers are available at https://www.beezup.com/.

Can I update marketplace order statuses in bulk?

Yes. POST /orders/v3/batches/changeOrders accepts a batch of state transitions, and POST /orders/v3/batches/changeOrders/{changeOrderType} scopes the batch to a specific transition such as marking shipped or cancelled. This is the recommended approach for fulfilment integrations to avoid hitting the 100 calls per minute limit.

BeezUP Merchant API

Connect the BeezUP Merchant API to your agent

Capabilities

Start building with BeezUP Merchant API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs