Agiliron API
★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey50 EndpointsREST
For Agents
Manage omni-channel commerce records: create and update sales orders, products, inventory, leads, and tickets across an Agiliron tenant.
Use for: Create a new sales order with three line items for an existing account, Update inventory levels after a warehouse stock count, List all leads created in the last 7 days, Find an account by company name across the Agiliron tenant
Not supported: Does not handle payment processing, shipping label generation, or storefront rendering — use for back-office order, inventory, and CRM operations inside Agiliron only.
Jentic publishes the only available OpenAPI specification for Agiliron API, keeping it validated and agent-ready. Agiliron is a SaaS platform for omni-channel commerce focused on retail, wholesale, distribution, and e-commerce operations. The 4.0 API exposes 50 endpoints providing full CRUD on leads, contacts, accounts, products, sales orders, purchase orders, quotes, potentials (opportunities), inventory, events, tasks, tickets, and notes. The base URL is tenant-scoped via a {company} placeholder so each customer hits their own subdomain at agiliron.net.
Install Jentic One Beta
Connect the Agiliron API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agiliron 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Agiliron API.
Create, read, update, and delete sales orders across channels via /SalesOrders/ endpoints
Manage product catalog and inventory levels via /Products/ and /Inventory/
Track sales pipeline through leads, contacts, accounts, and potentials (opportunities)
Open and resolve support tickets attached to customers via /Tickets/
Issue purchase orders to suppliers via /PurchaseOrders/
Generate sales quotes from product line items via /Quotes/
Use Cases
Patterns agents use Agiliron API for, with concrete tasks.
★ Order Sync Across Channels
Push orders from external channels (marketplace integrations, custom storefronts, EDI) into Agiliron as sales orders so inventory and fulfillment stay consolidated. The agent calls POST /SalesOrders/ per order and PUT /Products/ to deduct stock. Suited for omni-channel sellers who use Agiliron as the operational hub.
POST /SalesOrders/ for each marketplace order pulled from the channel API in the last hour, including line items and customer reference
Inventory and Replenishment
Read live stock levels from /Inventory/ and trigger /PurchaseOrders/ to suppliers when a SKU drops below its reorder point. The agent automates a previously manual cycle that a buyer used to run from spreadsheets. Useful for distribution businesses with hundreds of SKUs.
Read inventory levels for all products tagged 'fast-moving'; for any below threshold, POST /PurchaseOrders/ to the preferred supplier
Lead-to-Order Pipeline
Bring leads in from forms or marketing tools, convert qualified ones into accounts and contacts, then track the deal through /Potentials/ to /Quotes/ and finally /SalesOrders/. The agent stitches the conversion steps that the Agiliron UI requires manually. Suited for B2B distributors with consultative sales.
When a potential reaches stage 'Won', generate a quote, mark it accepted, and post a sales order using the same line items
Agent-Driven Operations Console
Run a Jentic-connected agent that answers operations questions ('how many sales orders shipped today?', 'which SKUs are below reorder?') by composing reads across /SalesOrders/, /Inventory/, and /Tickets/. The agent searches Jentic for each operation, loads the schemas, and aggregates results. This replaces a brittle internal dashboard with a conversational interface.
Answer 'which SKUs are out of stock and have open sales orders?' by joining /Inventory/ and /SalesOrders/ reads
Key Endpoints
50 endpoints — jentic publishes the only available openapi specification for agiliron api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/SalesOrders/
Create a sales order
GET
/SalesOrders/
List sales orders
GET
/Inventory/
Read current inventory levels
POST
/PurchaseOrders/
Create a purchase order
POST
/Leads/
Create a new lead
POST
/Quotes/
Create a sales quote
POST
/SalesOrders/
Create a sales order
GET
/SalesOrders/
List sales orders
GET
/Inventory/
Read current inventory levels
POST
/PurchaseOrders/
Create a purchase order
POST
/Leads/
Create a new lead
POST
/Quotes/
Create a sales quote
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Agiliron API keys are stored in the Jentic vault and injected as the apiKey header (or key query parameter) at execution time. The raw key never enters agent context.
Intent-based discovery
Agents search by intent (e.g. 'create a sales order' or 'check inventory') and Jentic returns the matching Agiliron operation with its input schema and the tenant-scoped base URL handled per connection.
Time to first call
Direct Agiliron integration: 1-2 days for tenant base URL handling, dual auth scheme support, and resource cross-references. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Payment processing for orders captured in Agiliron
Use Stripe to charge cards or handle recurring subscriptions tied to Agiliron sales orders or quotes.
FAQs
Specific to using Agiliron API through Jentic.
Why is there no official OpenAPI spec for Agiliron API?
Agiliron does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agiliron API via 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 Agiliron API use?
Agiliron supports two API key schemes: a 'key' query parameter and an 'apiKey' header. Most integrations use the header form. Through Jentic the key is held in the credential vault and injected at execution; the raw value never enters the agent's context.
Can I create a sales order with multiple line items in one Agiliron call?
Yes. POST /SalesOrders/ accepts a body with the order header and a line items array, so a multi-product order is created in a single request. Inventory deduction is handled by Agiliron based on the line items.
What are the rate limits for the Agiliron API?
Agiliron does not publish a fixed requests-per-second limit; the platform throttles abusive traffic at the network layer per tenant. Agents should retry-with-backoff on 429 responses and avoid running large bulk loads in a tight loop.
How do I read inventory levels through Jentic?
Use the Jentic search 'read agiliron inventory'. Jentic returns GET /Inventory/; load its schema, supply any product SKU or warehouse filter, and execute. The response lists current stock counts and warehouse locations.
Does the Agiliron base URL need a tenant value at call time?
Yes. The server URL is https://{company}.agiliron.net/agiliron/api-40 where {company} is your Agiliron subdomain. Set this once when configuring the integration; Jentic stores it as part of the connection profile so agents do not have to inject it on every call.
GET STARTED