Noon Seller API and Integration Options in 2026: FBPI, JUMP, CSV Imports and What noon Does Not Publish

"noon seller API documentation" is a common search and a frustrating one, because the honest answer is that noon does not run a public developer portal the way Amazon's Selling Partner API does. There is an API platform, there is a documented integration model, and there are several perfectly good ways to automate a noon store without writing a line of code. What there is not, as of September 2026, is an open reference you can read before you have an account.

This page sets out exactly what noon exposes, who genuinely needs it, what the alternatives are, and where noon publishes nothing at all. It is written for a seller based in the UAE or KSA running enough volume to consider automation, and for an Indian brand on the cross-border Global Store lane, whose integration options are different and narrower.

What does noon actually expose?

Who actually needs an API integration?

Very few of the sellers who ask us for one. A rough decision rule from running these accounts:

• Under about 30 orders a day, one warehouse: you need CSV discipline, not an API. Seller Lab's price and stock imports plus FBN for your fast movers will do it, and the money you would spend on integration is better spent on advertising.
• Multi-channel, one stock pool: this is the real trigger. If the same units are sellable on noon, Amazon.ae, your own store and a physical shop, oversell risk is what justifies integration, not order volume.
• You already run an ERP or WMS: integrate, because double entry into Seller Lab will decay and your stock file will drift.
• Cross-border from India: you are on FBP, and noon's own answer is OMS integrators such as Unicommerce or Increff rather than a direct build. Take that route; the Global importers handle price and HS codes.
• You have a tech team and want the webhook path: noon allows it. Its own guidance is that most sellers use a third-party integrator, "especially when they do not have internal technical resources", but "it's not mandatory" and you can act as your own integrator. Talk to your account manager for webhook details.

How does FBPI actually work?

FBPI is noon's model for sellers who run their own warehouse but want the order flow automated. Three parties: noon receives the customer order, an integrator sits between noon and you for stock updates and shipment creation, and you fulfil from your warehouse. The order flow noon publishes:

1. noon receives the order and pushes the details to the integrator by API.
2. The integrator passes them to you to confirm the item is available and fulfillable.
3. You acknowledge; the integrator creates the shipment and returns the shipment details to noon by API.
4. You pack in noon packing material, print the shipment label and apply it.
5. noon collects according to the handover preference you set when you created the warehouse.

The prerequisites are short: a store on Seller Lab, catalogue content created, and an Integration Warehouse. Creating the warehouse is a Seller Lab flow, after which you "Choose Integrator" and pick either a noon-partnered integrator from a dropdown or the webhook option for a direct build.

Several constraints in noon's FAQ are worth knowing before you plan:

• You cannot convert an existing warehouse. An FBN or FBP warehouse cannot become FBPI. You create a new, dedicated warehouse code, and each code is tied to one fulfilment model with no switching. You may run several models on one account, each with its own code.
• One integration serves noon and Namshi. noon states FBPI supports both marketplaces, so orders from either flow through the same integration. For a fashion seller that is a material saving.
• No fixed minimum volume, though noon assesses your setup during onboarding and expects moderate to high volume with real warehouse control.
• Multiple FBPI warehouses are allowed across locations or regions.
• Domestic and cross-border are both supported, configured per warehouse at onboarding.
• Onboarding is a test programme, not a switch. You get staging credentials and endpoints, integrate against staging, then complete test scenarios for inventory updates, order processing and shipment handling before live orders are enabled.

What about JUMP?

JUMP is the least-known of these and the most useful for a specific seller: someone who already sells on their own storefront in Saudi Arabia and wants noon's logistics behind it. noon describes it as "a platform that acts as a bridge between your external store, such as the SALLA, and the noon fulfillment services". Onboarding is three steps: create the JUMP account at welcome.noon.partners using your noon credentials, link your legal entity and sign the contract through the authorised signatory, then authorise the SALLA connection.

Two service levels: Fulfilled by Jump, where noon handles the full fulfilment and logistics cycle including storage in its warehouses, and Delivered by Jump, where you keep warehousing and fulfilment and use noon only for shipping. Choosing Fulfilled by Jump adds two steps: build the JUMP catalogue with name, description, image, a SKU matching your SALLA SKU and a barcode, and transfer stock into the noon warehouse by creating an ASN.

