Cloud Nekom NEKOM Orders API
49
AI ReadinessFoundational (D+)49/100
Community OpenAPI document · agent-readyE CommerceOrder ManagementapiKey48 EndpointsREST
Know of an official OpenAPI document?
Install Jentic One Beta
Connect the NEKOM Orders API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NEKOM Orders 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%2Fcloud.nekom.com%2Fcloud-nekom-com" | 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%2Fcloud.nekom.com%2Fcloud-nekom-com" | 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 NEKOM Orders API.
List and search orders by status, customer, invoice, or free text
Create direct, standard, and historical orders
Add, update, and cancel order positions
Attach, retrieve, and email order documents
Update delivery estimates, tours, and order status
Export orders to logistics and push status back to the shop
Use Cases
Patterns agents use NEKOM Orders API for, with concrete tasks.
★ Order status automation
Operations teams need orders to move through statuses without manual clicks. The NEKOM Orders API lets a system read orders by status and update each one, then push the new status back to the shop so the storefront stays in sync.
Find orders in a pending status, advance each to shipped, and send the status back to the shop
Customer service order lookup
Support agents answering order questions need a fast lookup across customer, invoice, and free text. The API's search and filter operations return matching orders with their positions and documents so an assistant can resolve a query in one pass.
Search orders for a customer, read the line items, and email the matching invoice document
Logistics and fulfillment export
Fulfillment depends on orders reaching the logistics provider accurately. The API exports an order to logistics, records tour assignments, and updates delivery estimates, keeping the warehouse and the customer aligned.
Export a confirmed order to logistics and set its delivery estimate and tour assignment
Key Endpoints
48 endpoints — the nekom orders api reads and manages orders inside the nekom order-management system.
METHOD
PATH
DESCRIPTION
GET
/api/v1/orders
Get orders by status code
POST
/api/v1/orders
Create a new order
GET
/api/v1/orders/search
Search orders by text
POST
/api/v1/orders/addposition
Add an order position
GET
/api/v1/orders/document
Get a document for an order
PUT
/api/v1/orders/status
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Hand-wiring NEKOM means managing its two header credentials and 48 order operations yourself. With Jentic One you install once, import the operations from the API Directory, and keep the client credentials in one place.
Permission scoping
Order resources are addressed by path parameters such as order UUID, so you can scope an agent to specific operations, for example letting it search and read orders while withholding create, cancel, and export.
Credential isolation
The clientuuid and Authorization token are stored encrypted by your own Jentic One instance and injected when a call runs, so neither value enters the agent's prompt, logs, or context.
Intent-based discovery
Agents locate the right order operation through Jentic's intent search, matching a request like finding a customer's recent orders to the matching NEKOM endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NEKOM Orders API through Jentic.
How does the NEKOM Orders API authenticate requests?
NEKOM expects two header credentials declared as API keys in its spec: a `clientuuid` that identifies your client and a token in the `Authorization` header for the interface user. Jentic One injects both at execution time.
Can I limit what my agent can do with the NEKOM Orders API?
Yes. You import only the operations an agent needs, so a reporting agent can be given read operations like order search while create, update, and export operations stay out of its reach.
Can the API create orders or only read them?
Both. Alongside the read and search operations it can create direct, standard, and historical orders and add or update their positions.
Does the API handle logistics and shipping?
It exports orders to a logistics provider and records tour assignments and delivery estimates, but the carrier movements themselves happen in the logistics system.
What formats does the NEKOM Orders API return?
Order data is returned as JSON, and documents such as invoices can be retrieved or emailed through the document operations.
GET STARTED