Get started with Nasam MM-API

Nasam MM-API (Marketplace Management API) connects a brand's catalog, marketplace accounts, stock, orders, and reports. Requests go to https://backend.nasam.co/v1; this documentation lives at developer.nasam.co. The first useful call is a brand read: a brand ID identifies the scope for most later operations.

1. Get a key and find your brands

Contact Nasam sales for an API key. Send it in the key header from your server.

curl --get 'https://backend.nasam.co/v1/brands' \
  -H 'accept: application/json' \
  -H 'key: YOUR_API_KEY'

The brands operation returns a brands array and pagination. Each brand has a numeric id. Without limit, this operation returns the caller's full accessible set; supply page and limit when you want a bounded page. A brand selection always stays within your key's access.

This response excerpt keeps only the brand fields used in the next step; a full brand object has more fields:

{
  "brands": [{ "id": 20, "name": "Brand name" }],
  "pagination": { "page": 1, "limit": 1, "total": 1, "totalPages": 1 }
}

Use the returned id in the next call. The numbers and name above illustrate the response shape; use your own returned values.

2. Resolve the marketplace account

Use channel definitions to get channel IDs and regions. Then read a brand's connected accounts. A saleChannelId identifies a marketplace and region; an account id identifies that brand's particular connection. Many listing, inventory, order, and connection operations need the account or channel ID rather than a display name. The multi-channel API guide shows how those identities carry into later workflows.

For example, a brand can be connected to more than one channel. Read the account's status, fulfillmentModel, and inventoryScope before deciding which stock or shipment workflow applies. The sale channel API guide explains the relationship.

curl 'https://backend.nasam.co/v1/brands/20/sale-channels' \
  -H 'accept: application/json' \
  -H 'key: YOUR_API_KEY'

If a brand has no account for the marketplace you need, pause the integration for that brand and follow the connection workflow. A channel definition existing globally does not mean the brand has connected an account. Keep the selected brand ID, channel ID, and connected account ID as distinct values in your integration.

3. Read a brand's catalog

Replace 20 with a brand ID from the first response:

curl --get 'https://backend.nasam.co/v1/products' \
  --data-urlencode 'brandIds=20' \
  --data-urlencode 'page=1' \
  --data-urlencode 'limit=10' \
  -H 'accept: application/json' \
  -H 'key: YOUR_API_KEY'

The products operation returns products, categories, filterCounts, and pagination. Each product can include listings on the brand's connected sale-channel accounts. Use the brand ID from step 1; brandIds narrows the catalog to brands your key can access. Continue with catalog and listing review to understand product IDs, listing IDs, and channel account context before updating anything.

4. Choose the next resource

Your task	Start here
Match a marketplace catalog to Nasam products	Catalog and listing review
Find the stock source, forecast, or drift	Inventory and planning
Read orders and act on seller parcels	Orders and fulfillment
Read settled financial data	Profitability
Check whether channel captures are current	Sync Health
Investigate a brand's operational status	Brand Health

Use the operation reference for exact request fields, response shapes, and permissions. The OpenAPI file can generate typed clients. Read pagination and errors before building a list sync or retry loop.

Before scheduling the first sync, check the resource grant on each operation, choose a fixed page size for paginated reads, and decide how your job will resume after a failed page. Store the Nasam resource IDs you receive; do not use a channel name, brand display name, or page position as an external key. For write workflows, read the resource's current state and follow its domain guide before posting a change.