This API provides live access to the CKAN portion of the Open Government Portal and Registry systems. ### Portal: https://open.canada.ca * Our public data portal * Includes data federated from provinces and municipalities * Read-only API calls can be made without an API key * Authorization required only for publishing federated data ### Registry: https://registry.open.canada.ca * Accessible within the Government of Canada (GoC) network for collecting and publishing data from GoC departments * New datasets must be manually reviewed and approved by the Open Government team * Publishes approved datasets to the Production Portal automatically * User account or API key required for all operations

These recommendations are intended as a general policy to be applied alongside the strategic policies, principles and guidelines that often guide ICT and service development in cities. From a technological and service-oriented standpoint, the significance of APis is, mostly due to accelerating digitalisation, increasing at such a pace that a need has emerged for a document that describes the importance of APIs and the goals related to them from the perspective of the cities.

This document presents the consolidated view of the Six largest cities in Finland on how to develop open APIs through inter-city cooperation. The Six cities are Helsinki, Espoo, Vantaa, Tampere, Turku and Oulu.

This portal is intended to serve as a means to access all available NMED data via secure Application Programming Interface (API).

To access our data, we require that you register with the portal.

You can browse the titles and a short description of our available APIs before registering.

Anyone who registers will be provided access to all of NMED’s public APIs.

Members of the regulated community served by NMED, as well as partner agencies and other official entities, can, during registration, request an elevated account that provides access to certain protected data APIs. Such requests will need to register using an official email account and potentially provide other means of verification before these account requests are approved.

Once registered, you will be able to fully explore and consume our collection of APIs, and access Open API Specification documentation that will help you understand, learn, and leverage those APIs for your purposes.

We hope you enjoy your visit to the NMED Open Data Portal and return many times.

The TransLoc Public API is a RESTful API which allows you to incorporate real-time vehicle tracking information into your web or mobile applications. It exposes several resources that allow you to access real-time information about transit systems tracked by TransLoc Inc. Following the REST principles, all the resources available through this API are located at specific URLs. You should use GET requests to access the resources behind the URLs. In all cases, if your request was successfully processed the HTTP status code will be returned as 200 OK. If an error occurs, an appropriate 400 or 500 level error will be returned, with the body of the response containing a plain text user-friendly error message.

Data.public.lu provides all its metadata in the DCAT and DCAT-AP formats, i.e. all data about the data stored or referenced on data.public.lu. DCAT (Data Catalog Vocabulary) is a specification designed to facilitate interoperability between data catalogs published on the Web. This specification has been extended via the DCAT-AP (DCAT Application Profile for data portals in Europe) standard, specifically for data portals in Europe. The serialisation of those vocabularies is mainly done in RDF (Resource Description Framework). The implementation of data.public.lu is based on the one of the open source udata platform. This API enables the federation of multiple Data portals together, for example, all the datasets published on data.public.lu are also published on data.europa.eu. The DCAT API from data.public.lu is used by the european data portal to federate its metadata. The DCAT standard is thus very important to guarantee the interoperability between all data portals in Europe. Usage Full catalog You can find here a few examples using the curl command line tool: To get all the metadata from the whole catalog hosted on data.public.lu curl https://data.public.lu/catalog.rdf Metadata for an organization To get the metadata of a specific organization, you need first to find its ID. The ID of an organization is the last part of its URL. For the organization "Open data Lëtzebuerg" its URL is https://data.public.lu/fr/organizations/open-data-letzebuerg/ and its ID is open-data-letzebuerg. To get all the metadata for a given organization, we need to call the following URL, where {id} has been replaced by the correct ID: https://data.public.lu/api/1/organizations/{id}/catalog.rdf Example: curl https://data.public.lu/api/1/organizations/open-data-letzebuerg/catalog.rdf Metadata for a dataset To get the metadata of a specific dataset, you need first to find its ID. The ID of dataset is the last part of its URL. For the dataset "Digital accessibility monitoring report - 2020-2021" its URL is https://data.public.lu/fr/datasets/digital-accessibility-monitoring-report-2020-2021/ and its ID is digital-accessibility-monitoring-report-2020-2021. To get all the metadata for a given dataset, we need to call the following URL, where {id} has been replaced by the correct ID: https://data.public.lu/api/1/datasets/{id}/rdf Example: curl https://data.public.lu/api/1/datasets/digital-accessibility-monitoring-report-2020-2021/rdf Compatibility with DCAT-AP 2.1.1 The DCAT-AP standard is in constant evolution, so the compatibility of the implementation should be regularly compared with the standard and adapted accordingly. In May 2023, we have done this comparison, and the result is available in the resources below (see document named 'udata 6 dcat-ap implementation status"). In the DCAT-AP model, classes and properties have a priority level which should be respected in every implementation: mandatory, recommended and optional. Our goal is to implement all mandatory classes and properties, and if possible implement all recommended classes and properties which make sense in the context of our open data portal.

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

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

