An administrative API to manage the api.data.gov service.

description: The data.gov catalog is powered by CKAN, a powerful open source data platform that includes a robust API. Please be aware that data.gov and the data.gov CKAN API only contain metadata about datasets. This metadata includes URLs and descriptions of datasets, but it does not include the actual data within each dataset.; abstract: The data.gov catalog is powered by CKAN, a powerful open source data platform that includes a robust API. Please be aware that data.gov and the data.gov CKAN API only contain metadata about datasets. This metadata includes URLs and descriptions of datasets, but it does not include the actual data within each dataset.

This list contains the government API cases collected, cleaned and analysed in the APIs4DGov study "Web API landscape: relevant general purpose ICT standards, technical specifications and terms".

The list does not represent a complete list of all government cases in Europe, as it is built to support the goals of the study and is limited to the analysis and data gathered from the following sources:

• The EU open data portal

• The European data portal

• The INSPIRE catalogue

• JoinUp: The API cases collected from the European Commission JoinUp platform

• Literature-document review: the API cases gathered from the research activities of the study performed till the end of 2019

• ProgrammableWeb: the ProgrammableWeb API directory

• Smart 2015/0041: the database of 395 cases created by the study ‘The project Towards faster implementation and uptake of open government’ (SMART 2015/0041).

• Workshops/meetings/interviews: a list of API cases collected in the workshops, surveys and interviews organised within the APIs4DGov

Each API case is classified accordingly to the following rationale:

• Unique id: a unique key of each case, obtained by concatenating the following fields: (Country Code) + (Governmental level) + (Name Id) + (Type of API)

• API Country or type of provider: the country in which the API case has been published

• API provider: the specific provider that published and maintain the API case

• Name Id: an acronym of the name of the API case (it can be not unique)

• Short description

• Type of API: (i) API registry, a set, catalogue, registry or directory of APIs; (ii) API platform: a platform that supports the use of APIs; (iii) API tool: a tool used to manage APIs; (iv) API standard: a set of standards related to government APIs; (v) Data catalogue, an API published to access metadata of datasets, normally published by a data catalogue; (vi) Specific API, a unique (can have many endpoints) API built for a specific purpose

• Number of APIs: normally only one, in the case of API registry, the number of APIs published by the registry at the 31/12/2019

• Theme: list of domains related to the API case (controlled vocabulary)

• Governmental level: the geographical scope of the API (city, regional, national or international)

• Country code: the country two letters internal code

• Source: the source (among the ones listed in the previous) from where the API case has been gathered

CPSC provides accessibility to recalls via a recall database. The information is publicly available to consumers and businesses as well as software and application developers.

Website and API containing the daily Federal Register.

The Houses of the Oireachtas are providing these APIs to allow our datasets to be retrieved and reused as widely as possible. They are intended to be used in conjunction with https://data.oireachtas.ie, from where our datasets can be accessed directly. By using the APIs, users can make metadata queries to identify the specific data they require. New data are available through the API as soon as they are published. Currently, https://data.oireachtas.ie contains data in XML format from the Official Report of the Houses of the Oireachtas (the “debates”) and replies to Parliamentary Questions in XML files complying with the Akoma Ntoso schema, as well data in PDF format for Bills, Acts and other documents published by the Houses of the Oireachtas. Files can be retrieved from https://data.oireachtas.ie by adding the URI fragment contained in the “formats” fields of the JSON documents returned by these APIs. At the moment only PDF and XML files are available directly from https://data.oireachtas.ie, but this will become the endpoint for direct access of all “uri” fields in the data queried through https://api.oireachtas.ie. We will also be making bulk downloads available through https://data.oireachtas.ie.

A dataset of all the meta-data for all of the datasets available through the data.gov.uk service. This is provided as a zipped CSV or JSON file. It is published nightly.

Updates: 27 Sep 2017: we've moved all the previous dumps to an S3 bucket at https://dgu-ckan-metadata-dumps.s3-eu-west-1.amazonaws.com/ - This link is now listed here as a data file.

