How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vaquill AI US Session Laws API

State session laws: the acts of each legislature as they were enacted, chapter by chapter, before they are folded into a code. A session law is what the governor signs. It carries the act's own text, including the language it strikes and inserts, its approval and effective dates, and, where the publisher prints one, the code sections it changes. That makes it the source for "which act changed this section, and when did it take effect".Every act has a permanent `sessionLawId` (for example `SSL_MN_2025R_G_Y2025_C1`, Minnesota Laws 2025, regular session, chapter 1) whether or not we hold its text, and a citation or bill number such as `S.F.No. 1552` is accepted where an id goes. v1 serves STATE acts only. Federal session laws (the Statutes at Large, `SAL_` ids) are served by `/us/statutes/section`, and `/us/statutes/resolve` points a session-law citation here.**Start here**: check `/us/statutes/coverage` (free) for what we hold per state: each jurisdiction's `sessionLaws` block lists its sessions, which are complete or only partly collected, and the `series` and `instrumentTypes` that exist. Then **List** a session or a date range to get ids, **Get** one act for its record, then **Body** for its text. A law missing from a partly collected session is a free 404 (`session_not_fully_collected`), not proof it does not exist.- **List**: everything enacted in a state's session, approved in a window, or taking effect on a date- **Get**: one act by id or by citation; dates (`effectiveDates` is always a list), sources and the code sections it affects- **Body**: the act's text as printed, paged by cursor, with amendatory markup preserved where the publisher printed it- **Batch**: up to 50 ids or citations in one call, the same record as Get, billed per law served, with every miss listed and its reason- **Changes**: a sync feed of the registry over an integer cursor (`sinceId`): what began to be served, was corrected, withdrawn or mergedThe reverse link, from a code section to the acts a publisher's own tables list against it, is `GET /us/statutes/section/{actId}/enactments`.

Vaquill AI US Session Laws API is one of 26 APIs that Vaquill AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 18 JSON Schema definitions.

Tagged areas include US Session Laws. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a changelog, and 18 JSON Schemas.

This API exposes 6 operations across 6 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.vaquill.ai.

6 operations 6 paths 31 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.vaquill.ai/api/v1
Authentication
HTTP Bearer, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Vaquill AI US Session Laws API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (vq_key_*) (ApiKeyAuth). An API key is passed in the header as X-API-Key (ApiKeyHeader). An API key is passed in the query as api_key (ApiKeyQuery). By default, every request must be authenticated.

  • ApiKeyAuth — API key issued from the developer dashboard. Pass as Authorization: Bearer vqkey... (preferred).
  • ApiKeyHeader — The same API key as a bare header value: X-API-Key: vqkey.... Equivalent to the Bearer form.
  • ApiKeyQuery — The same API key as a query parameter: ?apikey=vqkey.... Use only where you cannot set a header. A URL can end up in proxy and server logs, browser history and…

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

US Session Laws 6

State session laws: the acts of each legislature as they were enacted, chapter by chapter, before they are folded into a code.

GET
/api/v1/us/session-laws/changes
Feed of changes to the session-law registry
get_session_law_changes_api_v1_us_session_laws_changes_get 3 params → 200401402403422429500503
POST
/api/v1/us/session-laws/batch
Get many state session laws at once, by id or citation
get_session_laws_batch_api_v1_us_session_laws_batch_post body → 200401402403422429500503
POST
/api/v1/us/session-laws/search
Search the text of state session laws
search_session_laws_api_v1_us_session_laws_search_post body → 200401402403422429500503
GET
/api/v1/us/session-laws/list
List a state's session laws
list_session_laws_api_v1_us_session_laws_list_get 16 params → 200401402403422429500503
GET
/api/v1/us/session-laws/{session_law_id}/body
Get a state session law's text
get_session_law_body_api_v1_us_session_laws__session_law_id__body_get 4 params → 200404409401402403422429
GET
/api/v1/us/session-laws/{session_law_id}
Get a state session law, by id or by citation
get_session_law_api_v1_us_session_laws__session_law_id__get 2 params → 200404401402403422429500

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are SessionLawBatchLaw (50 properties), SessionLawResponse (46 properties), SessionLawSummary (33 properties), SessionLawBodyResponse (25 properties). Each schema is shown below with its type and property counts.

