Skip to content

All public APIs — page 87

Every API in the directory, 4,162 in all, best documented first.

smart-me

IoT

With the smart-me REST API you get Access to all your devices in the smart-me Cloud and you can add your own devices. So its an easy way to add the smart-me Cloud support to your Hardware or Software Product.

HTTP Basic64 endpoints

Avaza API Documentation

Documents & Productivity

Welcome to the autogenerated documentation & test tool for Avaza's API. <br/><br/><strong>API Security & Authentication</strong><br/>Authentication options include OAuth2 Implicit and Authorization Code flows, and Personal Access Token. All connections should be encrypted over SSL/TLS <br/><br/>You can set up and manage your api authentication credentials from within your Avaza account. (requires Administrator permissions on your Avaza account).<br/><br/> OAuth2 Authorization endpoint: https://any.avaza.com/oauth2/authorize <br/>OAuth2 Token endpoint: https://any.avaza.com/oauth2/token<br/>Base URL for subsequent API Requests: https://api.avaza.com/ <br/><br/>Blogpost about authenticating with Avaza's API: https://www.avaza.com/avaza-api-oauth2-authentication/ <br/>Blogpost on using Avaza's webhooks: https://www.avaza.com/avaza-api-webhook-notifications/<br/>The OAuth flow currently issues Access Tokens that last 1 day, and Refresh tokens that last 180 days<br/>The Api respects the security Roles assigned to the authenticating Avaza user and filters the data return appropriately. <br/><br><strong>Support</strong><br/>For API Support, and to request access please contact Avaza Support Team via our support chat. <br/><br/><strong>User Contributed Libraries:</strong><br/>Graciously contributed by 3rd party users like you. <br/>Note these are not tested or endorsesd by Avaza. We encourage you to review before use, and use at own risk.<br/> <ul><li> - <a target='blank' href='https://packagist.org/packages/debiprasad/oauth2-avaza'>PHP OAuth Client Package for Azava API (by Debiprasad Sahoo)</a></li></ul>

OAuth86 endpoints

Upstash

Development

Serverless Redis, Kafka and vector database with REST APIs

API keyCORS

API Pro Santé Connect

Government

L‘API Pro Santé Connect permet à des administrations, des éditeurs de logiciels ou des entreprises d’ajouter un bouton Pro Santé Connect, pour recueillir des données d’identité fiables et ainsi identifier les utilisateurs de leur service en ligne (en vue d’une entrée en relation ou connexion). ### À quoi sert cette API ? Pro Santé Connect est un Fédérateur de Fournisseurs d’identité (FFI) au standard OpenID. Il accepte comme « credential » d’authentification la carte CPS et l'application mobile e-CPS. L’assertion d’authentification OpenID Connect « remonte » au Fournisseur de Service (FS) demandeur de l’authentification les traits d’identités classiques plus l’identité sectorielle (profession, savoir-faire, situation d’exercice, …) afin que celui-ci puisse, au-delà de la simple authentification, gérer tout ou partie de son contrôle d’accès. Ces éléments sont fournis par [notre annuaire](https://annuaire.esante.gouv.fr) et incorporés dans le jeton OpenID Connect. ### Données disponibles dans l'API | Type | Données | | -------------------- | -------------------------------------------------------- | | Identifiant national | RPPS | | Données sectorielles | type d'activité (salarié ou libéral) et lieu d'activité. | [Lien des documentations supplémentaires](https://industriels.esante.gouv.fr/produits-et-services/pro-sante-connect/documentation-technique) ### Partenaire de l'API Ministère des Solidarités et de la Santé (MSS)

Restricted access

groov View Public API

IoT

#### Revised: 2019-11-21 ### Overview groov View Public API revision 1.

API key10 endpoints

Taxamo

Payments

Taxamo’s elegant suite of APIs and comprehensive reporting dashboard enables digital merchants to easily comply with EU regulatory requirements on tax calculation, evidence collection, tax return creation and data storage.

API key36 endpoints

Branded Fares Upsell

Transportation

