Get Regulation Wiki
GET /api/v1/regulation-wikis/:slugEach wiki is a one-call compliance playbook — a synthesized cross-authority answer structured in Authority Chain format (Statute → Regulation → Examination Handbook) with inline citations back to the underlying regulations. This endpoint returns the full Wiki Object for a single activity, including the synthesized body and the sources array of externalId slugs.
Parameters
Section titled “Parameters”| Name | In | Type | Description |
|---|---|---|---|
slug | path | string | Activity slug from a List Regulation Wikis result (e.g. sar-filing) |
Response
Section titled “Response”{ "slug": "sar-filing", "title": "Suspicious Activity Report (SAR) Filing", "domain": "bsa-aml-sanctions", "description": "Requirements for detecting and filing Suspicious Activity Reports under the Bank Secrecy Act, covering thresholds, timelines, completion standards, and safe-harbor protections.", "sources": [ "31-cfr-1020-320", "31-cfr-1010-320", "ffiec-bsa-aml-exam-manual-sar", "fincen-sar-instructions-2023", "31-cfr-1020-210", "us-code-31-5318", "fincen-sar-safe-harbor-guidance" ], "body": "# Suspicious Activity Report (SAR) Filing\n\n## Authority Chain\n\n### Statute\n\n**31 U.S.C. § 5318(g)** requires financial institutions to report any known or suspected violation of law or regulation. [Source: us-code-31-5318]\n\n### Regulation\n\n**31 CFR § 1020.320** requires banks to file a SAR within 30 calendar days of the initial detection of facts that may constitute a basis for filing. [Source: 31-cfr-1020-320]\n\n...", "updatedAt": "2026-04-15T00:00:00Z"}Response Fields
Section titled “Response Fields”The response is a Wiki Object. Key fields:
| Field | Type | Description |
|---|---|---|
slug | string | Activity slug |
title | string | Human-readable activity name |
domain | string | Compliance domain slug |
description | string | Plain-language summary |
sources | string[] | Ordered externalId slugs of source regulations |
body | string | Full synthesized markdown playbook |
updatedAt | string | ISO 8601 UTC timestamp of last regeneration |
Worked Example: SAR Filing
Section titled “Worked Example: SAR Filing”Fetch the SAR filing playbook:
curl "https://api.midlyr.com/api/v1/regulation-wikis/sar-filing" \ -H "x-api-key: $MIDLYR_API_KEY"Resolve the primary statutory source to read verbatim text:
curl "https://api.midlyr.com/api/v1/regulations/us-code-31-5318" \ -H "x-api-key: $MIDLYR_API_KEY"Resolve the primary regulatory source and pull its content:
# 1. Get document metadata and total sizecurl "https://api.midlyr.com/api/v1/regulations/31-cfr-1020-320" \ -H "x-api-key: $MIDLYR_API_KEY"
# 2. Read the full document bodycurl "https://api.midlyr.com/api/v1/regulations/31-cfr-1020-320/content?offset=0&limit=40000" \ -H "x-api-key: $MIDLYR_API_KEY"Resolving Sources
Section titled “Resolving Sources”Each entry in sources[] is an externalId slug that resolves to a regulation document in the Regulations API. Use Get Regulation Details with the slug as the document id.
Sources are ordered from most authoritative (statute) to most operational (examination guidance), mirroring the section order in body.
Not Found
Section titled “Not Found”If the slug does not exist, the API returns 404 not_found. Slugs are stable and never reassigned — a 404 means the wiki has not been published yet or the slug is misspelled.
Rate Limits
Section titled “Rate Limits”Regulation Wikis endpoints use a separate rate-limit bucket from the Regulations API. See Errors for rate-limit error shapes.
Authentication
Section titled “Authentication”Pass either a Bearer token or an x-api-key header. See Authentication.