Terminology
Definitions for all noon-specific terms used in this documentation.
| Term | Definition |
|---|---|
| Acknowledgment | The response sent by the seller's or integrator's system to noon after receiving an order notification. Confirms whether the order can be fulfilled and must be returned promptly — unacknowledged orders escalate to Pending and eventually Killed status. See also: Order Notification, Pending Order, Killed Order. |
| API Domain | A logical grouping of related noon Partner API endpoints that together support a specific commerce or fulfillment workflow (for example, Pricing, Offer, FBN Inbound). Each domain has its own base path and rate limits. |
| API Gateway | The unified entry point for all noon Partner API requests. All API calls are routed through noon-api-gateway.noon.partners. |
| API Key | A .json file downloaded when a service account is created. Contains the credentials (private key and metadata) needed to generate a JWT and authenticate with noon APIs. The file is shown only once — if lost, a new credential must be created. See also: Service Account, JWT. |
| ASN (Advanced Shipment Notice) | A record created through the FBN Inbound API before shipping inventory to a noon fulfillment center. Declares the expected contents and quantities of an inbound shipment. Must be created and sealed before a warehouse slot can be scheduled. |
| AWB (Airway Bill) | A unique tracking code assigned to each FBPI shipment before handover to noon logistics. noon provides AWBs via the Get noon Logistics AWBs API; they can be generated in bulk or one per shipment in real time. Every shipment must have an AWB mapped before pickup or drop-off. See also: Handover Type, Manifest / Manifestation. |
| Authorization Code | A short-lived, single-use token issued by noon's OAuth server after a seller grants consent to an integrator. The integrator must exchange it for an access token within 10 minutes. See also: OAuth 2.0. |
| Business Model | The operational context under which a product is sold on noon (noon, supermall, or Global). Each offer is scoped to one business model per country. The Offer API currently supports the noon business model. See also: Offer. |
| Channel Identifier | A unique identifier for a service account, returned as part of the credential object in OAuth token exchange responses. The API User Service accepts it in place of a user_code when managing or revoking credentials. See also: Service Account, OAuth 2.0. |
| Delivery Model | A configuration that defines how shipments move through noon's logistics network (for example, domestic, bulky, or cross-border). Set per warehouse during FBPI configuration. |
| Destination | An endpoint registered by a partner to receive event notifications. Each project supports up to 5 destinations; the currently supported type is HTTPS Webhook. See also: Event Notifications, Webhook. |
| Drop-off | A handover method in which the seller physically delivers prepared shipments to a noon facility. See also: Pickup, Handover Type. |
| Event Notifications | noon's system for pushing real-time business events to partner-configured endpoints. Delivery is automatic and retried on failure; partners do not need to poll APIs. See also: Destination, Webhook. |
| Exponential Backoff | A retry strategy in which the delay between attempts grows exponentially after each failure. Recommended when handling 429 Too Many Requests responses from the noon API Platform. |
| FBN (Fulfillment by noon) | noon's managed fulfillment model. Sellers ship inventory to noon fulfillment centers; noon handles storage, picking, packing, delivery, and returns end to end. See also: FBPI, ASN. |
| FBPI (Fulfilled by Partner Integration) | noon's API-driven fulfillment model in which sellers operate their own warehouses and connect to noon's systems via APIs and webhooks. Sellers or their integrators use the Stock, Pricing, and Shipment APIs to automate order fulfillment. See also: FBN, Integration Warehouse, Webhook. |
| Fixed Window Counter | The rate-limiting algorithm used by the noon API Platform. Counts requests within a fixed time window and rejects further requests with 429 once the limit is reached. Both a main window and a burst window are enforced simultaneously. See also: Exponential Backoff. |
| Handover Type | Indicates how a fulfilled shipment reaches noon: either pickup (noon's courier collects from the seller's warehouse) or drop-off (the seller delivers to a noon facility). See also: Pickup, Drop-off. |
| Integration Warehouse | A warehouse code registered specifically for the FBPI fulfillment model. Required before orders can flow and before stock, price, or shipment data can be synced via API. Must be activated to start receiving live orders. See also: Warehouse Activation, FBPI. |
| Integrator | A technical partner that connects one or more sellers' back-office systems to noon's APIs on the seller's behalf. Integrators obtain seller project access programmatically via OAuth and own the reliability of the webhook endpoint and data mapping. See also: Seller, OAuth 2.0. |
| JWT (JSON Web Token) | A signed token generated from a service account's private key. Submitted to noon's login endpoint and exchanged for a session cookie used to authenticate all subsequent API requests. See also: Service Account, Session Cookie. |
| Key ID | A unique identifier for an individual credential key within a service account. Used when revoking a specific key via the API User Service without deactivating other active keys on the same account. See also: Service Account, API Key. |
| Killed Order | An order that failed webhook delivery after all automatic retry attempts. Requires manual investigation through the FBPI Orders Dashboard. See also: Pending Order, Webhook, Acknowledgment. |
| Manifest / Manifestation | The process of creating a list of shipments ready for handover to noon. In FBPI, manifestation is performed manually through Seller Lab and is required before physical pickup or drop-off can occur. |
| MSRP (Manufacturer's Suggested Retail Price) | The recommended retail price for a product, set alongside the selling price in the Pricing API. Used for display and comparison purposes; not the actual transaction price. |
| OAuth 2.0 | The authorization framework used by integrators to obtain delegated access to seller projects without sellers manually creating or sharing credentials. noon's OAuth flow creates a service account in the integrator's project with scoped access to the seller's project. See also: Authorization Code, Channel Identifier. |
| Offer | A product listing on noon for a specific country and business model. Carries its own price, stock level, and live status. A single product can have multiple offers — one per country and business model combination. See also: PSKU, SKU, Business Model. |
| Order Notification | A real-time event pushed by noon to the seller's webhook when a customer places an order. Contains order details and requires an acknowledgment response. See also: Acknowledgment, Webhook, Pending Order. |
| Partial Success | A response pattern used by batch APIs where the HTTP status is 200 even if some items in the request failed. Each item in the response carries its own status field that must be checked individually. |
| Partner | Any organization or developer accessing the noon API Platform — including sellers, integrators, service providers, and developers. |
| Pending Order | An order that has been pushed to the webhook but not yet acknowledged by the integrator or seller system. Timely acknowledgment is required to prevent escalation to Killed status. See also: Acknowledgment, Killed Order. |
| Pickup | A handover method in which noon's courier collects prepared shipments directly from the seller's warehouse. See also: Drop-off, Handover Type. |
| Processing Time | The time a seller needs to prepare a shipment before noon's courier can collect it. Configured per warehouse as part of FBPI operational preferences. |
| Project Code | A unique identifier that scopes a set of API credentials, rate limit counters, and access permissions. Rate limits are enforced independently per project code; usage in one project does not affect another. See also: Service Account. |
| PSKU (Partner SKU) | The seller's own internal identifier for a product, as defined in their system. Used in Pricing and Offer API calls to reference products without using noon's internal SKU. See also: SKU, Offer. |
| Return to Origin (RTO) | The process by which undelivered or returned items are shipped back to the seller's warehouse. RTO preferences are configured per warehouse in FBPI. |
| Sandbox (Static Sandbox) | A test environment that mirrors the production API. Returns deterministic mock responses without side effects, data persistence, or calls to backend systems. The same auth flow, request validation, and rate limits apply as in production. |
| Seller | A merchant who lists and sells products on noon. In FBPI, the seller owns and operates the fulfillment warehouse. In FBN, the seller ships inventory to noon's fulfillment centers. See also: Integrator, Partner. |
| Seller Lab | noon's seller portal. Used for account setup, warehouse configuration, order monitoring, and manual operational steps such as manifestation. |
| Service Account | A non-human identity used by an application or system to authenticate API requests on behalf of a seller or partner. Credentials are stored in a .json key file. Each partner can create one service account with up to 5 active keys. See also: API Key, JWT, OAuth 2.0. |
| Session Cookie | An authentication token returned by noon's login endpoint after successfully exchanging a JWT. Must be included in all subsequent API requests. Sessions are valid for 30 days. See also: JWT, Service Account. |
| SKU | noon's internal catalog identifier for a product. Distinct from a seller's PSKU and returned in offer and catalog API responses. See also: PSKU, Offer. |
| Stock Sync | The automated process of sending inventory quantity updates from a seller's system to noon using the Stock API. Ensures that noon's listings reflect current stock availability. |
| Warehouse | A physical facility used to store and fulfill inventory. In FBPI, the warehouse is operated by the seller. In FBN, noon operates the fulfillment center. See also: Integration Warehouse, FBN, FBPI. |
| Warehouse Activation | The final configuration step that sets an FBPI Integration Warehouse to Active status, making it eligible to receive live orders. Must be completed after all operational preferences (processing time, handover type, delivery model, RTO) are configured. See also: Integration Warehouse. |
| Webhook | An HTTPS endpoint provided by the seller or integrator that noon uses to push real-time order notifications and events. Must be publicly reachable and respond promptly — slow or failed responses cause orders to become Pending or Killed. See also: Destination, Order Notification, Killed Order. |