Before using this API, we recommend you read our **[Authorization Guide](https://developers.amadeus.com/self-service/apis-docs/guides/authorization-262)** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, if you are not returning any results try with big cities/airports like LON (London) or NYC (New-York).

No auth1 endpoints

Edamam

Health

Food and nutrition data API with recipe search

API key

PipeDream

Development

Pipedream is the fastest way to build powerful applications that connect all the services in your stack

OAuth

Rudder API

Development

Download OpenAPI specification: [openapi.yml](openapi.yml) # Introduction Rudder exposes a REST API, enabling the user to interact with Rudder without using the webapp, for example in scripts or cronjobs. ## Versioning Each time the API is extended with new features (new functions, new parameters, new responses, ...), it will be assigned a new version number. This will allow you to keep your existing scripts (based on previous behavior). Versions will always be integers (no 2.1 or 3.3, just 2, 3, 4, ...) or `latest`. You can change the version of the API used by setting it either within the url or in a header: * the URL: each URL is prefixed by its version id, like `/api/version/function`. ```bash # Version 10 curl -X GET -H "X-API-Token: yourToken" https://rudder.example.com/rudder/api/10/rules # Latest curl -X GET -H "X-API-Token: yourToken" https://rudder.example.com/rudder/api/latest/rules # Wrong (not an integer) => 404 not found curl -X GET -H "X-API-Token: yourToken" https://rudder.example.com/rudder/api/3.14/rules ``` * the HTTP headers. You can add the **X-API-Version** header to your request. The value needs to be an integer or `latest`. ```bash # Version 10 curl -X GET -H "X-API-Token: yourToken" -H "X-API-Version: 10" https://rudder.example.com/rudder/api/rules # Wrong => Error response indicating which versions are available curl -X GET -H "X-API-Token: yourToken" -H "X-API-Version: 3.14" https://rudder.example.com/rudder/api/rules ``` In the future, we may declare some versions as deprecated, in order to remove them in a later version of Rudder, but we will never remove any versions without warning, or without a safe period of time to allow migration from previous versions. <h4>Existing versions</h4> <table> <thead> <tr> <th style="width: 20%">Version</th> <th style="width: 20%">Rudder versions it appeared in</th> <th style="width: 70%">Description</th> </tr> </thead> <tbody> <tr> <td class="code">1</td> <td class="code">Never released (for internal use only)</td> <td>Experimental version</td> </tr> <tr> <td class="code">2 to 10 (deprecated)</td> <td class="code">4.3 and before</td> <td>These versions provided the core set of API features for rules, directives, nodes global parameters, change requests and compliance, rudder settings and system API</td> </tr> <tr> <td class="code">11</td> <td class="code">5.0</td> <td>New system API (replacing old localhost v1 api): status, maintenance operations and server behavior</td> </tr> <tr> <td class="code">12</td> <td class="code">6.0 and 6.1</td> <td>Node key management</td> </tr> <tr> <td class="code">13</td> <td class="code">6.2</td> <td><ul> <li>Node status endpoint</li> <li>System health check</li> <li>System maintenance job to purge software [that endpoint was back-ported in 6.1]</li> </ul></td> </tr> <tr> <td class="code">14</td> <td class="code">7.0</td> <td><ul> <li>Secret management</li> <li>Directive tree</li> <li>Improve techniques management</li> <li>Demote a relay</li> </ul></td> </tr> <tr> <td class="code">15</td> <td class="code">7.1</td> <td><ul> <li>Package updates in nodes</li> </ul></td> </tr> <tr> <td class="code">16</td> <td class="code">7.2</td> <td><ul> <li>Create node API included from plugin</li> <li>Configuration archive import/export</li> </ul></td> </tr> </tbody> </table> ## Response format All responses from the API are in the JSON format. ```json { "action": "The name of the called function", "id": "The ID of the element you want, if relevant", "result": "The result of your action: success or error", "data": "Only present if this is a success and depends on the function, it's usually a JSON object", "errorDetails": "Only present if this is an error, it contains the error message" } ``` * __Success__ responses are sent with the 200 HTTP (Success) code * __Error__ responses are sent with a HTTP error code (mostly 5xx...) ## HTTP method Rudder's REST API is based on the usage of [HTTP methods](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.ht

API key134 endpoints

adsbdb

Transportation

Open access to aircraft, airline, and flight route data

No authCORS

DigitalNZ API

Open Data

OpenAPI specification of DigitalNZ's Record API. For more information about the API see [digitalnz.org/developers](https://digitalnz.org/developers). To learn more about the metadata/fields used in the API see the [Metadata Dictionary](https://docs.google.com/document/pub?id=1Z3I_ckQWjnQQ4SzpORbClcIXUheO-Jd4jt-oZFuMcoQ). To get a sense of what content is available via the API take a look at the search feature on the [DigitalNZ website](https://digitalnz.org/records?text=all%20sorts&tab=Images). The [terms of use](https://digitalnz.org/about/terms-of-use/developer-api-terms-of-use) specify how developers can use the DigitalNZ API.

API key3 endpoints

SIGNL4 API

Messaging

<p>Use our API for systems integration or to build your own use cases. Sample scenarios include but are not limited to:</p><ul><li>2-way integration: Triggering of Signls and updates in the third party systems when alert state changes occur</li><li>Retrieving alarms for logging purposes</li><li>Calendar integrations: Creation and management of on-call duties</li><li>Punch users in and out based on external calendars</li><li>etc.</li></ul><p>AUTHENTICATION<br>Using the API requires an API key, which you can generate in the SIGNL4 portal under 'Developers'.<br>This key must then be specified in a special header in every HTTP request.<br>This header is called <b style='color:#F8B41F'>X-S4-Api-Key</b>.<br><br>The base URL of the API is <a rel='noopener noreferrer' target='_blank' href='https://connect.signl4.com/api/'>https://connect.signl4.com/api/</a>.<br>Copyright © Derdack GmbH<br></p>

OAuth101 endpoints

Jobicy

Jobs

Remote Jobs API Feed

No auth

API Aides Territoires

Government

Aides Territoires est un moteur de recherche qui permet de retrouver près de 3000 dispositifs d'aides publiques existants en fonction du territoire. Ces aides proviennent de plus de 600 porteurs : * collectivités territoriales ; * agences ou établissements publics ; * partenaires du secteur privé. ### À quoi sert l’API Aides Territoires ? Elle permet en tant que réutilisateur de données de récupérer les aides et leurs critères disponibles sur Aides-territoires. ### Alimenter l'API ? Pour garantir une information de qualité, Aides-territoires s’appuie sur les données référencées par les porteurs d’aides financières et d’ingénierie et les animateurs locaux, après la [création d'un compte](https://aides-territoires.beta.gouv.fr/comptes/inscription/) porteur sur Aides-territoires. Si le porteur dispose déjà d’une base de données structurée et porte de nombreux dispositifs, Aides Territoires met en place un flux automatique. [Contacter l'équipe](mailto:[email protected]) pour plus d'informations. ### Quelles sont les données contenues dans l'API Aides Territoires ? On retrouve - entre autres - pour chaque dispositif d'aide répertorié : | Nom de la donnée | Description | | ---------------------- | --------------------------------- | | Porteur | Qui propose cette aide ? | | Description | Description de l'aide existante | | Nature | Par exemple : aide financière | | Zone géographique | Zone couverte par le dispositif | | Critères d'éligibilité | Les conditions pour en bé

No auth

Arbeitsamt

Jobs

API for the "Arbeitsamt", which is a german Job board aggregator

OAuth

City, Helsinki

Government

Helsinki(FI) City Open Data

No auth

KYC API Documentation

Finance

API Interface to retrieve company data and products from business registers

API key54 endpoints

Gun Policy

Government

International firearm injury prevention and policy

API key

Deal API

Shopping

<span class="tablenote"><b>Note:</b> This is a <a href="https://developer.ebay.com/api-docs/static/versioning.html#limited" target="_blank"> <img src="/cms/img/docs/partners-api.svg" class="legend-icon partners-icon" title="Limited Release" alt="Limited Release" />(Limited Release)</a> API available only to select developers approved by business units.</span><br /><br />This API allows third-party developers to search for and retrieve details about eBay deals and events, as well as the items associated with those deals and events.

OAuth4 endpoints

Erskine May API

Open Data

An API that allows querying of Erskine May data.

No auth11 endpoints

versionhistory.googleapis.com API

Analytics

Version History API - Prod

No auth4 endpoints

Delta Lake

Cloud Storage & File Sharing

Open-source storage framework enabling Lakehouse architecture with Spark, PrestoDB, Flink, Trino, Hive, and APIs

No auth

FullHunt

Security

Searchable attack surface database of the entire internet

API key

More categories