The Developer Portal now has a full documentation section — every feature walked through against the actual screens, with screenshots — and a Developer Portal entry in the site navigation to get you there.
\n\nIf you've never used one: a debugging session captures full request and response payloads — headers and bodies, per call — scoped to a single service and API user for a bounded window. It's the fastest way to see exactly what we received from you and exactly what we sent back. The page walks through setting one up.
\nThe portal itself is at developer.noon.partners.
", "url": "https://noon-docs.noonpartners.dev/changelog/developer-portal-documentation", "title": "A complete guide to the Developer Portal", "summary": "The Developer Portal now has a full documentation section — every feature walked through against the actual screens, with screenshots — and a Developer Portal entry in the site navigation to get you there.", "date_modified": "2026-08-19T00:00:00.000Z", "tags": [ "platform-update", "documentation", "major" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/portal-walkthrough-and-dark-mode", "content_html": "Signing in to the Developer Portal for the first time now starts with a short guided tour of the main areas, and the whole portal has a dark theme that follows your system setting.
\n\nFirst-time users are walked through where each part of the portal lives — rate limit analytics, event notification destinations, debugging sessions, support cases. It's skippable, and you can re-trigger it later from settings, which makes it a quick way to bring a new colleague up to speed.
\nThe portal follows your operating system's light or dark preference automatically. There's a manual toggle if you'd rather pin one, and that choice persists.
\nBoth are interface changes only — no API behaviour changed, and nothing you've built against the portal needs updating.
", "url": "https://noon-docs.noonpartners.dev/changelog/portal-walkthrough-and-dark-mode", "title": "Guided walkthrough and dark mode in the Developer Portal", "summary": "Signing in to the Developer Portal for the first time now starts with a short guided tour of the main areas, and the whole portal has a dark theme that follows your system setting.", "date_modified": "2026-08-10T00:00:00.000Z", "tags": [ "platform-update" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/seller-support-portal", "content_html": "The Seller Support Portal is live: raise a case with the API Platform team from inside the Developer Portal, track its status, and keep the whole exchange in one thread.
\n\nCases live under Support in the Developer Portal. From there you can open a new case, see everything you've raised, and open any one of them to read and continue the conversation. There's a full walkthrough in Support Cases.
\nA case moves through four states:
\n| Status | Meaning |
|---|---|
| Open | Raised, not yet picked up |
| Under Review | The platform team is working on it |
| Awaiting Partner Response | We've asked you something and are waiting |
| Closed | Resolved |
A case with no activity for 15 days closes automatically. If that happens and the problem hasn't gone away, open a new one and reference the old case.
\nThe more of this you provide up front, the fewer round trips:
\nIf failures are broad rather than specific to one call, the API health status page may already show the cause.
", "url": "https://noon-docs.noonpartners.dev/changelog/seller-support-portal", "title": "Support cases in the Developer Portal", "summary": "The Seller Support Portal is live: raise a case with the API Platform team from inside the Developer Portal, track its status, and keep the whole exchange in one thread.", "date_modified": "2026-07-27T00:00:00.000Z", "tags": [ "platform-update", "support", "major" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/copy-docs-as-markdown", "content_html": "Every documentation page — generated API reference included — can now be copied or downloaded as clean Markdown, ready to paste into an editor, a coding assistant, or your own internal docs.
\n\nEach page carries actions to copy its Markdown source or download it as a .md file. Endpoint pages also have a copy button on the method and path, so grabbing just the route doesn't mean selecting text by hand.
Markdown round-trips cleanly where a screenshot or a copy-paste from rendered HTML doesn't: tables stay tables, code blocks stay code blocks, and enum values survive intact.
\nThe site also publishes an llms.txt index, so tooling that understands that convention can discover the full documentation set on its own.
The API health status page is now public: current error rates for every endpoint we expose, grouped by service and broken out per marketplace.
\n\nEach service group rolls up to a single state:
\n| State | Meaning |
|---|---|
| Operational | No errors observed |
| Degraded | Some errors observed |
| Outage | Error rate above 10% |
A group shows as Outage if any endpoint under it is in outage, and Degraded if any endpoint is degraded.
\nThe page reads observed error rates directly — it isn't updated by hand, so it stays accurate during an incident without anyone remembering to flip a switch.
\nIt reflects current state only; there's no historical availability chart today. Establishing what happened during a window that has already passed still needs a conversation with us.
\nThe page is public and needs no login, so it's safe to link from your own runbooks and dashboards.
", "url": "https://noon-docs.noonpartners.dev/changelog/api-health-status-page", "title": "Live API health, per service and endpoint", "summary": "The API health status page is now public: current error rates for every endpoint we expose, grouped by service and broken out per marketplace.", "date_modified": "2026-07-06T00:00:00.000Z", "tags": [ "platform-update" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/list-return-references", "content_html": "A new Returns API lets you list return items and their barcode references for a given barcode across the merchants you operate, so your warehouse can identify an inbound return from the label alone.
\n\n| Endpoint | Summary |
|---|---|
POST /v1/return-references/list | ListReturnReferences — lists return items and their barcode references matching a barcode for the given merchants. |
This is the first endpoint on the Returns service — a single RPC, scoped to the merchants your credentials cover.
\nA returned parcel arrives at your facility carrying a barcode. Scan it, call ListReturnReferences, and you get the return items associated with it across all your partner merchants in one response — enough to route the parcel without a manual reconciliation step.
The endpoint and its full schema are in the Returns section of the API reference.
", "url": "https://noon-docs.noonpartners.dev/changelog/list-return-references", "title": "Return lookup by barcode", "summary": "A new Returns API lets you list return items and their barcode references for a given barcode across the merchants you operate, so your warehouse can identify an inbound return from the label alone.", "date_modified": "2026-06-29T10:00:00.000Z", "tags": [ "api-change", "returns" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/querying-event-notification-logs", "content_html": "There's now a guide for querying your event notification delivery logs, so you can confirm what we dispatched, when, and how your endpoint responded.
\n\nThe Querying logs guide covers the query editor in the Developer Portal: how to filter delivery attempts, what each field in a log record means, and how to read the results when a delivery failed.
\nThe guide is linked under Event Notifications in the docs sidebar, next to the event type references.
", "url": "https://noon-docs.noonpartners.dev/changelog/querying-event-notification-logs", "title": "A guide to querying event notification logs", "summary": "There's now a guide for querying your event notification delivery logs, so you can confirm what we dispatched, when, and how your endpoint responded.", "date_modified": "2026-06-29T09:00:00.000Z", "tags": [ "platform-update", "event-notifications", "documentation" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/global-product-and-content-apis", "content_html": "You can now browse the noon category tree, discover exactly which attributes a category expects, submit products against it, and read back their content — four endpoints, with a guide set that takes you from first call to go-live.
\n\n| Endpoint | Summary |
|---|---|
POST /v1/categories/list | ListCategories — lists all available product categories in the catalog. |
POST /v1/categories/attributes/list | ListCategoryAttributes — retrieves the attributes for a specified product category. |
POST /v1/product/upsert | UpsertProduct — creates or updates a product in the catalog. |
POST /v1/product/content/get | GetContent — retrieves content information for specified products. |
Five documents walk through a first integration end to end:
\nThe published reference is the source of truth for these endpoints: field and enum names match the service exactly, and rate limits render from the live specification.
", "url": "https://noon-docs.noonpartners.dev/changelog/global-product-and-content-apis", "title": "Content APIs for categories, attributes, and products", "summary": "You can now browse the noon category tree, discover exactly which attributes a category expects, submit products against it, and read back their content — four endpoints, with a guide set that takes you from first call to go-live.", "date_modified": "2026-06-19T10:00:00.000Z", "tags": [ "api-change", "content", "catalog", "major" ] }, { "id": "https://noon-docs.noonpartners.dev/changelog/catalog-sku-delete-and-barcode-import", "content_html": "The Catalog API now covers two operations you previously had to work around: deleting parent and child SKUs in batches, and loading barcodes in bulk from a file, a BigQuery table, or an inline list.
\n\n| Endpoint | Summary |
|---|---|
POST /v1/sku/parent/delete | ParentSkuDelete — deletes parent partner SKUs / ZSKU parents. This cascades: every associated child SKU is deleted with it. |
POST /v1/sku/child/delete | ChildSkuDelete — deletes individual partner SKUs / child ZSKUs. |
Both accept batches. Because parent deletion cascades, check what sits underneath a parent before you call it.
\n| Endpoint | Summary |
|---|---|
POST /v1/import/generate-import-signed-url | GenerateImportSignedUrl — returns a signed URL for uploading a file straight to GCS. Accepts csv, tsv, json, xlsx, xlsm, and parquet. |
POST /v1/import/barcode | CreateBarcodeImport — starts an import from exactly one source: file_url, bq_table, or inline items. |
GET /v1/import/status/{reference} | GetImportStatus — returns current status and a processing report: success and failure counts, progress, and completion timestamps. |
The usual flow is to call GenerateImportSignedUrl, upload your file to the URL it returns, pass that file_url to CreateBarcodeImport, then poll GetImportStatus with the returned reference until it completes. If your data already lives in BigQuery you can skip the upload and pass bq_table instead.
Full request and response shapes are in the Catalog section of the API reference.
", "url": "https://noon-docs.noonpartners.dev/changelog/catalog-sku-delete-and-barcode-import", "title": "Batch SKU deletion and bulk barcode import", "summary": "The Catalog API now covers two operations you previously had to work around: deleting parent and child SKUs in batches, and loading barcodes in bulk from a file, a BigQuery table, or an inline list.", "date_modified": "2026-06-19T09:00:00.000Z", "tags": [ "api-change", "catalog" ] } ] }