All public APIs — page 55

English video pronunciation search with timestamps, IPA phonetics and subtitle context

### A quoi sert l’API Annonces officielles et comptes annuels des associations ? Afin de faciliter la réutilisation des données, la direction de l’information légale et administrative (DILA) met à disposition une API accessible gratuitement. Cette version de l’API est une version bêta. Elle permet de recueillir vos remarques et vos suggestions d’amélioration ; elle pourra donc évoluer pendant toute la durée du test. Les principales fonctionnalités : - mise à disposition des données Associations et Comptes associations, - lancement d’une requête d’interrogation/filtrage en passant différents paramètres, - prévisualisation des premiers résultats ou téléchargement des données complètes, - nombreuses possibilités de filtrage, - format CSV, JSON, EXCEL, - recherche avec mots-clés, filtres et critères. ### Données disponibles Le jeu de données ASSOCIATIONS - Journal officiel associations et fondations d'entreprise (JOAFE) - publie : **1. Les déclarations de création, modification ou dissolution :** - des associations régies par la loi de 1901 depuis l’origine ; - des associations syndicales de propriétaires depuis 2004 ; - des fondations d’entreprise depuis 1991 ; - des fonds de dotation depuis 2009 ; - des fondations partenariales depuis 2018 ; - des fonds de pérennité depuis 2020. **2. les extraits de décisions de justice afférentes au domaine associatif** Le jeu de données Comptes associations publie les comptes annuels des associations, fondations d’entreprise fondations parten

City of Surrey Traffic Loop Count API.

Open Data

This API provides locations of City of Surrey traffic loops and the corresponding traffic loop counts in 15 minute intervals. While the counts are broken up by 15 minute intervals, the data is currently loaded only once per day. We are hoping to increase this frequency to at least once every hour. The LOOP_ID field is common to both datasets and can be used to cross-reference them.

Le Cerema est le gestionnaire de l’observatoire côtier national de mesure des états de mer, l’observatoire Candhis. Cet observatoire comprend un réseau d’une quarantaine de bouées de mesure temps réel, plus 500 ans de données archivées et un système d’information. Son principal objectif est la promotion de la mesure des états de mer dans le domaine proche côtier et d’assurer la diffusion des données auprès de la communauté scientifique, des professionnels de la mer et du grand public. **L'intégralité des mesures associées à chaque houlographe est accessible via cette API ou sur le site** **[CANDHIS](https://candhis.cerema.fr/)** L'API requiert un jeton d'accès, se référer à la documentation technique. Les points du réseau de mesure CANDHIS sont diffusés [ici](https://www.data.gouv.fr/fr/datasets/candhis-houlographes-de-lobservatoire-cotier-national-de-mesure-in-situ-des-etats-de-mer-france-metropole-et-outre-mer/)  Point de contact : candhis\@cerema.fr

Petfinder is dedicated to helping pets find homes, another resource to get pets adopted

PI Web API 2018 SP1 Swagger Spec

Business

Swagger Spec file that describes PI Web API

Blazemeter API Explorer

Development

Live API Documentation

BizToc

Media

Get the latest business news articles.

Fast and resilient DNS hosting service by Gcore. Improve the performance and availability of your online business.

U.S. EPA Enforcement and Compliance History Online (ECHO) - Resource Conservation and Recovery Act

Open Data

