Skip to content
QuickshipTechnologies

SoftwareUAE7 min read

Noon API Integration: What UAE Sellers Need to Know

Noon API integration for UAE sellers: what the API covers, how login and FBPI orders work, how Amazon.ae SP-API compares, and whether to build or buy.

By · Published

Looking for the software itself? See our custom software development Dubai.

A noon API integration lets your own system send stock, prices and catalog data to noon and receive orders back, without anyone retyping them in Seller Lab. noon documents one API Platform for catalogs, orders, fulfillment and event notifications, and you log in with a service account. Amazon.ae works differently, through its own Selling Partner API (SP-API), so plan two integrations, not one.

This guide is for UAE sellers who want orders and stock to move between their systems and the marketplaces on their own.

What does a noon API integration cover?

noon says its API Platform is one interface for catalogs, orders, fulfillment and event notifications. You don't connect to each internal noon service separately. Sellers, integrators and developers use it for catalog updates, inventory sync, pricing and order handling.

The API reference lists these areas:

Area What it is for
Authentication Service account login, OAuth for integrators
Catalog and Content Creating and updating product data
Offer, Pricing, Global Product & Pricing Your price and offer on each listing
Stock Reading and updating inventory between noon and your system
Event Notifications Real-time updates through webhooks
FBPI Fulfilled by Partner Integration, for sellers who run their own warehouse
FBPO Fulfilled by Purchase Order
Warehouse Platform Warehouse setup
Returns and Reports Return data and exports

You won't need every area on day one. Most UAE sellers start with three: Stock, Offer and Event Notifications for orders.

How does login work for the noon API?

A service account logs in with an API JWT token, and noon creates a session. The login endpoint is POST /public/v1/api/login, as shown in the noon authentication reference.

One integrator write-up describes the seller-side setup like this. Treat it as a guide and check it against the current docs, because screens change:

  1. Sign in at access.noon.partners with your Seller Lab account.
  2. Open API Users.
  3. Create a service account. That write-up says noon allows one per project.
  4. Download the JSON key and keep it private.
  5. Give the API user a role, such as Project Owner. Reports and exports depend on the role.

If you are a software provider building for many sellers, there is a better route. noon's OAuth flow lets a provider get a seller's consent and automatically create a service account with access to that seller's project. The seller must have a noon Partner account.

Treat the JSON key like a bank password. Don't email it, and don't paste it into a shared chat.

Is there a public noon developer portal and sandbox?

Yes, there is a public portal. noon publishes docs at noon-docs.noonpartners.dev and runs a Developer Portal at developer.noon.partners. The portal overview lists webhook destinations, rate limit analytics, debugging sessions and support cases.

You may see blog posts saying noon has no public developer portal or published rate limits. That conflicts with noon's own site, so go by the official docs. Still, confirm sandbox access and FBPI onboarding with your noon account manager. Those steps run through noon, not through a public form.

How does an FBPI order flow through the API?

In Fulfilled by Partner Integration, you run your own warehouse and stay connected to noon by API for stock updates, order processing and shipment management. noon's FBPI FAQs say you need either a system that can integrate with noon by API, or a third-party integrator that already supports FBPI. FBPI covers noon and Namshi.

The FBPI guide gives the order flow:

  1. noon receives the customer order and shares the details with the integrator by API.
  2. The integrator asks the seller to confirm the item is available.
  3. The seller confirms to the integrator.
  4. The integrator creates the shipment and sends the shipment details to noon by API.

Onboarding means building against noon's staging environment first, using the provided API docs.

What should your system do at each step?

  • Step 1. Receive the event, then fetch the full order. One integrator write-up says the webhook arrives first and your system then pulls the order.
  • Step 2 and 3. Check live stock for that SKU and warehouse. If you can't fill one item, say so before a shipment exists.
  • Step 4. Create the shipment and send the details back. One integrator article says that after creating shipments by API, sellers still had to create a manifest in Seller Lab before pickup was scheduled. It's a few months old, so check the current docs.

Why does stock not show on noon?

noon's help page says missing stock usually points to a misalignment. Typical causes are inventory pushed to the wrong warehouse, or API errors. It tells you to check your logs. Warehouses are created in Seller Lab or through your account manager, so keep the warehouse code in your system exactly as noon has it.

What about the Amazon.ae SP-API?

