# List a marketing contact's consent events

`GET /api/v1/marketing-contacts/{marketingContactId}/consent-events`

One contact's consent ledger, newest first: how the state on the contact came to be what it is. THIS IS THE EVIDENCE. The consent fields on a contact say what is true now; these rows say which channel, which decision, which words the person was shown and when. It is append-only and this platform holds no permission to update or delete a row, so a mistake can only be contradicted by a later event, never rewritten. ?channel= narrows it to email, sms or push. Omit it for the whole trail, which is the call to make when reconciling one person across channels. NO IP AND NO USER AGENT are published. They are a real person's network address and device, and nothing that makes this row proof depends on them.

## Path parameters

- `marketingContactId` (string, required)

## Query parameters

- `channel` (email | sms | push) — Narrow the trail to one channel. OMIT IT for the whole history, which is the call to make when reconciling one person across channels: the dashboard's own read requires a channel because it drives a per-channel tab, and requiring one here would make the common case cost three requests. An unrecognised value is a 400.
- `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 <key>` or as `X-API-Key: <key>`. It is
never accepted in a query string.
- `403` — The key lacks the read_marketing_contacts scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for.
- `404` — The resource this url addresses does not exist, or never did on this store.

`resource` names the kind of thing that was missing and is the half to branch
on: the code is `not_found` on newer routes and a per-entity spelling on
routes that shipped before that rule, and the two mean the same thing.

A 404 is ALWAYS about the url. An id inside the request body that resolves to
nothing is 422 `unprocessable_reference` instead, so the two cases stay
distinguishable. An id that belongs to a different merchant reads exactly like
one that never existed.
- `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-contacts/{marketingContactId}/consent-events' \
  --header 'Authorization: Bearer <token>'
```