Laws, publications, statistics, status and other public resources can be found through stable identifiers.
Public APIs
Documented interfaces can expand transparency, verification and reuse without turning an API into a source of authority or opening data that is not public.
What a public API should enable
Public interfaces are used to query and verify information already authorized for disclosure. They expand access and interoperability, but do not become a legal source merely by displaying or transmitting data.
Responses should make it possible to relate data to the competent source, version and time of update.
Documented formats and contracts reduce dependency on a single interface or implementation.
Public interface contract
| Dimension | Expected public rule |
|---|---|
| Versioning | Identifiable versions, documented changes and predictable transition. |
| Availability | Targets should be published only when verifiable operational measurement exists. |
| Limits | Documented request limits and abuse protection without arbitrary discrimination. |
| Authentication | Public queries without credentials when the data is already public; authentication when personal or restricted scope is involved. |
| Privacy | A public API does not convert personal or classified data into open data. |
| Provenance | The response must point to the responsible institutional source. |
Format examples — not yet available as a service
The paths above are organisational examples. They do not mean these addresses are published or available today.
The portal contains data and verification structures, but the current public version does not present a production Candeia API or measured service levels.