canonical: https://jentic.com/apis/nocnoc.com/nocnoc # nocnoc API Jentic publishes the only available OpenAPI specification for nocnoc API, keeping it validated and agent-ready. The nocnoc API is a marketplace integration surface for sellers managing products, orders, and package fulfillment across nocnoc's Latin America cross-border e-commerce network. Sellers can list and update product catalogs, look up product detail by SKU, retrieve order data, cancel orders, and fetch package records for shipping coordination. The API uses an x-api-key header for authentication on every endpoint. ## For AI agents Manage cross-border e-commerce listings, orders, and package fulfillment on the nocnoc marketplace through 8 product, order, and package endpoints. ## Scope Does not handle storefront hosting, payment capture, or buyer-side checkout - use for nocnoc seller-side product, order, and package operations only. ## Capabilities - List and create marketplace product listings via /products - Fetch a single product record by SKU through `/products/sku/{sku}` - Retrieve marketplace orders with filters via /orders - Cancel an order with `/orders/{order_id}/cancellation` - Pull package records for shipping coordination through /packages - Authenticate every request with the x-api-key header tied to the seller account ## Use cases ### Catalog Sync Sellers maintain a master product catalog in their PIM or ERP and need it mirrored to nocnoc for cross-border listings. The /products endpoint supports list and create operations, and `/products/sku/{sku}` resolves a single record for delta updates. A nightly sync can detect new SKUs in the source system and POST them to nocnoc without manual entry. Example prompt: Diff the local catalog against /products, POST new SKUs to /products, and call `/products/sku/{sku}` to verify each listing ### Order Fulfillment Workflow Operations teams need to pull marketplace orders, route them to a warehouse, and surface package data for carrier handoff. The /orders endpoint exposes the order list and detail, /packages returns the package records once fulfilment is created, and `/orders/{order_id}/cancellation` handles cancellations triggered by stock or fraud signals. This lets a single agent run the full marketplace fulfilment loop. Example prompt: Poll /orders for new orders, push each to the warehouse, and call /packages to retrieve the shipping record once the order ships ### Cross-Border Marketplace Reconciliation Finance and operations teams reconciling cross-border sales need a structured order and package feed tied to seller SKUs. The nocnoc API exposes orders and the connected packages, which can be joined against shipping carrier confirmations and finance entries. This produces an auditable trail from listing to settlement. Example prompt: Pull /orders for the previous billing period, then /packages for each order_id and join against the carrier feed to reconcile shipments ### AI Agent Marketplace Operator An operations agent monitoring multiple marketplaces can use Jentic to call nocnoc operations alongside other channels without writing per-channel auth code. A search for 'list my nocnoc orders' surfaces /orders; the agent loads the schema and Jentic injects the x-api-key. The same agent can call `/orders/{order_id}/cancellation` when an inventory alert fires. Example prompt: Use Jentic to call /orders, detect a stockout, then call `/orders/{order_id}/cancellation` for affected order ids ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/products` | List seller product listings on nocnoc | | POST | `/products` | Create a new marketplace product listing | | GET | `/products/sku/{sku}` | Look up a single product by SKU | | GET | `/orders` | Retrieve marketplace orders for the seller | | POST | `/orders/{order_id}/cancellation` | Cancel a specific order | | GET | `/packages` | List package records connected to fulfilled orders | ## Key resources - **Products** — List, create, and look up marketplace product listings - **Orders** — Retrieve and cancel marketplace orders - **Packages** — Fetch package records connected to fulfilled orders ## Why Jentic - **Setup:** Wiring nocnoc by hand means adding its API key, building requests against its versioned host (https://api.nocnoc.com/api/v2), and handling its seller-side payloads yourself. Through Jentic you install once, import the nocnoc API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** nocnoc carries the order id in the URL path (`/orders/{order_id}/cancellation`) but routes most work through the request body, so scope by operation: limit the agent to the operations it needs, such as listing products or reading orders, and leave out cancelling an order or creating products unless you add them. You choose the operations it may call. - **Credential handling:** Your nocnoc 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. - **Discovery method:** Agents search Jentic by intent such as 'list seller products' or 'read incoming orders', and Jentic returns the matching nocnoc operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify Admin API** — Shopify is a hosted storefront platform with a much broader admin surface for products, orders, and inventory. - **ShipEngine API** — ShipEngine provides multi-carrier label generation and tracking that complements nocnoc's package records. - **Amazon Selling Partner API** — Amazon SP-API offers comparable seller operations on the Amazon marketplace. ## FAQ ### Why is there no official OpenAPI spec for nocnoc API? nocnoc does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call nocnoc API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the nocnoc API use? nocnoc uses an apiKey passed as the x-api-key header on every request. Through Jentic the key is held encrypted in the vault and injected at call time so it never enters the agent context. ### Can I look up a specific product on nocnoc by SKU? Yes. Call GET `/products/sku/{sku}` with the seller SKU. The response returns the matching product record, including marketplace listing metadata. ### What are the rate limits for the nocnoc API? The OpenAPI spec does not declare specific rate limits. nocnoc enforces seller-tier quotas - Jentic surfaces 429 responses with backoff so retries are paced correctly. ### How do I cancel a nocnoc order through Jentic? Run pip install jentic, search Jentic for 'cancel a nocnoc order', load the `/orders/{order_id}/cancellation` operation, supply the order_id, and execute. Jentic injects the x-api-key automatically. ### Can I retrieve package data for a fulfilled nocnoc order? Yes. The /packages endpoint exposes package records connected to orders so a fulfilment workflow can pull shipping handoff data without scraping carrier portals. ### Can I limit what my agent is allowed to do with the nocnoc API? Yes. Because Jentic One is self-hosted, your own rules decide which nocnoc operations and credentials the agent may use, and you scope it by operation. You can allow read-only work such as listing products via GET /products or reading orders via GET /orders while leaving out write actions like creating a listing with POST /products or cancelling an order with POST `/orders/{order_id}/cancellation.` Only the operations you grant are callable, and the API key stays in your own instance rather than the agent context.