SessionLawDenominator
object
How many laws a session is supposed to hold, and where that number comes from.
3 properties 2 required
SessionLawDetailSession
object
The session block of a single law: the session, and whether we hold all of it.
5 properties 1 required
SessionLawSearchRequest
object
Body of POST /us/session-laws/search.
9 properties 1 required
SessionLawDate
object
One printed date on a session law.
5 properties
SessionLawBatchMiss
object
One entry of ids that did not yield a law, and why.
10 properties 4 required
SessionLawBodyResponse
object
Response for GET /us/session-laws/{sessionLawId}/body.
25 properties 6 required
SessionLawChangesResponse
object
Response for GET /us/session-laws/changes.
6 properties
ApiDetailError
object
Error envelope the API actually returns. Every error (400/401/402/403/404/405/422/429/5xx) carries a detail string, e.g. {"detail": "Insufficient API credits."…
2 properties 1 required
SessionLawVolume
object
The bound volume an act's text was cut out of.
4 properties 3 required
SessionLawResponse
object
Response for GET /us/session-laws/{sessionLawId}.
46 properties 9 required
SessionLawSessionCoverage
object
One legislative session's session-law coverage.
13 properties 3 required
SessionLawSearchResponse
object
Response for POST /us/session-laws/search.
9 properties 2 required
SessionLawListResponse
object
Response for GET /us/session-laws/list.
7 properties
SessionLawBatchLaw
object
One served law: the same record GET /us/session-laws/{sessionLawId} returns.
50 properties 11 required
CodeSectionAffected
object
A code section the publisher lists the act as affecting.
4 properties 1 required
SessionLawSource
object
A document the record was collected from.
8 properties 1 required
SessionLawChange
object
One entry of the registry feed.
5 properties 5 required
SessionLawBatchResponse
object
Response for POST /us/session-laws/batch.
7 properties
SessionLawSearchResult
object
One law in the ranking.
13 properties 10 required
ApiFieldError
object
One rejected field in a 422 response.
3 properties 3 required
SessionLawPublisherId
object
An identifier the publisher itself gives an act.
2 properties 2 required
SessionLawResolution
object
How a citation sent in place of a sessionLawId was matched.
4 properties 3 required
SessionLawProvenance
object
How the text of an act was obtained, and what the collector noted about the record.
4 properties
SessionLawPublisher
object
What the publisher itself printed or published about an act, beyond the record's dates and citation.
9 properties
SessionLawListCoverage
object
What we hold of the session or state an EMPTY page was asked about.
8 properties 4 required
SessionLawSession
object
The legislative session a law was enacted in.
4 properties 1 required
SessionLawSearchParsed
object
How the query was read, so a caller can see why a result matched.
4 properties 1 required
SessionLawNotFoundError
object
The 404 from GET /us/session-laws/{sessionLawId} and its /body.
9 properties 3 required
SessionLawBatchRequest
object
Batch read. See POST /us/session-laws/batch.
3 properties 1 required
SessionLawSummary
object
One session law, as it appears in lists and citation results.
33 properties 9 required
SessionLawSearchPassage
object
The passage of the law that matched best, with a cut of its text.
8 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vaquill-ai-us-session-laws-api-openapi.yml Raw ↑

Other APIs Vaquill AI publishes across the network.

Vaquill AI Board Watches API
Vaquill AI Chronology API
Vaquill AI Clients API
Vaquill AI Comparisons API
Vaquill AI Compliance API
Vaquill AI Credits API
Vaquill AI Documents API
Vaquill AI Drafting API
Vaquill AI Facts API
Vaquill AI Folders API
Vaquill AI India Credits API
Vaquill AI India Pricing API
Where this information came from

This is an independent, third-party profile of Vaquill AI US Session Laws API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.