---
title: "Upcoming AI-law effective / compliance dates (JSON or iCal)"
method: GET
path: "/deadlines"
---

# Upcoming AI-law effective / compliance dates (JSON or iCal)

`GET /deadlines`

## Request

- Base URL: `https://ai-law-tracker.com/api/v1`
- URL: `https://ai-law-tracker.com/api/v1/deadlines`
- Auth: one of:
  - none
  - API key in header `X-API-Key`
  - HTTP bearer

A forward-looking compliance calendar derived deterministically from the curated corpus — each entry carries the VERBATIM source deadline text + primary-source URL (no fabricated dates; a jurisdiction whose deadline text has no explicit date is only counted in meta.undated). Free for every tier. Pass ?format=ical (alias ics) for an RFC 5545 .ics you can subscribe to (webcal). The interpreted "what must I do about each deadline" layer is on /obligations + /assess.

## Query parameters

- `scope` 'state' | 'federal' | 'eu' | 'global'
- `jurisdiction` string
- `upcoming` boolean
- `format` 'json' | 'ical' | 'ics'

## Response `200`

A page of deadlines (application/json) or an .ics feed (text/calendar).

## Other responses

- `400`: Invalid parameter

---

[API](https://skmtc.dev/ai-law-tracker/apis/ai-law-tracker-public-laws-api.md) · [All operations](https://skmtc.dev/ai-law-tracker/apis/ai-law-tracker-public-laws-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ai-law-tracker/apis/ai-law-tracker-public-laws-api/revisions/25403268a853?raw)