API docs

The Juriset API is a read-only REST API at https://api.juriset.dev/v1. Every response carries the rule, the dates it applies, its official source and a saved copy of that source.

Reference

The OpenAPI document lists every endpoint, parameter and response with examples. llms.txt summarises the site for agents. Changes to /v1 only ever add; a breaking change would be /v2, with /v1 still served.

Keys

Send your key as Authorization: Bearer <key>. Plans and what each includes are on the pricing page.

Trying it without a key

Read-only requests (GET) work without a key, limited to 60 an hour and 500 a day per address. Past a limit the API answers 429 with the rate-limit headers saying when to retry. Anything that writes needs a key.

Errors

Errors are JSON, {"error": {"code": "…", "message": "…", "docs_url": "…"}}, with the HTTP status that fits. code is stable: branch on it, not on the message.

Caching

Every read has an ETag. Send it back as If-None-Match and, while nothing has changed, you get a 304.

Status

Outages and planned maintenance are on the status page.

Audit bundles

Paid plans (Developer and above) can download a zip for any version: GET /v1/versions/{id}/audit-bundle. It holds the version as served, its whole verification record, the change events around it and the cited source as fetched, each file with its SHA-256. It is for showing an auditor which rule a decision rested on. It is not signed yet.

Track record

GET /v1/track-record returns the figures on the track-record page: no key needed, not counted as a lookup.

Not legal advice

Informational only. Not legal advice. Verify with the cited source. Every response from /v1 carries it, in the body of a rule and in a Juriset-Disclaimer header on all of them. Your use of the API is covered by the terms; the full statement says what Juriset is and is not.