What can you do with CSV alone?

More than most sellers realise, and this is where we start with almost every account. Seller Lab's import types cover price update, price range, FBP stock update, SKU rename, SKU delete, bulk SKU creation, barcode mapping and multi-category bulk listing. The published rules that matter:

• A 30% cap per import file. noon does not allow price changes of more than 30% in a single import. Above that you split it into two passes, or noon verifies it with you by email first. Plan sale pricing around that, especially before Yellow Friday.
• Price guardrails. noon sets an x_noon_price_min and max to stop catastrophic mispricing, and you can set your own seller price min and max so a bad file simply does not go live. Use both. To price below noon's floor you email seller@noon.com with the SKUs.
• Format discipline. xlsx or CSV, never xls. Dates are YYYY-DD-MM, which is unusual enough to catch people out. Save as Unicode Text on Windows or UTF-16 on Mac. Under 500 rows, paste straight into the Paste tab and skip file encoding entirely.
• Barcodes are a separate import (Barcode, then Partner Barcode Map), and every size and colour variant needs its own unique barcode. Different SKUs sharing a barcode causes reconciliation problems. Once assigned, a barcode cannot be deleted, only superseded. If you have no manufacturer barcode you can create an alphanumeric one up to 16 characters, or see GTIN for the GS1 route.
• Indian sellers use the Global importers: 8-digit HS codes through the Global Product Importer (mandatory), and USD prices through the Global Price Importer with country_code AE or SA, where price_usd is the selling price excluding VAT and GST.

A worked cost comparison

Assumptions: 1,500 SKUs, 60 orders a day, one UAE warehouse, an operations person at 6,000 AED a month (about Rs 141,000). Integrator fees are illustrative because noon publishes none.

At 60 orders a day the CSV route is usually still the right answer for a single channel. It stops being right the moment a second channel shares the same stock. Note also that noon's Fees and Revenue Calculator, which models FBN against FBP per unit, lives inside Seller Lab and is not exposed as an API, so margin modelling stays a manual or spreadsheet job either way; our noon seller fees calculator and noon seller fees explained cover that ground.

Choosing an integration route without guessing

The sequence that works: get the CSV cadence clean first, because a bad import discipline will produce a bad integration. Then decide whether your problem is volume or multi-channel stock. Only then talk to noon about FBPI, and ask for the partnered-integrator list and staging access in the same conversation, because that is where the schedule risk lives. If you want someone to run the import cadence, hold the integrator to account and reconcile what actually synced against what should have, that is part of our noon account management work. We run the same discipline on Amazon and the Indian marketplaces, so a shared stock pool across markets is a familiar problem rather than a new one. See the service page for scope, and selling on noon from India if you are on the cross-border lane.

FAQ

Does noon have a public seller API documentation page? No. noon describes an API Platform covering catalogue, orders, fulfilment and event notifications, and links to a document from its help centre, but there is no open developer portal, no published authentication scheme and no published rate limits. Access and staging credentials come through a support ticket and FBPI onboarding.

What is FBPI and how is it different from FBP? FBP is you fulfilling from your own warehouse using Seller Lab. FBPI is the same thing with the order, stock and shipment flow automated by API through an integrator or your own webhook. You cannot convert an FBP warehouse to FBPI; you create a new warehouse code dedicated to it.

Do I have to use a third-party integrator? No. noon says most sellers do, especially without internal technical resources, but you can act as your own integrator using the webhook option and noon's documentation. Ask your account manager for the webhook details.

Does one integration cover Namshi too? Yes. noon states FBPI supports both noon and Namshi, so once integrated your system can serve orders from either platform through the same integration.

Is JUMP available in the UAE? Not as of September 2026. noon's own article says JUMP is only available for KSA sellers for now, and it connects external storefronts such as SALLA to noon's fulfilment. Support runs through jumpsupport@noon.com.

What is the fastest automation that needs no development? Seller Lab's CSV imports. Price update, stock update and barcode mapping cover most day-to-day work, with a 30% cap on price movement per file, YYYY-DD-MM dates, xlsx or CSV only, and a paste tab for anything under 500 rows.