For Agents
Programmatically create or update product, register webhooks. Covers 2 operations with apiKey authentication.
Use for: I need to or update product, I want to register webhooks, Get the current status of Storeplum API resources, List all records from Storeplum API
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Storeplum API for managing products, webhooks, and e-commerce operations. The API exposes 2 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Storeplum 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%2Fstoreplum.in%2Fstoreplum" | shStep 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%2Fstoreplum.in%2Fstoreplum" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Storeplum API.
Create or update product
Register webhooks
Integrate Storeplum API into automated workflows
Query and filter Storeplum API records by parameters
Monitor Storeplum API operational status and events
Patterns agents use Storeplum API for, with concrete tasks.
★ E-Commerce Operations
Use the Storeplum API to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including create or update product, register webhooks.
Call POST /integration/action/product/save to create or update product
Data Retrieval and Monitoring
Query Storeplum API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Storeplum API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Storeplum API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create or update product', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — storeplum api for managing products, webhooks, and e-commerce operations.
METHOD
PATH
DESCRIPTION
/integration/action/product/save
Create or update product
/integration/subscribe
Register webhooks
/integration/action/product/save
Create or update product
/integration/subscribe
Register webhooks
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Storeplum API by hand means sending its key in the X-SP-INTEGRATION header on every call to api.storeplum.in and shaping the product and subscribe payloads yourself. Through Jentic you install once, import the Storeplum API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Storeplum takes the product and subscriber details in the request body rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as saving a product or adding a subscriber. Only the operations you add are available to the agent.
Credential isolation
Your Storeplum API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create or update a product' or 'add a newsletter subscriber', and Jentic returns the matching Storeplum API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Storeplum API through Jentic.
What authentication does the Storeplum API use?
The Storeplum API uses an API key passed in the `X-SP-INTEGRATION` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create or update product with the Storeplum API?
Yes. Use the POST /integration/action/product/save endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Storeplum API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create or update product through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create or update product'. Jentic returns the matching Storeplum API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Storeplum API have?
The Storeplum API exposes 2 endpoints covering integration operations.
GET STARTED