laws_history

The dated change records the source publishes in its Point in Time document for an act, newest first: effective date, the note, and whether it carries the text before the amendment. These are notes about changes, not a consolidation.

Cost: 2 units of your allowance (see Rate limits).

ParametersCopy Anchor Link

• doc_id (string, required)
• section (string, optional): min length 1, max length 20
• limit (integer, optional): min 1, max 50, default 20

RESTCopy Anchor Link

curl -X POST https://api.bcmcp.ca/v1/tools/laws_history \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"doc_id":"..."}'

MCPCopy Anchor Link

Call the tool laws_history with these arguments. Over raw JSON-RPC:

curl -X POST https://api.bcmcp.ca/mcp \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"laws_history","arguments":{"doc_id":"..."}}}'

What comes backCopy Anchor Link

Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.