From 13/10/16 we added .v2.jsonl dump, which is set to replace the .json dump (which will be discontinued after a 3 month transition). This is produced using 'ckanapi dump'. It provides an enhanced version of each dataset ('validated', or what you get from package_show in CKAN API v3 - the old json was the unvalidated version). This now includes full details of the organization the dataset is in, rather than just the owner_id. Plus it includes the results of the archival & qa for each dataset and resource, showing whether the link is broken, detected format and stars of openness. It also benefits from being json lines http://jsonlines.org/ format, so you don't need to load the whole thing into memory to parse the json - just a line at a time.

On 12/1/2015 the organizations of the CSV was changed:

• Before this date, each dataset was one line, and resources added as numbered columns. Since a dataset may have up to 300 resources, it ends up with 1025 columns, which is wider than many versions of Excel and Libreoffice will open. And the uncompressed size of 170Mb is more than most will deal with too. It is suggested you load it into a database, ahandle it with a python or ruby script, or use tools such as Refine or Google Fusion Tables.

• After this date, the datasets are provided in one CSV and resources in another. On occasions that you want to join them, you can join them using the (dataset) "Name" column. These are now manageable in spreadsheet software.

You can also use the standard CKAN API if you want to search or get a small section of the data. Please respect the traffic limits in the API: http://data.gov.uk/terms-and-conditions

The Federal Procurement Data System (FPDS) Next Generation has been re-engineered as a real-time federal enterprise information system. Web services based on SOAP and XML, implemented using Java technologies, are used in FPDS-NG to provide interoperability with various federal procurement systems

The Tax Rate API is used by Find a Sales and Use Tax rate and other web applications to determine the tax rate or rates.

When a California address or coordinate is sent in a request to the API, this returns the tax rate and other codes, based on a GIS map in a response.

The API does not validate addresses. Always enter a valid address or use an address validator before sending the address to the API.

https://services.gis.boe.ca.gov/api/taxrates/Rates.svc

See also REST API https://services.maps.cdtfa.ca.gov/

Terms of Us https://www.cdtfa.ca.gov/use.htm

The data.gov.ie API

Data.gov.ie is built using CKAN v2.2 (link is external), which provides a powerful API that allows developers to retrieve datasets, groups or other CKAN objects and search for datasets. There is full documentation (link is external) available for the CKAN API online.

Example API Calls

Get JSON-formatted lists of a site’s datasets or other CKAN objects: data.gov.ie/api/3/action/package_list data.gov.ie/api/3/action/tag_list Get a full JSON representation of a dataset, resource or other object: data.gov.ie/api/3/action/package_show?id=the-walled-towns-of-ireland data.gov.ie/api/3/action/tag_show?id=marine Search for packages or resources matching a query: data.gov.ie/api/3/action/package_search?q=museum data.gov.ie/api/3/action/resource_search?query=name:The%20Walled%20Towns%20of%20Ireland

More information at https://data.gov.ie/developers

NOTE: This dataset is not maintained. This note was added on the 4th of October 2024 and any resources with dead links removed. For API guidance from the Government Chief Digital Officer (GCDO) please check https://www.digital.govt.nz/standards-and-guidance/technology-and-architecture/application-programming-interfaces-apis and email GCDO@dia.govt.nz for more information. This is a convenient place for the Service Innovation team to keep track of APIs we discover across the New Zealand Government that we find useful for our work (which involves collaborating with agencies to design and deliver new services and reusable components.) We don’t run or have responsibility for these APIs. We just want to make them easier to find. If you know more APIs please contact us. This is a short-term exercise and we plan to use what we learn (from collecting and sharing information about APIs and reusable components) to inform future approaches to making it easier for people to discover and use APIs and platforms. Where possible we have linked to the landing page for the API and not directly to the end point API itself – this is so you can get the latest context and information about the API before you use it.

