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 `126.96.36.199/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.
Welcome to Vouchery.io API v2.0! Vouchery provides a REST-oriented API which gives you access to easily create main campaign that includes multiple promo campaigns, add rewards, validate and redeem vouchers. You will find a detailed description of API design, authentication and authorisation, available endpoints, and responses on successful requests and errors at https://docs.vouchery.io/reference
US Zipcode, County, City, and State Boundaries API: A simple & very fast API that will allow you to integrate multiple GeoJson US boundaries results into your apps and systems. This API is designed to be used programatically for optimal performance. When using the MashApe UI for queries expect significant latency issues on large result sets!
A RESTful API designed for developers who want to access hyper-localized product data More than 60 available retailers (food & beverages, pets, electronics & hightech, sport, DIY) - 90% located in France
UK Postal Code(ex. ZE1 0AE), Sector, District, Boundaries API: A simple & very fast API that will allow you to integrate multiple GeoJson UK Unit and sector level boundaries result into your apps and systems. This API is designed to be used programatically for optimal performance. When using the MashApe UI for queries expect significant latency issues on large result sets!
The SurveyMethods API is designed so that you can integrate third party applications (like HR, CRM, Helpdesk, etc.) with SurveyMethods using HTTP methods. To use our API, you must have an account with SurveyMethods. Our API is available to all users regardless of package preferences.
This API is designed to provide authoritative National Park Service (NPS) data and content about parks and their facilities, events, news, alerts, and more.
A school's score or placement on the API is designed to be an indicator of a school's performance level and is calculated annually by the California Department of Education
Recognant's SESTA FOSTA Compliance API is designed to find content that advertises for prostitution. On April 11th, 2018 SESTA FOSTA was signed in to law, it requires that content publishers actively work to prevent their platform from being used in the advertising of prostitution. Many sites rely on community moderators to spot such ads, but under the new rules this is insufficient. The Recognant AI has been aiding in the arrest of human traffickers and the rescue of those being trafficked for more than 2 years. We now offer this same technology to site operators to minimize their risk now that safe harbor provisions have been removed.
CA Postal Code(ex. T6H, or A0A0A1 ), FSA and LDU, Boundaries API: A simple & very fast API that will allow you to integrate multiple GeoJson CA FSA and LDU level boundaries result into your apps and systems. This API is designed to be used programatically for optimal performance. When using the MashApe UI for queries expect significant latency issues on large result sets!
Tabex PDF Intelligence API is designed to help you extract meaningful data in your data flow. Millions of PDF are created daily around the world and contain data in border-less and bordered tabular forms. Tabex helps you to make these data available in a meaningful and actionable format. Start discovering the hidden insights from your documents. Tabex PDF Data intelligence API is designed to offer both performances and flexibility. The API is restful call that offers high speed and precision. Developers can call the API in different modes and integrate it in a variety of work flows for semantic analysis, data capture, Financial data base building and others. The API is able to extract tabular data from both scanned and editable PDF into a variety of formats. Formats include PDF to EXCEL, PDF to XML, PDF to CSV, PDF to HTML and PDF to Text. The API leverages several algorithms to identify tabular data, extract them in editable or machine readable format and allow developers to leverage data in their data work flow.
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.
Our email parsing API is designed to retrieve travel itineraries from an email. So we can receive a raw email with some type of itinerary, such a hotel reservation of flight reservation, we will extract all the relevant information and return it in a
The API is designed for furniture store repository which provides furniture store data against a token and name of the furniture store
This Ethfinex trustless API is designed to allow access to submit, cancel and query placed orders onto the shared Bitfinex/Ethfinex order book
This is a very simple REST API designed to test students' ability to consume external services from their applications.
The bdea.cc api helps to detect domains of disposable email address services such as mailinator.com, spamgourmet. In other words: if you need to keep your userbase clean you should avoid throw-away, one-time, instant, temporary email addresses. That's what this api is designed for. BTW: no false positives.
The Spam Scanner API provides a way to scan individual messages or text for Spammy content. This API is primarily designed for email but can be used for any kind of spam, including message spam, comment spam, etc. The data provided is checked against an extensive spam database, and if there's spammy content such as a spammy URL or domain, spammy text or a spammy email address, Spam Scanner will classify the message as spam. This is an early version of the API, so while it is very limited right now, there will be more coming if there is enough interest.
The listed REST API calls give you access to the entire Onehop Platform stack. These API calls are designed to make it easy to add a rich in-app messaging feature to your application.
Synapsify’s REST API is based on a core set of linguistic algorithms, utilizing phonemics, natural language processing (NLP), machine learning, etc. The API has been designed to be as flexible as possible, and can be adapted to a very wide range of domains and fields of interest, including: Reading any type of written content based on several dimensions; Revealing the quality, balance, credibility and quotablity of such content and its most important topics and phrases; Indexing and matching against other written content or customized indexes; Enhancing the ability to discover, understand and segment actionable insights.