All public APIs — page 32

Jokes One

Games & Comics

Joke of the day and large category of jokes accessible via REST API

JSON2Video

Video

Create and edit videos programmatically: watermarks,resizing,slideshows,voice-over,text animations

Public Api

Cloud Platforms

# Introduction This API allows resellers to manage their resources in a simple, programmatic way using HTTP requests. # Conventions ## Requests The API supports different methods depending on the required action. | Method | Description | --- | --- | GET | Retrieve resources in a collection or get a single resource.<br/>Getters will never have any effect on the queried resources. | POST | Create a new resource in a collection. | PUT | Update an existing resource with its new representation. | DELETE | Delete an existing resource. ## HTTP status codes The API will reply with different HTTP statuscodes: | StatusCode | Description | --- | --- | 200 OK | The requests was processed and you receive data as a result. | 201 CREATED | The resource has been created. Either the Location header contains a link to the created resource, or links are being returned in the response body. The applied method will be indicated in the documentation. | 202 ACCEPTED | The request has been validated and accepted. Because we need to do some background processing prior to returning the result, we cannot send back a useful representation. | 204 NOCONTENT | The request has been processed, but no details can be returned. | 400 BADREQUEST | Your request is malformed. | 401 UNAUTHORIZED | You are not authorized. Follow the instructions in the Authorization documentation. | 403 FORBIDDEN | Access to the resource or operation is not allowed. | 404 NOTFOUND | The resource cannot be found. | 410 GONE | The resource is permanently no longer available. | 429 TOOMANYREQUESTS | The ratelimit has been exceeded. Please refer to the documentation on rate limiting for more details. | 500 INTERNALSERVERERROR | An error occurred during the processing of the request. The error is unexpected and most likely due to a bug in the api. In the event of a problem, the body of the response will usually contain an errorcode and errormessage. In rare cases additional details about the error are reported. Errorcodes 400-499 are considered to be client errors and indicate that there was an issue with the request. We will not take any action besides monitoring. Errorcodes 500-599 are considered to be server errors. The errors are monitored AND action will be taken to resolve the error. ## Formatting Snake casing is applied on resources and query parameters. The API is strictly returning JSON. No other formats are supported. Datetimes are returned in ISO-8601 format. ## Pagination Pagination is on by default on collections and is controlled by specifying *skip* and *take* parameters. **Skip** indicates the number of results to skip and where to start the new take. **Take** indicates the number of records to return. The returned number of items can be smaller than the requested take. Paged results will have headers with useful information regarding the paging. | Header | Description | --- | --- | X-Paging-Skipped | The number of results that have been skipped. | X-Paging-Take | The number of items in the current take. The number might differ from the requested take. It represents the actual number of items returned in the response. | X-Paging-TotalResults | The total number of results regardless of paging. ## Rate limiting The number of requests per interval is limited. Detailed information on the rate limiting can be found in specific headers which will be sent on each request. | Header | Description | --- | --- | X-RateLimit-Limit | The number of requests that can be made in a specific time interval. | X-RateLimit-Usage | The number of requests already made in the current time interval. | X-RateLimit-Remaining | The number of requests remaining until the reset. | X-RateLimit-Reset | The number of seconds until the reset.<br />After the reset you are allowed to make as many requests as specified by the X-RateLimit-Limit header. | Retry-After | The number of seconds you have to wait until you can make new requests.<br />This header is only present when the rate limit has been reached. I

Shotstack

Video

Cloud video editing API to create and render videos programmatically

Storm Glass

Weather

Global marine weather from multiple sources

Tisane

Text Analysis

Text Analytics with focus on detection of abusive content and law enforcement applications

Swiss public transport API

Uebermaps

Geocoding

Discover and share maps with friends

WebScraping.AI

Development

Web Scraping API with built-in proxies and JS rendering

Community driven API for Brazil Public Data

opendatasoft

Open Data

With our data marketplace solution, centralize and share your data assets with all types of user in a simple, secure and interactive way.

Wowza Streaming Cloud REST API Reference Documentation

Media

