# List marketing campaigns `GET /api/v1/marketing-campaigns` The store's marketing campaigns, newest first. IT DOES NOT CARRY THE CAMPAIGN BODY, and that is a size bound rather than a permission one: a body may be 500 KB and a page may hold 100 rows, so a list that served them could answer one request with fifty megabytes of markup. Read a single campaign to get its copy. ?status= and ?channel= narrow it, so "what is sending right now" is one call. An unknown value for either is a 400 rather than the unfiltered list, because "no paused campaign" and "there is no such status" are different facts and a client told the first stops looking. enqueued_count IS NOT DELIVERY. It counts the messages a campaign handed to the sending spine; the spine's own compliance gate can still decline an individual recipient, and the stats route is where that shows up. ## Query parameters - `status` (draft | scheduled | sending | paused | sent | cancelled) — Filter by lifecycle state. sending and paused are the two a monitoring client polls; sent and cancelled are terminal, so a campaign in either will not move again. A value outside the enum is a 400 naming the legal set. - `channel` (email | sms | push) — Filter by transport. A value outside the enum is a 400 rather than an empty page, which would read as "this store sends no email". - `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_marketing_campaigns 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/marketing-campaigns' \ --header 'Authorization: Bearer ' ```