SOS Inventory API
✓ Official Vendor SpecE CommerceInventoryoauth2161 EndpointsREST
For Agents
Programmatically create item, list items. Covers 161 operations with oauth2 authentication.
Use for: I need to item, I want to items, Search for item, Find all item
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
SOS Inventory is a cloud-based inventory management system that provides APIs for managing inventory, orders, customers, vendors, and more. The API exposes 161 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the SOS Inventory API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SOS Inventory 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.
1
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%2Fsosinventory.com%2Fsosinventory" | sh2
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%2Fsosinventory.com%2Fsosinventory" | 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.
Capabilities
What an agent can do with SOS Inventory API.
Create item
List items
Get item
Update item
Delete item
Use Cases
Patterns agents use SOS Inventory API for, with concrete tasks.
★ E-Commerce Operations
Use the SOS Inventory API to perform e commerce operations programmatically. The API provides 161 endpoints covering core functionality including create item, list items, get item.
Call POST /api/v2/item to create item
Automated API Management
Automate API operations by combining multiple SOS Inventory API endpoints. Agents can list items and then get item in a single workflow.
Call GET /api/v2/item to list items, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SOS Inventory 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 oauth2 tokens manually.
Search Jentic for 'create item', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
161 endpoints — sos inventory is a cloud-based inventory management system that provides apis for managing inventory, orders, customers, vendors, and more.
METHOD
PATH
DESCRIPTION
POST
/api/v2/item
Create item
GET
/api/v2/item
List items
GET
/api/v2/item/{id}
Get item
PUT
/api/v2/item/{id}
Update item
DELETE
/api/v2/item/{id}
Delete item
GET
/api/v2/item/{id}/bom
Get item bill of materials
POST
/api/v2/customer
Create customer
GET
/api/v2/customer
List customers
POST
/api/v2/item
Create item
GET
/api/v2/item
List items
GET
/api/v2/item/{id}
Get item
PUT
/api/v2/item/{id}
Update item
DELETE
/api/v2/item/{id}
Delete item
GET
/api/v2/item/{id}/bom
Get item bill of materials
POST
/api/v2/customer
Create customer
GET
/api/v2/customer
List customers
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SOS Inventory API by hand means running its OAuth2 flow, pointing at the api.sosinventory.com host, and managing token refresh across more than a hundred and fifty item and customer operations yourself. Through Jentic you install once, import the SOS Inventory API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The SOS Inventory API puts resource ids in the URL path (/api/v2/item/{id}, /api/v2/item/{id}/bom), so a rule can pin your agent to one item: it can read and update that item and nothing else. You choose the operations it may call, so destructive ones like deleting an item are not included unless you add them.
Credential isolation
Your SOS Inventory credential 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 an item' or 'look up a customer', and Jentic returns the matching SOS Inventory API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using SOS Inventory API through Jentic.
What authentication does the SOS Inventory API use?
The SOS Inventory API uses OAuth 2.0 for authorization. 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 item with the SOS Inventory API?
Yes. Use the POST /api/v2/item endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SOS Inventory 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 item through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create item'. Jentic returns the matching SOS Inventory API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SOS Inventory API have?
The SOS Inventory API exposes 161 endpoints covering API operations.
Can I limit what my agent is allowed to do with the SOS Inventory API?
Yes. Jentic One is self-hosted by you, so your own rules decide which SOS Inventory operations and credentials the agent may use. Because the API puts resource ids in the URL path, such as /api/v2/item/{id} and /api/v2/item/{id}/bom, a rule can pin the agent to a single item so it can read and update that item and nothing else. You also choose which operations are exposed, so destructive calls like DELETE /api/v2/item/{id} stay off limits unless you explicitly add them.
GET STARTED