Tags are free-form labels you put on products and content pages to group and filter them. They aren’t defined in advance. A tag exists while at least one record carries it.

Products and content pages keep separate tag lists. A guides tag on a product and a guides tag on a content page are unrelated, and each list has its own endpoint.

In the admin

On a product:

  1. Open the product from Catalog → Products.
  2. Under the product name, click + Add tag (or + tag if the product already has tags).
  3. Type the tag and press Enter. The input suggests tags already used in your catalog. The change saves straight away.
  4. To remove a tag, click the × on its chip.

On a content page: open the page from Content → Content pages and use the Tags section the same way.

Filtering: on the products list, the Tags group in the filter sidebar shows the most-used tags with counts. Click one to filter the list.

Many products at once: select products on the list, then click Tags in the bulk bar. Pick Add to existing, Remove from existing or Replace existing. See Bulk editing.

With the API

MethodPathWhat it does
GET/v1/products/tagsProduct tags in use, with counts
GET/v1/content/tagsContent-page tags in use, with counts
GET/v1/products?tag=…Products carrying the tag
GET/v1/content?tag=…Content pages carrying the tag
PATCH/v1/products/{id}tags replaces the product’s full list
POST/v1/products/bulk-set-tagsAdd, remove or replace tags on up to 500 products
curl 'https://api.minipim.com/v1/products?tag=summer-sale&tag=featured' \
  -H 'Authorization: Bearer pim_…'

The ?tag= parameter can be repeated. When you pass more than one, a record has to carry all of them to match. Filter values are normalized the same way stored tags are, so ?tag=Summer%20Sale matches summer-sale.

The tag-list endpoints return [{ "value": "featured", "count": 42 }, …], most used first.

Full reference: api.minipim.com/docs.

Rules and limits

  • Tags are normalized when they’re saved. minipim lowercases each tag, strips accents, replaces every run of other characters with - and trims leading and trailing -. "Buying Guide" is stored as buying-guide. The response won’t match your input exactly.
  • A tag can be up to 80 characters as sent, and is cut to 60 characters after normalizing. Two long tags can end up as the same tag.
  • A record can carry up to 50 tags.
  • Tags that normalize to nothing (such as "!!") are dropped. Duplicates are removed, keeping the first one. The list you get back can be shorter than the one you sent.
  • Sending tags on a product or content-page update replaces the whole list. To add or remove single tags without resending the list, use bulk-set-tags with mode: "add" or "remove". Products only.
  • The tag-list endpoints return at most 200 tags.
  • Only products and content pages have tags. Variants, categories and brands don’t.
  • Product tags are different from the tags attribute type, which stores a list of strings as an ordinary attribute value. The Shopify connector imports Shopify’s product tags into a tags attribute, not into product tags.

See also

  • Products — How minipim products work: family, slug, attribute payload and tags, plus creating, editing, duplicating and deleting them in the admin or via the API.
  • Content pages — Store policies, guides and blog posts next to your catalog. Turn content pages on, manage content types, look pages up by slug, and publish safely.
  • Bulk editing — Change many products at once: set an attribute, status, tags or categories, move family, or delete. Up to 500 ids per API call, with a result for each product.
  • Listing, filtering and pagination — How minipim list endpoints page with limit, offset and hasMore, which ones return plain arrays, and the filters, sorts and limits /v1/products accepts.