# List low stock thresholds `GET /api/v1/low-stock-thresholds` The reorder thresholds this store has armed, newest first: the total stocked quantity, summed across every location, at or below which the store owner is emailed that a variant is running down. THIS IS THE MERCHANT'S OWN NOTION OF LOW, not a stock level. How many units exist is read_inventory and changes on every order; this is a preference that changes rarely, which is why the two are separate grants and why a replenishment tool wants this one without being handed a live feed of the other. ONE THRESHOLD PER VARIANT AT MOST, so a store that armed its catalogue has as many rows as it has variants. Page it; do not assume one response holds them all. notified is the notify-once LATCH: true means the owner has already been told and will not be told again until stock recovers above the threshold. Read it before you raise a purchase suggestion, or every sync re-raises one the merchant has already acted on. It says nothing about when mail was sent or to whom, and no send time is published. A threshold of ZERO IS REAL and means "tell me when this variant is actually out". It is not the absence of a threshold. Absence is the row not being here at all, which is what DELETE produces. NO FILTERS. ?notified= is the one that looks useful and it would page a set that changes underneath you every time stock crosses a threshold; filter the page instead. ## Query parameters - `limit` (integer) — Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it. - `after` (string) — The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page. ## Responses - `200` — Success - `400` — The request was refused before any state changed. `code` is one of: `invalid_body`, a write body this route will not take. `reason` partitions it and `field` names the key when one key is at fault. `invalid_query`, a query parameter, including limit and after. `invalid_text`, a NUL byte or bytes that are not valid UTF-8 anywhere in the path, the query or the body. Strip control characters before sending. `idempotency_key_required`, a write sent without the Idempotency-Key header. `invalid_request`, an Idempotency-Key longer than 255 bytes. Routes add their own codes for rules only they know. Switch with a default arm. - `401` — No credential, or one this API does not accept. `code` is always `unauthorized`. THE BODY IS DELIBERATELY UNINFORMATIVE. An expired key, a revoked key, a publishable key, a key belonging to another merchant and a key that never existed are all refused with the same bytes, so this response cannot be used to probe which keys exist. Check the key's state in the dashboard rather than inferring it here. Send the key as `Authorization: Bearer ` or as `X-API-Key: `. It is never accepted in a query string. - `403` — The key lacks the read_low_stock scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for. - `429` — Too many requests. `code` is `rate_limited`. Two limits apply independently: one on the credential and the route family, one on the client address. The headers describe whichever has less left, so honouring Retry-After always clears the window that bound. - `default` — Any status this operation does not list, in the same envelope. A 5xx means the request may or may not have applied. Retry it with the SAME Idempotency-Key: that is the only way to find out without risking a duplicate, and it is what the key is for. A few 4xx conditions arrive here rather than as a listed status because they depend on the merchant's plan or on a module being wired: 402 when a quota or a plan limit is reached, and 503 when a capability the route needs is not configured on this deployment. Both carry a `code` naming which. ## Example ```bash curl --request GET \ --url 'https://api.mercemur.com/api/v1/low-stock-thresholds' \ --header 'Authorization: Bearer ' ```