API
Everything DALICC does through the website it also does over HTTP. Start with the interactive documentation, then read the reference for what each answer means.
-
Interactive API documentation
The OpenAPI page lists every operation with its parameters and its answers, and it sends a request for you from the browser. It runs on the API host, so it opens in a tab of its own.
-
API reference
The reference explains every endpoint in prose: what it takes, what it answers and what each field means. Read it when you know the shape of a call and need to know what it does.
-
Python client
The
daliccpackage wraps the same operations as Python functions, and it brings a command line tool along. Its only runtime dependency ishttpx. -
API tokens and limits
Reading, searching and reasoning need no credentials, so most of the API answers you right away. Writing and anything that belongs to an account need a personal token. Accounts are given by invitation.
Nothing the API returns is legal advice. Every answer is a statement about a model of a license, not about the license text.
The records the API returns are published under CC BY 4.0. Credit them as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license a record describes belongs to its publisher. Licensing says what else is under which license.
The ten documented operations are unchanged: their paths, parameter names, parameter types, defaults and response keys stay as they were published, and everything added since is additive.