Enforcement and Compliance History Online (ECHO) is a tool developed and maintained by EPA's Office of Enforcement and Compliance Assurance for public use. ECHO provides integrated compliance and enforcement information for over 1 million regulated facilities nationwide. RCRA Rest Services provides multiple service endpoints, each with specific capabilities, to search and retrieve data on hazardous waste handlers/facilities regulated under the Resource Conservation and Recovery Act (RCRA). The returned results reflect data drawn from EPA's RCRAInfo database. \ The get_facilities, get_map, get_qid, and get_download end points are meant to be used together, while the enhanced get_facility_info end point is self contained. The get_facility_info end point returns either an array of state, county or zip clusters with summary statistics per cluster or an array of facilities. \ The recommended use scenario for get_facilities, get_qid, get_map, and get_downoad is: \ <b>1)</b> Use get_facilities to validate passed query parameters, obtain summary statistics and to obtain a query_id (QID). QIDs are time sensitive and will be valid for approximately 30 minutes. <b>2)</b> Use get_qid, with the returned QID, to paginate through arrays of facility results. <b>3)</b> Use get_map, with the returned QID, to zoom in/out and pan on the clustered and individual facility coordinates that meet the QID query criteria. <b>4)</b> Use get_download, with the returned QID, to generate a Comma Separated Value (CSV) file of facility information that meets the QID query criteria. \ \ Use the qcolumns parameter to customize your search results. Use the Metadata service endpoint for a list of available output objects, their Column Ids, and their definitions to help you build your customized output. \ Additional ECHO Resources: <a href="https://echo.epa.gov/tools/web-services">Web Services</a>, <a href="https://echo.epa.gov/resources/echo-data/about-the-data">About ECHO's Data</a>, <a href="https://echo.epa.gov/tools/data-downloads">Data Downloads</a>

Billingo API v3

Finance

