RaveGeo WebMap API Search Results & Alternatives
AFEX API is designed for businesses that want to make frequent payments. By accessing our Payment Engine via our API, it allows customers to automate their end-to-end payment processes and rapidly deliver tailor-made solutions for our customers’ business directly. Payments are sent through AFEX’s intermediary banks, payment channels and are bound by applicable laws, regulations, clearing house rules or payment processing procedures. Our API is built by developers for developers making it straightforward to integrate with our systems. We’ve also designed our documentation to be easy to use. Our API calls are grouped into feature sets which you can see in the navigation here in our API documentation. What's new in this version? ------------ The latest release to support these changes was deployed to production on 28th of June, 2019. * A new *Production* API endpoint `https://webapi.afex.com/` was deployed with new load-balanced architecture for **increased stability** and **up-time** * New V2 launch of key methods including [api/V2/Quote](https://doc.api.afex.com/?version=latest#98c6fc20-a17a-4d42-b141-93c4f16c77bd), [api/V2/Trades/Create](https://doc.api.afex.com/?version=latest#91dda474-6ac2-435c-8999-e2f9302130c6), and [api/V2Payments/Create](https://doc.api.afex.com/?version=latest#9a8d48e2-012e-4f05-8f43-bb238cf705da) *Note that methods listed as "V2" are available through the Version 2 endpoint* * Enhanced beneficiary validation for **IBAN** and **SWIFTBIC/Routing Code** Technical Notes ------------ **Non-Prod:** V5.2019 was be deployed to the demo environment on the 6th of June, 2019. **TLS version support:** Effective June 2018, AFEX no longer supports TLS version 1.0. AFEX currently supports TLS 1.1 and 1.2 in both the demo and production environments. **Production server IP address range:** Effective August 2018, the AFEX production servers public IP range was changed to `18.104.22.168/26`. Getting Started ------------ **1. Read the documentation** We recommend that you read the API documentation in Developer Center to familiarize yourself with the API conventions and functionality along with exploring the examples. **2. Use the Demo API** The Demo API is connected to our test infrastructure. It returns real data but executes trades on your *demo account* and does not execute live transactions. A unique demo account will be provided to you as part of your engagement and will mirror the configuration needed for your *eventual* production account. Demo end points are: **AFEX API (beneficiaries, trading and payments):** Version 1.0 https://demo.api.afex.com:7890/ Version 2.0 https://WebApiDemo.afex.com/ **Partner API (account on-boarding):** Version 1.0** https://demo.api.afex.com:7885/ **3. Design & Development** Your dedicated Integrated Solutions Program Manager will assist with defining the optimum technical design based on your unique requirements.
A public RESTful API that provides access to Hydra Movies entire data set of more than 3,500 movies - data that may be useful to other webmasters and film buffs alike. Users can obtain the following information from each film title: - Movie Title - Movie Year - Genre - Movie Synopsis - Movie Poster – via URL path - IMDB ID - IMDB Rating - Runtime - Language - YouTube trailer video ID
Related APIs in Category: Mapping
Chicmi are mapping out the fashion scene in the world's fashion cities, starting with London, Glasgow, Edinburgh and Manchester. Use the Chicmi API to access our unique set of fashion data, including every fashion sale, sample sale, fashion exhibition and fashion event in each city.
What is Widevine DRM? Widevine's DRM solution combines the following industry adopted standards to provide robust multiplatform content protection: Dynamic Adaptive Streaming over HTTP (DASH) DASH enables streaming of high quality media content over the Internet. DASH leverages standard HTTP protocol and can be easily deployed on existing Internet infrastructure (web servers, CDNs, firewalls, etc). Common Encryption (CENC) CENC is an industry standards based approach to content encryption. CENC identifies standard encryption and key mapping mechanisms that may be utilized by one or more DRM systems to allow the decryption of the same file using different DRM systems. CENC enables content providers to encrypt their content once and deliver it to numerous client devices and their assorted DRM schemes. Encrypted Media Extensions (EME) EME is a proposed W3C standard that provides a set of common APIs that can be used to interact with DRM systems and manage license key exchange. EME allows content providers to design a single application solution for all devices. Key benefits of Widevine's DRM solution: Support for reliable content protection across multiple systems:. Provides ubiquitous device coverage and extends synergy across multiple content protection systems. See a list of currently supported platforms. Complete control and flexibility during video playback: Fully featured HTML5 video player with adaptive streaming, QoS, and accessibility support across devices.
API AI provides a way to create mapping between language structures that are common in natural languesgea and data structures that are easy for software to parse and take action. Once these mappings have been created, you can make a query with either natural languages text or a voice sound file, and API.AI will return structured data with an action to take the parameters to act upon.
JSONpedia API is designed to simplify access at MediaWiki contents transforming everything into JSON. Such API provides a REST service to parse, convert, and enrich WikiText documents. JSONpedia supplies capabilities for recursive template expansion and mapping to DBpedia. This framework has been designed to extract linguistic resources from the Wikipedia and to enable massive data scraping. Our mission is to deliver a general purpose infrastructure for Wikipedia multi language data consumption both for researchers and industry.