The linked data API for National Composite Gazetteer of Australia. Uses linked data principles to provide Human readable and machine readable resources for data sharing and linking. Includes alternate views for machine readable services, and links to vocab resources, as well as a landing page map for visualisation. Link: http://linked.data.gov.au/dataset/placenames The linked data API for National Composite Gazetteer of Australia. Uses linked data principles to provide Human readable and machine readable resources for data sharing and linking. Includes alternate views for machine readable services, and links to vocab resources, as well as a landing page map for visualisation. Link: http://linked.data.gov.au/dataset/placenames

This Choose Work webpage provides access to a tool for doing a direct search for Ticket to Work service providers by zip code. It functions similarly to a web based API.

Envirofacts integrates information from a variety of EPA's environmental databases. Each of these databases contains information about facilities that are required to report activity to a state or federal system. Using this API, you can retrieve information.

The FTA Portal is an Australian Government Department of Foreign Affairs and Trade (DFAT) initiative. The Portal enables users to explore how importers and exporters can benefit from Australia’s Free Trade Agreements.\r \r The API service of the FTA Portal provides third party organisations and systems access to the same data and functionality that enables the website. The API has been made available to encourage users to find new ways to use, display and share data relating to the Australia's Free Trade Agreements.\r \r We welcome queries about the FTA Portal API and feedback from interested parties to FTAportalfeedback@dfat.gov.au.

Military Facilities. The dataset contains locations and attributes of Military Facilities, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Information researched by the DC Office of the Chief Technology Officer identified Military Facilities and DC GIS staff geo-processed the data.

Split the city's report data into smaller statistical units such as valid subcategories, locate the data with a fixed rule independent URL, provide JSON transmission format for different applications or software to collect and integrate data.

Look up VA forms and check for new versions. Our goal is to make it easier to keep up with the ever-changing landscape of VA forms. This API indexes data sourced from VA.gov, creating unique hashes for each version of a form and allowing quick lookup. The documentation is hosted by Lighthouse, a Veteran-centered API platform for securely accessing VA data.

The SaferBus API is a RESTful service API provided by FMCSA for the purpose of making available, the safety performance data of U.S. Department of Transportation (U.S. DOT) registered bus companies. The primary goal is to encourage the development of products, tools or services that can help consumers more easily check the safety record of bus companies to avoid those that have been placed out of service or those that do not have the proper operating authority.

This API accesses QLD Government's MapsOnline service that integrates, summarises, presents and delivers spatially-referenced information as map and report products. Responses are returned via the specified email address once processed. There are supporting functions that retrieve the available report and feature types.

The primary request report function has separate GET and POST end points:

GET or POST https://mapsonline.information.qld.gov.au/service/environment/resource/MapsOnline/1/http/rest/request

** Parameters:**

• reportType: any type in getReportTypes

• featureType: any type in getFeatureTypes

• features: any valid feature, e.g. a coordinate as -27,150, a lot plan as 1,RP1 or GeoJson. Geometries must fall within Queensland and have a total bounding box of less than 200,000km2. Multiple pipe seperated features can be included in a single request, e.g. -27,150|-26,149|-23,148

• emailAddress: any valid email address

• customerReference: (optional) - include your own file reference

Example Valid Request https://mapsonline.information.qld.gov.au/service/environment/resource/MapsOnline/1/http/rest/request?reportType=VEG1L&featureType=LotPLan&features=1,RP1&emailAddress=OpenData@example.com

{
  message: "Report Requested",
  message_code: "success",
  output: [ ],
  status: 200,
  success: true
}

Example Invalid Request https://mapsonline.information.qld.gov.au/service/environment/resource/MapsOnline/1/http/rest/request?reportType=VEG1C&featureType=coord&features=160,-27&emailAddress=OpenData@example.com

{
  message: "Report request failed",
  message_code: "input_validation",
  output: [
    "Coordinates outside of Queensland"
  ],
  status: 200,
  success: false
}

BioMaps and WetlandMaps provide map interfaces to request some reports available in this API