# About the REST API The Wowza Streaming Cloud^TM REST API (application programming interface) offers complete programmatic control over live streams, transcoders, stream sources, and stream targets. Anything you can do in the Wowza Streaming Cloud UI can also be achieved by making HTTP-based requests to cloud-based servers through the REST API. The Wowza Streaming Cloud REST API features *cross-origin resource sharing*, or CORS. CORS is a [W3C specification](https://www.w3.org/TR/cors/) that provides headers in HTTP requests to enable a web server to safely make a network request to another domain. In order to protect shared resources, the Wowza Streaming Cloud REST API is subject to limits. For details, see [Wowza Streaming Cloud REST API limits](https://www.wowza.com/docs/wowza-streaming-cloud-rest-api-limits). # About this documentation This reference documentation is based on the open-source [Swagger framework](http://swagger.io/specification/). It allows you to view the operations, parameters, and request and reponse schemas for every resource. Request samples are presented in cURL (Shell) and JavaScript; some samples also include just the JSON object. Response samples are all JSON. For more information and examples on using the Wowza Streaming Cloud REST API, see our [library of Wowza Streaming Cloud REST API technical articles](https://www.wowza.com/docs/wowza-streaming-cloud-rest-api). # Query requirements The Wowza Streaming Cloud REST API uses HTTP requests to retrieve data from cloud-based servers. Requests must contain proper JSON, two authentication keys, and the correct version number in the base path. ## JSON The Wowza Streaming Cloud REST API uses the [JSON API specification](http://jsonapi.org/format/) to request and return data. This means requests must include the header `Content-Type: application/json` and must include a single resource object in JSON format as primary data. Responses include HTTP status codes that indicate whether the query was successful. If there was an error, a description explains the problem so that you can fix it and try again. ## Authentication Requests to the Wowza Streaming Cloud REST API must be authenticated with two keys: an API key and an access key. Each key is a 64-character alphanumeric string that you can find on the **API Access** page in Wowza Streaming Cloud. Use the `wsc-api-key` and `wsc-access-key` headers to authenticate requests, like this (in cURL): ```bash curl -H 'wsc-api-key: [64-character-api-key-goes-here]' -H 'wsc-access-key: [64-character-access-key-goes-here]' ``` <!-- ReDoc-Inject: <security-definitions> --> ## Version The Wowza Streaming Cloud API is currently at version 1.0.0. Use `v1` in your base path in every request, like this path to the live_streams endpoint: ``` https://api.cloud.wowza.com/api/v1/live_streams ``` ## Example query Here is a complete example POST request, in cURL, with proper JSON syntax, headers, authentication, and version information: ```bash curl -H 'wsc-api-key: [64-character-api-key-goes-here]' -H 'wsc-access-key: [64-character-access-key-goes-here]' -H 'Content-Type: application/json' -X POST -d '{ "live_stream": { "name": "My live Stream", "...": "..." } }' https://api.cloud.wowza.com/api/v1/live_streams ```

Real-time cryptocurrency data, graphs and API that allows buy&sell

Clever-Cloud API

Cloud Platforms

Public API for managing Clever-Cloud data and products

Product Finder API

Finance

HSBC, one of the largest banking and financial services institutions in the world, serves millions of customers through its four global businesses.

L'API FICOBA (*FI*chier des *CO*mptes *B*ancaires et *A*ssimilés) permet aux entités administratives (administrations publiques, ministères, organismes sociaux) et aux acteurs privés qui sont éligibles d’accéder aux coordonnées bancaires d'un usager afin de permettre d'intégrer et de valider ces données dans leur système d'information. En effet, selon les dispositions de [l'article 1649 A du Code Général des Impôts](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000041578443/2020-02-29) : _"les administrations publiques, les établissements ou organismes soumis au contrôle de l'autorité administrative, (...) et toutes personnes qui reçoivent habituellement en dépôt des valeurs mobilières, titres ou fonds doivent déclarer à l'administration des impôts l'ouverture et la clôture des comptes de toute nature (...)"_. ### A quoi sert l'API Ficoba ? L'API permet de rechercher un compte bancaire, de plusieurs manières: * avec un identifiant : IBAN, SIREN/SIRET ou identifiant fiscal (SPI, voir [API R2P](https://www.data.gouv.fr/fr/dataservices/api-recherche-des-personnes-physiques-r2p/)) ; * avec un état civil d'un usager, avec ou sans adresse, pour une personne physique ; * avec la dénomination et deux éléments d'adresse pour une personne morale. * Vérifier l'existence d'un compte bancaire * Valider la cohérence entre un compte et l'identité du titulaire **Cas spécifique**: lors de l'ouverture d'un produit d'épargne réglementé (ex : livret d'épargne populaire LEP, livret A et

US Address Verification

Provides worldwide forward/reverse geocoding, batch geocoding and geoparsing

Postmark API

Email

Postmark makes sending and receiving email incredibly easy.

Directions, POIs, isochrones, geocoding (+reverse), elevation, and more

OSDB REST API v1

Development

An OpenAPI description of the OpenLink Smart Data Bot REST API v1

A hosted REST-API ready to respond to your AJAX requests

Onchain GraphQL APIs & DEX APIs

German realtime gas/diesel prices