---
title: "Fetch a published advisory by slug"
method: GET
path: "/trust/advisories/{slug}"
tags: ["Trust"]
---

# Fetch a published advisory by slug

`GET /trust/advisories/{slug}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/trust/advisories/{slug}`
- Auth: none required

Returns the canonical advisory record for `{slug}`. Drafts and archived rows are not exposed on this surface — the CMS admin endpoints serve those.

## Path parameters

- `slug` string, required

## Response `200`

Advisory record.

- object
  - `id` string, uuid, required
  - `slug` string, required: URL-safe slug used as the customer-facing detail path.
  - `title` string, required
  - `summary` string, required
  - `body_markdown` string, required
  - `severity` 'info' | 'low' | 'medium' | 'high' | 'critical', required
  - `status` 'draft' | 'published' | 'archived', required
  - `published_at` string, date-time, nullable, required
  - `archived_at` string, date-time, nullable, required
  - `post_mortem_for_campaign_id` string, uuid, nullable, required
  - `synthetic` boolean, required
  - `created_by` string, uuid, required
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)