Government platforms
A list of common registers, components and open APIs used by governments around the world
License
Creative Commons Attribution Share-Alike 4.0
Publisher
The Platform Government Initiative
Update frequency
Bi-monthly
Files
| Name | Format | Description | Data | Download | |
|---|---|---|---|---|---|
| common-components | text/csv | Common components and APIs | View | Download | |
| trust-and-consent | text/csv | Trust and consent | View | Download | |
| registers | text/csv | Registers | View | Download |
Submission guidelines and definitions
The definition of a platform is fuzzy, so, if in doubt, please raise a ticket on github.
There are three categories of platform:
Common components and APIs- cross-government components (such as payment systems or analytics platforms) and APIs that expose the business rules of government (e.g. apply for a fishing license)Trust and consent- cross-government authentication and identity systems, key management and data exchange systemsRegisters- canonical datasets used by multiple government services
The key thing is that all of the above should be in use across a government or city, not within a single agency.
Field definitions
The IsSelfService should be set to 'True' if it is possible for a user to start using the platform immediately (e.g. in a sandbox mode).
DoumentationUrl should be a valid URL for any documentation on how developers or administrators should use the platform.
HasCodeLibraries should be set to 'True' if there are public code samples for integrating with the platform.
OrganisationName should be the organisation responsible for maintaining and operating the platform.
Last update: 2019-06-03 at 14:52