intelligent.pageDocs

Namshi

UAE fashion retailer inside the noon group: no separate Namshi seller API, so integration runs through noon or a buying relationship.

Namshi is an online fashion and lifestyle retailer serving the Gulf, founded in Dubai and long one of the region's best known apparel destinations. It now sits inside the noon group, which changes the integration question: the relevant seller surface is noon's, not a standalone Namshi developer portal. Namshi has historically operated closer to a retailer than a marketplace, buying inventory from brands and selling it on its own account, with brand partnerships layered on top. There is no public Namshi API.

At a glance

What it is

Namshi is a Gulf-focused fashion e-commerce business headquartered in Dubai, selling clothing, footwear, beauty and accessories across the United Arab Emirates and neighbouring markets including Saudi Arabia, Kuwait, Bahrain, Oman and Qatar. It was owned by Emaar before being acquired by noon, the regional e-commerce group backed by the Public Investment Fund and Mohamed Alabbar. The acquisition was announced in 2022. The exact completion date and consideration are not verified on this page, because no primary source could be fetched.

The commercial shape matters more than the corporate history. Namshi's traditional model is retail: a buying team purchases inventory from brands and distributors, Namshi owns the stock, sets the price, runs the merchandising and handles fulfilment and returns from its own warehouse. That is the opposite of a marketplace where a brand controls its own listing. Some Gulf fashion platforms also run consignment or marketplace lanes alongside the retail lane, and Namshi has partnered with brands in that way, but no published seller portal or self-serve signup exists under the Namshi name.

API access

No Namshi developer portal, API reference, SDK or Postman collection was found. namshi.com itself did not respond to the fetcher within sixty seconds on 2026-09-21, on both the root and the /uae-en/ locale path, which is consistent with a geo-aware edge or a bot filter rather than an outage.

Every noon domain tried also timed out: sellerlab.noon.com, noon.com's sell-on-noon page, noon.partners and docs.noon.partners. So while noon does run a third-party seller programme, nothing about its credential model, endpoints or documentation can be stated here from a primary source, and nothing is asserted.

One usable signal survives the blocking. Unicommerce's published integrations catalogue lists Noon as a supported sales channel, which means an order management aggregator has a working credential path into the noon seller side. Namshi is not listed separately in that catalogue. Taken together, the practical reading for 2026-09-21 is:

  • Selling on the group programmatically means selling on noon, through a noon seller account.
  • Supplying Namshi means a buying relationship: purchase orders, inbound to a Namshi warehouse, goods receipt and payment terms, handled by email and document exchange.
  • Nobody should build against a "Namshi API" without first asking noon whether Namshi is now served by the same seller account and the same interface.
Note

Confirm whether a brand's Namshi assortment is visible and manageable from the noon seller account, or whether the two catalogues are still operated separately. This is the single question that determines whether Namshi needs its own connector at all, and it cannot be answered from public pages.

Authentication

Not published under the Namshi brand. For a noon seller account, the credential model could not be verified because the documentation domains timed out. No token endpoint, header, scope or lifetime is claimed here.

Objects we can read

Nothing documented under the Namshi brand.

If Namshi supply is a buying relationship, the vendor-visible object set is the usual one: a purchase order document, an inbound appointment, a goods receipt against ordered quantity, and a payment advice reconciling invoices less deductions. None of it is published, none of it is structured, and it will arrive by email.

If the assortment sits inside a noon seller account, the readable set is whatever noon exposes to sellers: orders, order items, listings, inventory, returns and settlement reports. Field names are not reproduced here because noon's documentation could not be read.

Writing back: listings, price and stock

Not available under the Namshi brand. In a retail relationship the brand has no listing to write, no price control beyond the negotiated cost price and no stock to publish, because Namshi holds the inventory it bought. Content, imagery and new SKU introduction go through the buying and content teams.

Where a noon seller account exists, listing, price and stock updates are a noon capability, and that is where the write path should be designed and documented. See the noon connector page rather than this one.

Webhooks and notifications

None published under the Namshi brand. For a buying relationship the notification channel is a mailbox, and the design is a document parser watching it. For a noon seller account, use noon's mechanism.

Rate limits and pagination

Not applicable under the Namshi brand.

Mapping to the unified model

Two shapes, depending on which relationship exists.

Retail supply relationship:

Marketplace lane through noon: use the noon mapping, set channel to noon and carry the storefront that sold the unit as an attribute rather than as a separate channel, so revenue is not counted twice.

Gaps and open questions

  • namshi.com and all noon domains timed out for the fetcher, so this page has no primary source from either company. Confidence is low and a browser-based re-fetch is needed.
  • Whether Namshi assortment is now managed from a noon seller account, or still separately, is the key unresolved question.
  • Whether Namshi runs a consignment or marketplace lane for brands, and on what terms, is unverified.
  • The completion date and consideration of the noon acquisition are unverified here.
  • Currency and entity handling across the Gulf markets, which affects orders.currency and channel_account_id, is unverified.
  • Web search was unavailable for this page, so no news coverage was reviewed.

Sources