Amazon.ae uses the Selling Partner API (SP-API), and it has its own access rules. Amazon's seller documentation says only Professional selling accounts can access Developer Central and SP-API. You must be the primary account user to create a developer profile. The path is Seller Central, then Apps and Services, then Develop Apps. Check Seller Central for the current steps before you plan a build.

Here is how the two compare at a planning level:

Question noon Amazon.ae
API name noon API Platform Selling Partner API (SP-API)
Who sets it up Seller with a noon Partner account, or an integrator via OAuth Primary user on a Professional account
Where you start Seller Lab and the noon Developer Portal Seller Central, Develop Apps
Order alerts Event Notifications by webhook Check Amazon's current docs
Own-warehouse model FBPI Check Amazon's current docs

Don't copy one integration's logic into the other. Names, statuses and error formats differ.

Should you build it, buy a connector or use a module?

You have three realistic options. The right one depends on how unusual your process is.

Option Good when Watch out for
Build direct to noon and SP-API You have odd rules, such as bundles or custom ERP fields You own the upkeep every time an API changes
Ready-made connector You want standard catalog, stock and order sync Feature gaps. One connector lists repricing, merchant returns and noon express as not supported
A module that already syncs stock You sell on Amazon, noon and Shopify and want one stock record Check it covers your exact workflow

Quickship's Inventory module handles multi-warehouse stock with Amazon, noon and Shopify sync. If your process needs something it doesn't do, Quickship also builds custom software on quote. We are a technology company. We build the software, and you or your fulfilment partner handle the goods.

What mistakes break marketplace integrations?

These are the ones we would check first:

  • Updating stock by product name instead of Partner SKU and warehouse. noon's Stock API works by Partner SKU plus warehouse, according to one integrator write-up.
  • Pushing stock to the wrong warehouse code. The orders then fail or the stock never shows.
  • Ignoring errors. noon's changelog mentions a standard error format. Log every error, and alert someone.
  • No stock buffer. Say a Dubai seller has 3 units left and two marketplaces both show 3. One order on each means one cancellation. Keep one master count and push it to both.
  • Open access to customer data. Order data holds names, phone numbers and addresses. Treat it as personal data under UAE PDPL and limit who can see it. Ask your legal adviser for the details.
  • Shared keys. One JSON key used by five people means nobody knows who changed what.

What should you prepare before you start?

Use this short checklist:

  1. Confirm your noon Partner account and Amazon.ae Professional account are active.
  2. Decide which system is the master for stock, and which is the master for prices.
  3. List every warehouse with its exact noon warehouse code.
  4. Clean your Partner SKUs. One SKU should mean one product.
  5. Ask your noon account manager about staging access and FBPI onboarding.
  6. Decide who gets alerts when an order fails to sync.

Start with stock and orders. Add pricing and returns after those run cleanly for a few weeks.

Frequently asked questions

Do I need a developer to connect my system to noon?

For a direct noon API integration, yes. Someone has to build against the API docs, test on staging and handle errors. If you only need standard catalog, stock and order sync, a ready-made connector or an integrator that already supports FBPI can mean no custom code on your side.

Can one system handle both noon and Amazon.ae?

Yes, but the two platforms use different APIs, login methods and data formats. A good setup keeps one internal stock record per SKU and warehouse, then has a separate adapter for each marketplace. That way a change on one platform does not break the other.

Where do I find the noon API documentation?

noon publishes it at noon-docs.noonpartners.dev, and the Developer Portal is at developer.noon.partners. You need a noon Partner account to use features such as webhook destinations. Confirm sandbox access and FBPI onboarding with your noon account manager.

How do I know if stock is not syncing to noon?

Start with your own API logs. noon's help centre says missing stock usually points to a misalignment, such as inventory pushed to the wrong warehouse, or API errors. Check the warehouse code and Partner SKU first.

Sources

  1. noon API Platform: getting started
  2. noon API docs: Authentication (service account login)
  3. noon API docs: Getting credentials with OAuth
  4. noon Developer Portal overview
  5. noon help centre: Fulfilled by Partner Integration (FBPI) FAQs
  6. noon help centre: FBPI comprehensive guide

Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 15 November 2026. Check the official source before acting on it.

Software Development

Custom software for the processes off the shelf tools do not fit.

Get a quote

Related guides

Instant quote