--- title: "Which acts a state publisher lists against this section" method: GET path: "/api/v1/us/statutes/section/{act_id}/enactments" tags: ["US Statutes"] --- # Which acts a state publisher lists against this section `GET /api/v1/us/statutes/section/{act_id}/enactments` ## Request - Base URL: `https://api.vaquill.ai` - URL: `https://api.vaquill.ai/api/v1/us/statutes/section/{act_id}/enactments` - Auth: one of: - HTTP bearer - API key in header `X-API-Key` - TypeScript: (a function with typed inputs; its response is checked against the schema) The state session laws a publisher's own tables list against one code section: which act added, amended or repealed it, when the act took effect, and what the publisher printed. Start from an `actId` (or a citation), then read the act at `href`, or its text at `href` plus `/body`. **Stage 1.** This reads the code-section tables that state publishers print against their session laws ("sections affected") through a reverse lookup. It is never a complete amendment history: only acts we hold, in sessions we hold (`coverage.sessionsHeld`), whose table lists the section in the printed form we map. An empty `enactments` with `supported: true` means "no held table lists this section", not "this section was never amended". `coverage.note` says per jurisdiction what is not read. Rows are newest act first and one per act; the section record's own `history` field names only the latest amendment, so a section can show one act there and many here. **Two kinds of evidence, never blended.** `basis: publisher_sections_affected` with `matchQuality: as_printed` comes from the publisher's table. In AR, LA, ME, MI, VT, WI there is no such table read, so the section's history credit line is read instead: `basis: credit_line` with `matchQuality: credit_cite_unique` means the credit cites a session law (`citeAsPrinted`, verbatim) that names exactly one act we hold, in the same state, in a year that fits. A citation that fits several acts, a special-session or list form, or an act we do not hold is dropped, not guessed. A credit-line row states no action (`action: other`). **Where it works.** CA, DC, HI, KY, MO, MS, NE, UT, WA: the jurisdictions where the publisher's printed form was shown to map to our section numbers against real data on both sides. Any other jurisdiction (and any federal, regulation or constitution section) answers `supported: false`, an empty list, a `reason` and a `coverage.note`, and is not charged. Matching is on the whole number after folding case, spacing, dashes and the section sign (`71-24,104` does not match `71-24,10`); where a publisher qualifies a section by code (California, Hawaii, DC) the code must match too. **Cost**: 1 credit per call. Refunded on a 404, on an unsupported jurisdiction or section, and on a failure (500, 503). A supported section whose answer is empty is charged, because "no held table lists it" is the answer you paid for. A citation in place of the id also pays the `/resolve` price when it resolves; a citation that resolves to nothing is refunded in full, that price included. `creditsConsumed` reports what was billed. **A row.** `sessionLawId` and `href` name the act. `action` is `added | amended | repealed | renumbered | other`, mapped only where the publisher's legend is settled, and `actionAsPrinted` is always the publisher's own code. `effectiveDates` are the act's, not necessarily this section's. `sectionAsPrinted`, `codeAsPrinted` and `actSectionAsPrinted` are verbatim. An act whose table lists the section more than once with the same action is folded into one row, and `printedEntryCount` says how many entries it holds. An omnibus act is titled by every section it amends (California): such a `title` is shortened to the section you asked about, `titleCompacted` is true and `sectionsTouchedCount` says how many sections the title lists; the full title is at `href`. `truncated` is true past 200 rows. **Example** ```bash curl "https://api.vaquill.ai/api/v1/us/statutes/section/STATE_MS_T27_C71_S27-71-5/enactments" \ -H "Authorization: Bearer $VAQUILL_API_KEY" ``` **Related endpoints** - `GET /us/statutes/section/{actId}/changes` is what our refreshes observed to the section. - `GET /us/session-laws/{sessionLawId}` reads an act from `href`; `/body` reads its text. - `GET /us/statutes/coverage` says which sessions we hold in each jurisdiction's `sessionLaws` block. ## Path parameters - `act_id` string, required: Section identifier, e.g. `USC_T42_C21_S1983` (42 U.S.C. § 1983). Take it from a `/us/statutes/search`, `/resolve` or `/divisions` result; do not assemble one. A citation such as `42 USC 1983` also works and adds the `/resolve` price (see `GET /us/statutes/section/{actId}`). State session laws (`SSL_` ids) are read at `/us/session-laws/{sessionLawId}`. ## Headers - `Idempotency-Key` string, nullable: Optional. 16 to 255 visible ASCII characters (a UUIDv4 works). Repeating the same request with the same key replays the original 2xx response for 24 hours without charging again. The same key on a different request is rejected. With the account's `cacheQueryDerivedData` retention setting off, no body is stored and a retry answers 409 `idempotency_replay_unavailable`, still without a second charge. ## Response `200` The entries the publisher's tables list against the section, or `supported: false` (not charged). Not a complete history. - SectionEnactmentsResponse: Response for `GET /us/statutes/section/{act_id}/enactments`. - `actId` string, required: The section's act_id as served, after any citation or copy damage was resolved. - `resolvedFrom` SectionIdentifierResolution: How the identifier you sent was matched, when it was not an exact act_id. Present only when the input did NOT match as sent. Absent (null) means the section is exactly the act_id in your request. - `input` string, required: The identifier exactly as you sent it. - `actId` string, required: The act_id it matched. Send this next time to skip resolution. - `via` 'normalized_id' | 'citation', required: `citation` -- your input was a citation, resolved with the same resolver as `GET /us/statutes/resolve`. Check it the way you would check a `/resolve` answer. `normalized_id` -- your input was an act_id carrying surrounding whitespace, quotes, a trailing period or double percent-encoding, which were removed. - `subsection` string, nullable: The pincite your citation carried, e.g. `(h)(11)` for `26 U.S.C. § 1(h)(11)`. The whole section is served; use `pinpoint=(h)(11)` on `/body` to get that subsection, or `structured=true` for the whole tree. - `matchLevel` 'container' | 'multiple' | 'repaired' | 'register_reference', nullable: Present only when `section` is NOT the exact unit you cited. `container`: you cited a container in one of the supported forms (a Missouri, New Jersey, West Virginia or Wyoming regulation series or chapter, a constitution article or amendment, an Indiana chapter, an Illinois article, or a U.S. Code chapter such as `18 U.S.C. ch. 96`; a U.S. Code subchapter is not read), and `section` is the FIRST section inside it (see `container` for how many there are and what they are). A state STATUTE chapter, subchapter, title, article or part cited with its container word and a code name we read for that state (`8 Del. C. ch. 1, subch. VII`, `Tex. Penal Code ch. 19`, `N.Y. Penal Law art. 125`, `Mass. Gen. Laws ch. 93A`, `La. R.S. Title 14`) also answers `container`, with `section` the first live section in statutory order, but only where we hold that container and its number is unique within the code. A container we do not hold, a missing or unrecognised code name, a regulation or rule set, or a number that repeats in the code (California repeats chapter numbers across its titles) when the citation names more than one level, returns `resolved: false` with `missReason: container_not_supported`. An article that IS the section unit (`La. Civ. Code art. 2315`, `Tex. Code Crim. Proc. art. 38.23`) is read as a section. To browse chapters, titles and articles use `GET /us/statutes/divisions`. `multiple`: you cited several sections (`§§ 8, 10`, `§§ 1983-1985`) and `section` is the first of them (see `citedSections`), or your citation fits more than one held section (`D.C.COLO.LR 7.1` is both Local Civil and Local Criminal Rule 7.1) and every candidate is listed in `container`; a state statute container number that repeats within its code (`Cal. Penal Code tit. 8` is a title of each of four parts) lists each candidate container's first section there, never picking one, when there are at most 10. `repaired`: the code name you wrote is a recognised miscite and `section` is the one it names (see `repair`); or (`repair.kind: prior_edition`) the text you cited has been replaced by a current one, and `section` is NOT the text you cited: a C.F.R. or U.S.C. section the current code no longer holds, answered with the MOST RECENT historical annual edition we hold, or a superseded rule set whose rule numbers were kept, answered with the current rule (`Tex. R. Civ. Evid. 803` is answered by `Tex. R. Evid. 803`), or a state regulation we hold only as superseded filings, answered with the latest filing (`W. Va. Code R. § 64-14-5`); `repair.interpretedAs` names what was served and why, and `repair.alternatives` lists the other held editions, if any; or (`repair.kind: former_law`, `former_number`) you cited a FORMER section number, recodified or renumbered since, and `section` is the successor the state's own disposition table or history line names, never the former text (a former section split into several answers `multiple`, every successor in `citedSections`). or (`repair.kind: code_name_inferred`) your citation named no code (`CODE ANN. § 73.001`, `Code 4121-3-34`) and `section` is the only one in the state that carries that number, so the code was inferred from the number and not read from your citation; or (`repair.kind: repealed_range`, `renumbered_range`, `range_member`) you cited a New York or California section the publisher printed only inside a run of sections (`6 NYCRR 420.4` inside `420.3 to 420.4`), and `section` is that stub, not the section's own text (`repair.interpretedAs` names the range); `register_reference`: you cited a state register page, and `section` is a rule whose history cites it (see `registerReference`). `resolved` keeps its meaning (a section was returned) and is true at every level; read `matchLevel` to tell an exact section from a first-of-several. Absent for an exact match. - `container` ResolveContainerInfo: What the citation named, and what lies inside it. - `kind` string, required: What was cited: `chapter`, `subchapter`, `series` (a rule group number such as `5th Cir. R. 47`, held only as `47.1` to `47.10`), `article`, `section` (a constitution section made of numbered paragraphs, or a California regulation held as one document per subsection, `18 CCR 17071` being `(a)` to `(q)`), `amendment`, `document` (a rule set stored as one document holding several editions) or `alternatives` (with `matchLevel: multiple`: the held sections the citation could mean). - `label` string, required: The container, as we read your citation. - `childCount` integer, required: How many sections the container holds. Always exact, even when `children` is cut. - `children` ResolveContainerChild[]: The sections inside, in document order. `section` is the first of them that is in force (the first of all when none is), so it is `children[0]` unless that one is repealed or otherwise not in force. For an `amendment` of a state whose constitution is held as amended text, these are the sections whose own note credits that amendment, which is what the corpus records; a section the corpus does not annotate is not listed. - `actId` string, required: The child section's id. - `citation` string, nullable: The child's own citation. - `status` string, nullable: Its status in the corpus (`in_force`, `repealed`, ...). - `truncated` boolean: True when `children` lists fewer than `childCount` sections. - `citedSections` string[], nullable: Set with `matchLevel: multiple`. The sections your citation named, as written (a range such as `1983-1985` is one entry); `section` is the first. Omitted from the response when it has no value. - `repair` ResolveRepairInfo: A miscite we recognised, and how we read it. - `kind` string, required: What was repaired: `code_name` (a recognised miscite of the code name); `prior_edition` (the text you cited has been replaced, so `section` is not it: a C.F.R. or U.S.C. section held only as a historical annual edition, where `interpretedAs` names the edition and its year and `alternatives` the other editions; or a superseded rule set whose numbers were kept, such as the former Texas Rules of Civil and Criminal Evidence, answered with the current rule and the reason in `interpretedAs`; or a state regulation held only as superseded filings, where `interpretedAs` names the latest filing's date and `alternatives` the earlier filings); `code_name_inferred` (the citation named no code, so the only section in the state with that number was served: `interpretedAs` is that section's citation, `cited` the head as you wrote it, and `alternatives` is empty because a number held by two codes is refused, never guessed); `former_law` (you cited a section number the state's code no longer carries, and the state's own disposition table, a code commission comparative table, a revisor's renumbering stub or the Code's history credits, says which current section it became; `cited` is the number you wrote, `interpretedAs` the successor's citation with what the table says: recodified, renumbered or merged, the effective date when the table gives one, and the source. The former text itself is not served; with `matchLevel: multiple` the former section was SPLIT and `citedSections` lists every successor); `former_number` (the same, read from the successor's own history line where the state prints its lineage there: Georgia's `Code 1933, §` and Washington's `Formerly RCW`). Other values name the kind of miscite that was read through, such as `act_section`, `article_edition`, `ca_ucc_article_number`, `cfr_exchange_act_rule`, `cfr_five_digit_part`, `cfr_listing_of_impairments`, `cfr_part_number_mixed`, `cfr_part_omitted`, `cfr_part_truncated`, `cfr_separator`, `cfr_title`, `cfr_title_typo`, `code_article_for_constitution`, `dash_spacing`, `dotted_subdivision`, `duplicated_act`, `federal_label_state_rule`, `footnote_digit`, `former_code_name`, `former_collected`, `former_lpra_repealed_twin`, `former_title_renumbered`, `fused_subdivision`, `fused_subsection`, `fused_subsection_letter`, `glued_et_seq`, `glued_paragraph_letter`, `habeas_rules_stray_number`, `hyphen_restored`, `inside_range`, `letter_suffix_pinpoint`, `local_rule_series_inferred`, `lost_section_sign`, `merged_section`, `nm_rule_set_prefix`, `number_spelling`, `nycrr_title`, `ocr_digits`, `padded_decimal`, `part_and_section`, `pr_appendix_evidence`, `range_member`, `renumbered_provision`, `renumbered_range`, `renumbered_rule`, `renumbered_title`, `restated_rule`, `roman_section`, `set_label`, `slash_for_hyphen`, `snapshot_numbering`, `source_table`, `source_table_split`, `statute_cited_as_regulation`, `tex_statute_under_rule_label`, `title_chapter_form`, `title_dropped`, `title_inferred`, `title_moved`, `trailing_rule`, `transposed_chapter`, `truncated_section`, `usc_appendix_range_point`, `usc_appendix_unique_act`, `usc_cfr_miscite`, `usc_patent_rule_miscite`, `usc_state_code_miscite`, `wrong_rule_set_same_state`, `zero_padded_rule`, `zero_padded_section`, `zero_padding`. The set grows as repairs are added, so treat `kind` as an open string, not a closed enum; `interpretedAs` always says in words what was read. - `cited` string, required: The part of your citation we corrected. - `interpretedAs` string, required: What we read it as. - `alternatives` ResolveRepairAlternative[]: Other sections the name you wrote could also have meant. Empty when the repair was the only reading. - `actId` string, required: Another held section the cited name could also have meant. - `citation` string, nullable: That section's own citation. - `registerReference` ResolveRegisterReference - `citation` string, required: The register citation, as we read it. - `state` string, required: Two-letter state code of the register. - `kind` 'page' | 'range' | 'issue' | 'filing', required: How the citation matched the rules' history notes. `page`: a note cites exactly this volume and page. `range`: a note cites a page range that contains it. `issue`: the citation names a register issue (Colorado, Michigan). `filing`: it names a filing identifier (Washington WSR, Nevada LCB file, Indiana LSA document, Wisconsin register number). - `ruleCount` integer, required: How many held rules cite it. Always exact, even when `rules` is cut. - `rules` string[]: Their act_ids in document order, starting with the one returned as `section`. - `registerItemHeld` boolean: False when `section` is a RULE whose history cites the item (the item itself is not held for this state). True when `section` IS the register item, held under `corpusType=STATE_REGISTER`; then `rules` is that one item and `kind` is `page` (the cite names the page the item starts on) or `range` (a later page of the item). - `jurisdiction` string, nullable: Lowercase two-letter code of the section's jurisdiction. Null for a federal section. - `supported` boolean, required: True when this section's jurisdiction is one whose publisher table is mapped to the statutes section numbers and this section is in the form that mapping was proven on, or one whose credit lines are read for session-law citations: then `enactments` is an answer, even when it is empty, and the call is charged. False when it is not (see `reason`): `enactments` is empty, says nothing about the section, and the call is NOT charged. - `reason` 'unsupported_jurisdiction' | 'not_a_state_code_section' | 'section_not_in_proven_form' | 'section_number_missing' | 'section_citation_mismatch' | 'code_unknown' | 'code_not_proven', nullable: Why `supported` is false. `unsupported_jurisdiction`: we do not read this jurisdiction's table (none is printed, or its form is not verified against our section numbers), see `coverage.note`. `not_a_state_code_section`: the section is not a state statute (a federal, regulation or constitution section). `section_not_in_proven_form`: the jurisdiction is read, but this section's stored number is not in a form the mapping was proven on, so it is not guessed at. `section_number_missing`: the stored section carries no number to look up. `section_citation_mismatch`: the stored section number and the stored citation disagree (or the citation is not in the printed shape), so neither is trusted. `code_unknown` / `code_not_proven`: the section sits in a code (California, Hawaii, DC) we cannot name, or one whose printed form was not proven against our section numbers. Null when `supported` is true. - `enactments` SectionEnactment[]: The acts the publisher's tables list against this section, newest act first (by approval date, undated last), ONE ENTRY PER ACT AND ACTION (`printedEntryCount` says how many printed entries were folded into it). This is the whole chain of acts we can link to the section, while the section record's own `history` is only its latest amendment. NEVER a complete history: only acts we hold, in sessions we hold, whose table lists the section in the printed form this jurisdiction's mapping reads. Empty with `supported: true` is a real answer: no held table lists it. - `sessionLawId` string, required: The act, in the session-law registry. Read it at `href`. - `href` string, required: Path of the act on this API: `GET` it for the record, or its `/body` for the text. - `citation` string, nullable: The act's citation as its publisher prints it. Null when none is held. - `title` string, nullable: The act's title as printed. Null when none is held. - `sessionCode` string, nullable: The session the act was enacted in, as in `coverage.sessionsHeld`. - `approvedDate` string, date, nullable: Date the governor approved the act, ISO 8601: never an effective date. Null when none is held. - `effectiveDates` SessionLawDate[]: Every effective date the publisher prints for the ACT, in printed order: the act's, not necessarily this section's (an act can take effect in parts, and a date may carry a `scopeAsPrinted`). Empty when none is held, which does not mean the act is not in force. - `kind` string, nullable: What the date is, on `otherDates`: `approved`, `filed` or `other` (`kindAsPrinted` carries the publisher's label for `other`). Null on `effectiveDates`, where every entry is an effective date. - `date` string, date, nullable: The date as ISO 8601 when the printed text could be read as one. Null when the publisher's wording is not a calendar date. - `dateAsPrinted` string, nullable: The date exactly as the publisher wrote it, including any time of day. - `kindAsPrinted` string, nullable: The publisher's own label for what the date is, when it prints one. - `scopeAsPrinted` string, nullable: What the date applies to when it is not the whole act, as printed: an act can take effect in parts. Null when the date applies to the act as a whole. - `action` 'added' | 'amended' | 'repealed' | 'renumbered' | 'other', required: What the act did to the section, normalised: `added`, `amended`, `repealed`, `renumbered`, or `other`. It is mapped from `actionAsPrinted` only where the publisher's legend is settled; `other` means the table prints no action (Nebraska, `actionAsPrinted` is null), prints one that is not a change to this section (Mississippi's `BF`, brought forward), or one we do not map. Never read `other` as 'unchanged'. The publisher's own code is always in `actionAsPrinted`. - `actionAsPrinted` string, nullable: The publisher's own action code or word for this entry, verbatim. Null when the table prints none. - `sectionAsPrinted` string, required: The section exactly as the publisher's table prints it. - `codeAsPrinted` string, nullable: The code the publisher qualifies the section with, as printed (`HRS`, `D.C. Code`, `Education Code`). Null where the publisher prints none. - `actSectionAsPrinted` string, nullable: Which section of the ACT does it, as printed (Washington's `1223`, Kentucky's `5`). Null where the table prints none. - `citeAsPrinted` string, nullable: Set only on `basis: credit_line` rows: the session-law citation exactly as the section's credit line prints it. Null on `publisher_sections_affected` rows. - `basis` 'publisher_sections_affected' | 'credit_line': Where the entry comes from. `publisher_sections_affected`: the publisher's own table of the code sections an act affects. `credit_line`: the section's own history credit cites the act, and the citation names exactly one act we hold; weaker evidence, and it states no action. Never read out of the act's prose. - `matchQuality` 'as_printed' | 'credit_cite_unique': How the entry was matched. `as_printed` (publisher table rows): the printed section equals this section's number after folding case, spacing, dashes and the section sign, and nothing is matched by prefix. `credit_cite_unique` (credit-line rows): the credit's citation resolved to exactly one act in the same state with a numbering year within one year of the cited one; a citation that fits several acts is dropped, never guessed. Neither is a legal analysis of what the act did. - `identityConfidence` 'confirmed' | 'single_source' | 'inferred' | 'disputed', required: How firmly the registry knows the act is the law it says it is: `confirmed`, `single_source`, `inferred` or `disputed`. - `textStatus` 'held' | 'withheld' | 'not_held' | 'pending', required: Whether we serve the act's text: `held`, `withheld`, `not_held` or `pending`, as on `GET /us/session-laws/{sessionLawId}`. - `enactmentOutcome` 'signed' | 'became_law_without_signature' | 'veto_overridden' | 'line_item_veto' | 'vetoed' | 'pocket_veto' | 'not_presented' | 'approved_by_voters' | 'unknown', nullable: How the act became (or did not become) law, as on the act's record: `signed`, `vetoed` and so on. Null when it is not recorded. - `printedEntryCount` integer: How many printed entries of the publisher's table were folded into this one entry. An act appears once however many times its table lists the section (a second spelling of the number, or two sections of the act amending it); above 1 means `actionAsPrinted` and `actSectionAsPrinted` may list several values. - `sectionsTouchedCount` integer, nullable: Set only when `title` was shortened: how many code sections the act's own title lists. An omnibus act is titled by every section it amends; `title` then keeps the section asked about and counts the rest. Null when the title is served as printed. - `titleCompacted` boolean: True when `title` is a shortened display form. The full title is on the act: `GET` `href`. - `count` integer: Entries returned in `enactments`. - `truncated` boolean: True when more entries matched than are returned (the newest are kept). A section amended by that many acts is not a case we have met. - `coverage` EnactmentCoverage, required: What this answer is read from, and what it is not. - `jurisdiction` string, nullable: Lowercase two-letter code of the section's jurisdiction. Null for a section that is not a state statute (a federal section). - `sessionsHeld` EnactmentSession[]: The sessions of this jurisdiction whose code-section tables are held. A session not listed contributes nothing to `enactments`: an empty list says we read nothing, not that the section was untouched. Empty for an unsupported jurisdiction. - `code` string, required: Session code, `{year}{type}{ordinal}`, as on `GET /us/session-laws/list`. - `label` string, nullable: The session's canonical label, as the publisher names it. - `status` 'complete' | 'partial', nullable: Whether we hold every act of the session (`complete`) or only part of it (`partial`): an act missing from a partial session is not evidence that it did not touch the section. Null when coverage could not be read just now. - `note` string, required: In words: where the list comes from for this jurisdiction, and what it does not read. Show it beside the list: `enactments` is what the publisher's table prints, never a complete amendment history. - `creditsConsumed` integer: Credits actually charged for this call, never the list price. 0 when `supported` is false (refunded) and on a failure. A citation sent in place of the act_id adds the `/us/statutes/resolve` price when it resolves; a citation that resolves to nothing is refunded in full, the `/us/statutes/resolve` price included. - `processingTimeMs` number: Server-side time for this request in milliseconds, excluding network transit. Not billed on. ## Other responses - `401`: Missing, invalid or revoked API key. - `402`: Insufficient credits (`insufficient_credits`, never retry). `creditsRequired` and `creditsAvailable` say how short you are when known; top up, then repeat the call. - `404`: No such section. `reason` says why, `didYouMean` lists real ids. Not charged for the route; a citation's `/resolve` price is kept on an unresolved citation. - `409`: Idempotency conflict. `idempotency_in_progress`: the original request with this key is still running (retry after `Retry-After`). `idempotency_replay_unavailable`: it completed but its response was too large to replay; nothing is charged again, so check the credit balance instead of retrying. - `422`: Validation error: `detail` plus one `errors` entry per rejected field. `idempotency_key_reused`: the `Idempotency-Key` was already used with a different request. - `429`: Rate limit exceeded. - `500`: Internal error (`internal_error`, retryable). Any credits charged for the call are refunded; retry with backoff and quote `requestId` to support if it persists. - `503`: The statutes corpus or the session-laws database is temporarily unavailable. The charge is refunded; retry. ## Changes - **2026-11-07** `340c0d24d0b6`: 4 warning, 55 info - added the new `code_not_proven` enum value to the `reason/anyOf[subschema #1]/` response property for the response status `200` - added the new `code_unknown` enum value to the `reason/anyOf[subschema #1]/` response property for the response status `200` - added the new `section_citation_mismatch` enum value to the `reason/anyOf[subschema #1]/` response property for the response status `200` - added the new `section_number_missing` enum value to the `reason/anyOf[subschema #1]/` response property for the response status `200` - …55 more [Operation history](https://skmtc.dev/vaquill/apis/vaquill-developer-api/changes/api/v1/us/statutes/section/:act_id/enactments/get.md) --- [API](https://skmtc.dev/vaquill/apis/vaquill-developer-api.md) - [All operations](https://skmtc.dev/vaquill/apis/vaquill-developer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vaquill/apis/vaquill-developer-api/revisions/340c0d24d0b6?raw)