DOCSEARCHbyAlgolia
Submit Docs

Noon Partner API Reference

website·Indexed 31 days ago

https://noon-docs.noonpartners.dev

API documentation for Noon partners, covering catalog management (SKU generation, barcode imports), content services (product upserts, category attributes), event notifications via HTTPS webhooks, and FBPI shipment and order management. Includes technical specifications and implementation examples in Python, Java, and C#.

Tokens
174.6K
Snippets
456
Records
697
Agent score
59%

What's inside Noon

  1. Overview of the noon API Platform

    The noon API Platform provides a unified, production-grade interface for interacting with noon's marketplace services. It allows developers to manage catalogs, orders, fulfillment, and event notifications through a single consistent interface rather than integrating with multiple internal services separately. The platform is designed for high availability, scalability, and secure access, supporting use cases ranging from simple automations to large-scale ERP/OMS integrations.

  2. Overview of Fulfilled by Partner Integration (FBPI)

    Fulfilled by Partner Integration (FBPI) is noon's API-driven fulfillment model where sellers fulfill customer orders directly from their own warehouses. Unlike FBN, inventory is not stored in noon's warehouses. noon routes orders to the seller, who then handles picking, packing, and shipping.

  3. Overview of Event Notifications delivery logs querying

    Event Notifications records every delivery attempt (payload, destination, timestamp, and status) in a delivery log. Users can search these logs using the query editor by constructing expressions following the pattern: field → operator → value.

  5. Overview of noon Developer Portal capabilities

    The noon Developer Portal is a browser-based management tool for developers to maintain their integrations without writing code. Key capabilities include:

    • Event Notifications: Create and manage webhook destinations, subscribe to event types, and review delivery attempts (logs and analytics).
    • Debugging Sessions: Capture and inspect the request and response of live API calls for a specific service.
    • Rate Limit Monitoring: Track usage against limits per marketplace, service, and endpoint to prevent throttling.
    • Support Cases: Raise, attach evidence to, and track support cases to resolution.

  6. Overview of the API User Service for Credential Management

    The API User Service allows developers to programmatically create and remove RSA key pair credentials for service accounts without using the noon Partner portal. These credentials (private keys) are used to sign JWT tokens, which are then exchanged for session cookies to authenticate API requests. Each service account can have up to 5 active keys simultaneously.

  7. Overview of the noon Pricing API

    The Pricing API allows sellers and ERP integrators to programmatically retrieve and update selling prices, Manufacturer's Suggested Retail Price (MSRP), and active status for SKUs in bulk across the UAE (AE), Saudi Arabia (SA), and Egypt (EG) markets. It is designed for high-volume synchronization and managing large catalogs.

  8. Overview of the noon Offer API

    The Offer API provides read-only access to the live status, current price, stock level, and visibility of products across all markets where a seller operates on noon. It is primarily used by sellers and ERP integrators to monitor catalog health, diagnose non-live listings, and verify that pricing or stock updates have propagated. Because it is read-only, updates to prices or stock must be handled via the Pricing API or Stock API respectively.

  9. Overview of the noon Content Integration API

    The Content Integration API is designed for sellers and integrators managing large catalogs across noon's bilingual storefronts. It enables the programmatic creation, updating, and monitoring of product listings. Key capabilities include discovering category codes, submitting single-SKU or multi-size product groups, managing bilingual content (English and Arabic), and tracking QC approval and image review status to identify why listings may not be live.

  10. Overview of the noon Stock API

    The Stock API allows sellers and ERP integrators to programmatically manage the available quantity of SKUs on noon. It ensures that customers only see fulfillable inventory by pushing changes from the seller's internal systems to noon. This is particularly useful for large or fast-moving catalogs where manual updates in the Partner Portal are impractical.

  11. Understand the noon product onboarding lifecycle

    Getting a product live on noon involves a repetitive 'create-monitor-fix' loop. A product only becomes active when all 'go-live gates' are passed for a specific language. QC (Quality Control) review only begins after content completeness reaches 100%. Images are reviewed independently and in parallel. Developers should expect at least two cycles of submission and polling on the first attempt.

    Go-live Gates:

    • Content Completeness: 100% of mandatory attributes must be present and valid (statuses[].content.completeness = "100%").
    • Image: At least one image must be REVIEW_STATUS_VALID and VISIBILITY_STATUS_VISIBLE.
    • QC: Status must be QC_STATUS_APPROVED (statuses[].qc.status).
    • Quota: Must have an available product slot in the monthly allowance (checked during UpsertProduct).

  12. Understand the noon API Platform domain organization

    The noon API Platform is structured into functional domains. Each domain serves as a logical grouping of related APIs that support specific segments of noon's commerce and fulfillment workflows. Developers should navigate to individual domain pages to find specific endpoint details, request requirements, and response formats.