This dataservice is deprecated.

The REST API is one of the ways to access the EU Open Data Portal. Under API are available the portal core functionalities. This encompasses all you can do with the web interface. The information retrieved can thus be used by external code that calls the portal API.

The application used by the EU Open Data Portal for the API is CKAN. You can find useful documentation about the API at the CKAN On whose website.

JSON is the used message format (specified in RFC 4627) for communication. If you want to use the REST API in your application, you can check the following examples.

All of the tabular data sets in Camden's Open Data portal can be accessed via SODA (Socrata Open Data API). This is a basic tutorial on what's needed to access and get data from the API.

Getting comfortable with APIs by: understanding how they work; learn how they are used; and gain experience using them.

Norges Bank’s open data API provides machine access to selected statistics such as interest rates and exchange rates published by the bank. The service is implemented as a REST programming interface where one can formulate queries against the bank’s datasets and extract statistics in a variety of formats. The service can be used freely and requires no authentication.

The Victorian Government Open Data Directory uses CKAN to surface thousands of datasets from across the Victorian Government. This API is based on version 2.7.3 of the CKAN API documentation and …Show full descriptionThe Victorian Government Open Data Directory uses CKAN to surface thousands of datasets from across the Victorian Government. This API is based on version 2.7.3 of the CKAN API documentation and provides access to CKAN functionality for the purpose of integrating with other CKAN instances. It can also be used as a data source for other applications to search and download the datasets provided by Data.Vic. This API is the updated version that implements the Whole of Victorian Government API Design Standards for RESTful APIs developed by the Victorian Government.

API of NASA held and pending patents.

Teoston keräämä livemusiikkidata on Suomen suurin ja kattavin. Nyt avoimen rajapinnan kautta avatussa datassa on kaikki Teostolle ilmoitetut, Suomessa viime vuonna (2014) järjestetyt livekeikat: keikkojen ajankohdat, keikkapaikat paikkatietoineen ja koordinaatteineen, esiintyjät, esitetyt biisit ja sekä biisien tekijätiedot.

Haastamme kehittäjät rikastamaan livemusiikin paikkatietodataa ja kehittämään sille uusia, innovatiivisia käyttömahdollisuuksia. Esimerkkejä datan rikastamisesta ovat muiden avointen paikkatietoaineistojen yhdistäminen tapahtumadataan tai musiikkiin liittyvän metadatan yhdistäminen biisikohtaiseen tietoon.

Livedatan kehittäminen on mukana Open Finland Challenge -kilpailussa ja Ultrahack-tapahtumassa.

This endpoint structures the APOD imagery and associated metadata so that it can be repurposed for other applications. In addition, if the concept_tags parameter is set to True, then keywords derived from the image explanation are returned. These keywords could be used as auto-generated hashtags for twitter or instagram feeds; but generally help with discoverability of relevant imagery.

The Victorian Government's open data portal, data.vic, uses CKAN to surface thousands of data sets and metadata records from across the Victorian Government.\r \r This API is based on version 2.7.3 of the CKAN API documentation and provides access to CKAN functionality for the purpose of integrating with other CKAN instances. It can also be used as a data source for other applications to search and download the datasets provided by Data.Vic.\r

NASA has released a series of space sounds via sound cloud. We have abstracted away some of the hassle in accessing these sounds, so that developers can play with the audio files.

Information about all the assets on Data.NJ.Gov including information about their API's and how to use them.

All 311 Service Request from 2010 to Present. Starting in November 2011 the data will be updated on a daily basis.

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.