This is a Billingo API v3 documentation. Our API based on REST software architectural style. API has resource-oriented URLs, accepts JSON-encoded request bodies and returns JSON-encoded responses. To use this API you have to generate a new API key on our [site](https://app.billingo.hu/api-key). After that, you can test your API key on this page.

ClickMeter API

Business

Api dashboard for ClickMeter API

UniCourt Enterprise APIs

Open Data

<button><a href="/enterpriseapi/download/UniCourt-Enterprise-API-Spec.yaml" >Download UniCourt Enterprise APIs Specification</a></button>

Xero Payroll AU API

Finance

This is the Xero Payroll API for orgs in Australia region.

BulkSMS JSON REST API

Phone

## Overview The JSON REST API allows you to submit and receive [BulkSMS](https://www.bulksms.com/) messages. You can also get access to past messages and see your account profile. The base URL to use for this service is `https://api.bulksms.com/v1`. The base URL cannot be used on its own; you must append a path that identifies an operation and you may have to specify some path parameters as well. [Click here](/developer/) to go to the main BulkSMS developer site. In order to give you an idea on how the API can be used, some JSON snippets are provided below. Have a look at the [messages section](#tag/Message) for more information. Probably the most simple example ``` { "to": "+27001234567", "body": "Hello World!" } ``` You can send unicode automatically using the `auto-unicode` query parameter. Alternatively, you can specify `UNICODE` for the `encoding` property in the request body. Please note: when `auto-unicode` is specified and the value of the `encoding` property is `UNICODE`, the message will always be sent as `UNICODE`. Here is an example that sets the `encoding` explicitly ``` { "to": "+27001234567", "body": "Dobrá práce! Jak se máš?", "encoding": "UNICODE" } ``` You can also specify a from number ``` { "from": "+27007654321", "to": "+27001234567", "body": "Hello World!" } ``` Similar to above, but repliable ``` { "from": { "type": "REPLIABLE" }, "to": "+27001234567", "body": "Hello World!" } ``` A message to a group called Everyone ``` { "to": { "type": "GROUP", "name": "Everyone" }, "body": "Hello World!" } ``` A message to multiple recipients ``` { "to": ["+27001234567", "+27002345678", "+27003456789"], "body": "Happy Holidays!" } ``` Sending more than one message in the same request ``` [ { "to": "+27001234567", "body": "Hello World!" }, { "to": "+27002345678", "body": "Hello Universe!" } ] ``` **The insecure base URL `http://api.bulksms.com/v1` is deprecated** and may in future result in a `301` redirect response, or insecure requests may be rejected outright. Please use the secure (`https`) URI above. ### HTTP Content Type All API methods expect requests to supply a `Content-Type` header with the value `application/json`. All responses will have the `Content-Type` header set to `application/json`. ### JSON Formatting You are advised to format your JSON resources according to strict JSON format rules. While the API does attempt to parse strictly invalid JSON documents, doing so may lead to incorrect interpretation and unexpected results. Good JSON libraries will produce valid JSON suitable for submission, but if you are manually generating the JSON text, be careful to follow the JSON format. This include correct escaping of control characters and double quoting of property names. See the [JSON specification](https://tools.ietf.org/html/rfc4627) for further information. ### Date Formatting Dates are formatted according to ISO-8601, such as `1970-01-01T10:00:00+01:00` for 1st January 1970, 10AM UTC+1. See the [Wikipedia ISO 8601 reference](https://en.wikipedia.org/wiki/ISO_8601) for further information. Specifically, calendar dates are formatted with the 'extended' format `YYYY-MM-DD`. Basic format, week dates and ordinal dates are not supported. Times are also formatted in the 'extended' format `hh:mm:ss`. Hours, minutes and seconds are mandatory. Offset from UTC must be provided; this is to ensure that there is no misunderstanding regarding times provided to the API. The format we look for is `yyyy-MM-ddThh:mm:ss[Z|[+-]hh:mm]` Examples of valid date/times are`2011-12-31T12:00:00Z` `2011-12-31T12:00:00+02:00` ### Entity Format Modifications It is expected that over time some changes will be made to the request and response formats of various methods available in the API. Where possible, these will be implemented in a backwards compatible way. To make this possible you are required to ignore unknown properties. This enables the addition of information in response documents while maintaining compatibility with older c

nFusion Solutions Market Data API

Finance

[nFusion Solutions](https://nfusionsolutions.com) provides [REST APIs](https://nfusionsolutions.com/data-feeds/) that deliver enterprise-grade financial data. Data sets include real-time and historical pricing for Spot prices of precious metals such as Gold, Silver, Platinum, and Palladium, exchange rates for major currency pairs, exchange rates for Crypto Currencies such as BTC, ETH, and LTC. All API access requires authentication. In order to be issued access credentials you must first enter into a service agreement with nFusion Solutions and acquire a commercial license. For information on how to obtain a licence [take a tour of our products](https://nfusionsolutions.com/nfusion-solutions-metals-gold-price-feed-tour/) or email [email protected].

L’API données ouvertes de [l’Éducation Nationale](https://data.education.gouv.fr/) est une API ouverte à tous, qui permet d’accéder à l’ensemble du catalogue de jeux de données publiés sur le portail Open data. ### A quoi sert l’API données ouvertes de l’Éducation Nationale L’API met à disposition l’ensemble des jeux de données publics (non restreints) du catalogue de jeux de données du portail. Cette API est en accès libre. Elle permet à tout le monde de : - Réutiliser les jeux de données publics du portail données ouvertes de l’Éducation Nationale - Bénéficier des données mises à jour directement via l’API qui « appelle » les données du catalogue ### Données disponibles Parmi les principaux jeux de données accessibles via cette API, on peut citer : | Donnée | Lien vers le jeu de données | | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Annuaire de l'éducation | [En savoir plus](https://data.education.gouv.fr/explore/dataset/fr-en-annuaire-education/api/) | | Adresse et géolocalisation des établissements d'enseignement | [En savoir plus](https://data.education.gouv.fr/explore/dataset/fr-en-adresse-et-geolocalisation-etablissements-premier-et-second-degre/api/) | | Calendrier scolaire | [En savoir plus](https://data.education.gouv.fr/explore/dataset/fr-en-calendrier-scolaire/api/) | | Taille

L'[API Sirene](https://portail-api.insee.fr/catalog/api/2ba0e549-5587-3ef1-9082-99cd865de66f?aq=ALL) permet d'interroger le répertoire Sirene des entreprises et des établissements, géré par l'Insee. ### Les données du répertoire Sirene depuis 1973 &#x20; API Sirene donne accès aux informations concernant les entreprises et les établissements enregistrés au répertoire interadministratif Sirene depuis sa création en 1973, y compris les unités fermées. La recherche peut être unitaire, multicritère, phonétique et porter sur les données courantes et historisées. Les services actuellement disponibles interrogent : * les unités légales (siren) * les établissements (siret). *Le service informations* permet de connaître les dates de dernières mises à jour. *Le service Liens de succession* informe sur les prédécesseurs et les successeurs des établissements. Les personnes inscrites au répertoire ayant demandé à bénéficier du **statut de diffusion partielle** conformément à l'article R123-232-1 du code de commerce ne doivent avoir leurs informations personnelles ni rediffusées entièrement, ni utilisées à des fins de prospection. Le *service nonDiffusibles* anciennement proposé est, depuis le 21 mars 2023, plus disponible. La modalité non diffusible "**N**" n’existe plus, et le statut de diffusion des unités antérieurement non diffusibles "N" a été automatiquement converti en statut de diffusion partielle , "**P**". Il n’y a donc plus d’unités non diffusibles "N" dans la base Sirene. De m

Front accounting is multilingual and multicurrency software for small businesses

A free API client that allows you to design, debug, test, and mock APIs locally, on Git, or cloud.

Reputation of IPs, domains, URLs and file hashes from aggregated threat feeds, plus CVE lookups

SERP data from major search engines with a free trial

API Reference - Ideal Postcodes

Geocoding

# Getting Started ## Overview ### Access All API methods are either a `GET`, `POST` or `OPTIONS` request. The API communicates over both HTTPS and plain HTTP using IPv4 and IPv6. We recommend using HTTPS only although HTTP is available. We use appropriate HTTP status codes where possible to indicate the request status. ### Rate Limiting Each IP address is rate limited at 30 requests per second. Tripping the rate limit will result in a 503 response. The autocomplete API also has an additional rate limit. If you expect to breach the limit please contact us and we can move you to an endpoint with a higher limit. ### JSONP [JSONP](http://en.wikipedia.org/wiki/JSONP) requests are supported. Include a `callback=` in your request as a query parameter. Your results return wrapped in a function designated by your request. ## Authentication Most requests require an **API key** for authentication. Authenticate by passing an `api_key` as part of the query string. For example: ``` api.ideal-postcodes.co.uk/v1/autocomplete/addresses?api_key=iddqd&q=parkside ``` Alternatively, authentication can be transmitted via the `Authorization` header using the following scheme: ``` Authorization: api_key="iddqd" [other_key="foo"] ``` ## Versioning This API is versioned with a simple prefix in the URL. The current version is `/v1/`. We will maintain backwards-compatibility by releasing breaking changes under a new version. Please note that the following changes are backwards-compatible: - Adding new properties to existing API responses - Adding new API endpoints - Adding new optional request parameters to existing API endpoints - Changing the order of properties in existing API responses - Changing the autocomplete address suggestion format ## Error Handling A successful lookup is accompanied with a HTTP status code of 200 and a response code of 2000 (found in the body). An error has occurred if the HTTP status code is not 200. Errors can range from a benign 404 (resource not found) to more urgent errors (your API Key ran out of credit, failed authentication, etc). ## Testing Each new account comes with a free test balance. Contact us if you need more for testing and integration. ### Community Key Our documentation and demos make heavy use of our community key `iddqd`. This allows for convenient access for trialing the API. Many restrictions on this key are relaxed to allow developers make test requests. This key has a limit of 15 lookups per IP address per day as well as a daily usage cap. If you hit any limit restrictions, you can continue testing the API by creating a key of your own and using our free test methods. Please be kind with the community key. We're trusting everyone to use it responsibly so that other developers may trial the API. Thank you! ## Metadata Requests that affect your balance may be annotated with arbitrary metadata. This data is stored along with your lookup history and can be queried at a later date via the API or the dashboard. We call the ability to label your requests [tagging](https://docs.ideal-postcodes.co.uk/docs/guides/tags). # Response Codes The API returns two indicators to help you to determine the status of each HTTP request. The first is the **HTTP Status**, which is found in the status-line of all HTTP requests. The API will return status codes that adhere to HTTP /1.1 Specifications wherever possible. `2XX` status codes indicates success while `4XX` and `5XX` indicate client and server errors respectively. The second is the **API response code**, which can be found in the `code` property of the response body. This code will provide a more specific reason if a failure has occurred and can point you in the right direction when debugging. Please use the glossary of code numbers and HTTP status codes below when debugging your requests. ## 200 Request Success | HTTP Code | API Code | Description | | --------- | -------- | -------------------------------------------- | | 200 | 2000 | Success. Request was completed s

Co-WIN Certificate API

Open Data

API to get Co-WIN vaccination certificate.