The following are the specifications for the APIs to be implemented at the Health Repository end if an entity is only serving the role of a HIU. The specs are essentially duplicates from the Gateway and Bridge, but put together so as to make it clear to *HIUs* which set of APIs they should implement to participate in the network. 1. The APIs are organized by the flows - **identification**, **consent flow**, **data flow** and **monitoring**. They represent the APIs that are expected to be available at the HIU end by the Gateway. 2. For majority of the APIs, if Gateway has initiated a call, there are corresponding callback APIs on the Gateway. e.g for **/consents/hiu/notify** API on HIU end, its expected that a corresponding callback API **/consents/hiu/on-notify** on Gateway is called. Such APIs are organized under the **Gateway** label. 3. Gateway relevant APIs for HIUs are grouped under **Gateway** label. These include the APIs that HIPs are required to call on the Gateway. For example, to request a CM for consent, HIU would call **/consent-requests/init** API on gateway. 4. **NOTE**, in some of the API documentations below, **X-HIP-ID** is mentioned in header (for example in /auth/on-init). These are the cases, when a particular API is applicable for both HIU and HIP (e.g an entity is playing the role of HRP representing both HIU and HIP). If you are only playing the role of HIP, then only X-HIU-ID header will be sent

APIs for Interacting with NTP1 Tokens & The Neblio Blockchain

A web service for near earth objects. All the data is from the NASA JPL Asteroid team. NeoWs is proud to power AsteroidTracker on iOS and Android as well as related apps. Follow us on Twitter

API to access NetBox

The Labs64 NetLicensing RESTful API gives you access to NetLicensing’s core features.

Authentication
You authenticate to the NetLicensing API by providing your account credentials or simply use our demo account - demo:demo

Find out more about Labs64 NetLicensing at netlicensing.io

The general-purpose API

The interface to our OAuth2 server

The entry point to user-specific information

Audio recommendations tailored to a user's preferences

Sponsorship for non-NPR One client applications

Allows clients to look up NPR member station information

The Buildings Database is a shared resource for the building industry. The Database, developed by the U.S. Department of Energy and the National Renewable Energy Laboratory (NREL), is a unique central repository of in-depth information and data on high-performance, green building projects across the United States and abroad.

Query our database of federal and state laws and incentives for alternative fuels and vehicles, air quality, fuel efficiency, and other transportation-related topics. This dataset powers the Federal and State Laws and Incentives on the Alternative Fuels Data Center.

This API allows programmers to build National Snow and Ice Data Center data and metadata services into their applications.

The Archive API provides lists of NYT articles by month going back to 1851. You can use it to build your own local database of NYT article metadata.

With the Article Search API, you can search New York Times articles from Sept. 18, 1851 to today, retrieving headlines, abstracts, lead paragraphs, links to associated multimedia and other article metadata. Note: In URI examples and field names, italics indicate placeholders for variables or values. Brackets [ ] indicate optional items. Parentheses ( ) are not a convention — when URIs include parentheses, interpret them literally.

The Books API provides information about book reviews and The New York Times bestsellers lists.

Get access to comments from registered users on New York Times articles. NOTE: This API is deprecated.