noon’s partner API is the official, documented way for software to read and change a noon seller account. It’s worth understanding even if you’ll never write a line of code, because it sets the limits for every integration, repricer or AI connector built on it. If a tool for noon claims to do something the API doesn’t cover, ask how.
The documentation is public at noon-docs.noonpartners.dev. The developer portal at developer.noon.partners sits behind the noon partner login. noon says the platform is for sellers automating catalogue, stock, pricing and order work, for service providers building tools, for system integrators connecting ERPs, and for developers in general.
What “API” means in seller terms
Seller Lab is a set of screens built for a person. The API is the same account exposed as a set of requests for a program. Instead of clicking Edit on a price, a program sends “set SKU X in Saudi Arabia to 149 SAR” in a fixed format, and noon replies with the result. There are no screens, so nothing can be misclicked. There are also no screens to stop a wrong instruction.
The parts that cover day-to-day selling
noon groups its APIs into 15 domains. These are the ones that map to what a seller does each week, and the ones our noon Seller MCP connector uses.
Prices. The Pricing API reads and updates the selling price, MSRP and active status of SKUs in the UAE, Saudi Arabia and Egypt. MSRP is the crossed-out “was” price customers see. noon says one request can update hundreds or thousands of SKUs, and that switching a SKU inactive in one country doesn’t touch the others.
Stock. The Stock service takes a list of warehouse code and partner SKU pairs and returns the quantity for each. noon’s fulfilment guide describes sellers pushing stock quantities through the same Stock API.
Offers. One call returns every offer for a partner SKU across countries: price, whether it’s active, net stock, live status, and an offer_issues list giving the reasons an offer isn’t visible. That list is the answer to “why isn’t my listing live?”.
Warehouses. The Warehouse Platform domain lists your warehouses and their codes, which the stock calls need.
Orders. These live in the fulfilment part of the API. Under FBPI, noon’s model for sellers who ship from their own warehouse, noon sends each new order to the seller’s webhook, and an order API returns the full details. Shipments and the AWB number go through a shipment API. noon’s FBPI page says manifests, processing times and holiday schedules are still handled in Seller Lab.
Product content and categories. The Content domain covers creating and updating catalogue content and listing categories. Category codes describe the full path to a product type, family then type then subtype. The Catalog domain has further endpoints for product data.
The rest is there if you need it: event notifications, returns, bulk reports, cross-border pricing and purchase-order fulfilment.
How access works
This part confuses most sellers, so here it is in order.
You need a noon partner account first. Your account lives in a project, which has a code; noon’s examples use the form PRJ12345.
Programs sign in as a service account, which noon calls an API user. It’s a separate identity from your own login. noon’s credentials guide gives the steps: open the Access App, go to API Users, click Add Service Account, fill in a display name and username, choose one or more roles, and click Add. A .json key file downloads to your computer. You can optionally limit the key to certain IP addresses and set an expiry; without an expiry the key is valid forever.
Some limits from the same page: each partner can create one service account from the seller portal, a service account can hold up to five keys, a session lasts 30 days, and deactivating a key takes effect immediately.
A program uses the key file to sign a short token, swaps it for a session, and sends requests with that session. Every request also needs a User-Agent header naming the app.
Rate limits apply per project and per endpoint, with a main window and a shorter burst window running at the same time. The offers and stock lookups, for example, allow 1,500 requests in 60 seconds. Go over and noon returns a 429 error until the window resets.
OAuth: how an app gets access without your key
Handing a .json key file to an outside company is a bad idea, and noon’s documentation says sellers should never share credentials with integrators manually. OAuth is the alternative.
An integrator registers with noon and gets OAuth client credentials. When you connect their app, you’re sent to noon’s consent page at oauth.noon.partners and approve access there. noon then creates a new service account in the integrator’s project with access to your project, and hands the credential to the integrator once; noon doesn’t store the private key. The sign-in code expires after 10 minutes and the access token after an hour, each usable once.
The result for you: no password shared and no key file emailed.
Using it without writing code
Calling the API yourself means a developer, a server to keep the key safe, code to sign requests and handle 429s, and any checks you want before a change goes live. For a seller with an ERP that’s a reasonable project. For a seller who wants to ask “which offers are live with zero stock?” it’s far too much.
That gap is why we built the connector. It’s an MCP server, a standard way for an assistant like Claude to use tools, sitting on top of noon’s partner API. You add https://mcp.thegrowthfolks.com/noon-mcp in Claude under Settings > Connectors > Add custom connector (newer versions of Claude label the menu Customize > Connectors), click Connect, sign in on noon’s page and approve. That’s the OAuth route above: noon issues a dedicated key for the connection, and we never see your password.
From then on you ask in words. Claude can read orders, warehouses, stock, prices, offer status, product content, categories and category attributes. It can change prices, stock, offers on or off, and product content. Each change is shown as a before-and-after preview and applied only when you confirm, with at most 50 items per change, price moves capped at 30% per step, zero prices and MSRP-below-price refused, and no delete tool at all. noon has no draft mode, so a confirmed change is live. Order data passes through to answer your question and isn’t stored.
To revoke it, disconnect the connector in Claude and remove its key under API Users in the noon partner portal. The connector works for the UAE, Saudi Arabia and Egypt. It’s free, built by The Growth Folks®, and not affiliated with or endorsed by noon; the connector terms cover responsibility for the changes you approve.
If you want prompts to start with, our walkthrough on running your noon store from Claude has five seller jobs written out. If you’re weighing the API against noon’s spreadsheet import for price changes, see the four ways to bulk update noon prices and stock. Questions about the connector: team@thegrowthfolks.com.
Questions people ask
Where do I get a noon API key?
In the noon partner portal's Access App, under API Users. noon's documentation says to click Add Service Account, give it a display name, username and role, and click Add. A .json key file downloads; it holds the private key, so keep it out of email and shared drives.
Can an app use my noon account without my password?
Yes, through noon's OAuth flow. You approve access on noon's own consent page, and noon creates a service account for that app with access to your account. noon's documentation says sellers should never manually share their credentials with an integrator.
Do I need a developer to use the noon partner API?
To call it directly, yes: requests are signed with a private key and sent from code. To use it without code, connect a tool built on it. The noon Seller MCP connector from The Growth Folks® lets you read and change your account by asking Claude, with a preview before every change.
What happens if I send too many requests to the noon API?
noon returns a 429 error and you wait for the window to reset. Limits apply per project and per endpoint, with a main window and a shorter burst window. noon recommends retrying with exponential backoff.
Sources
- noon API Documentation: noon API Platform introduction
- noon API Documentation: API domains overview
- noon API Documentation: Quick start
- noon API Documentation: Getting your credentials
- noon API Documentation: Getting credentials via OAuth
- noon API Documentation: Rate limits and usage
- noon API Documentation: Pricing API
- noon API Documentation: GetProductOffers
- noon API Documentation: What is FBPI?
