Mock sample for your project: Taunt as a service API

Below is the documentation for the API calls. You can try them out right here.

Fungenerators API gives access to the full set of generators available at fungenerators.com so that you can integrate them in your workflow or an app. Click here to get details and subscribe . Here are the individual API links:
QR Code API
Generate QR Code images for text, url, email , business cards etc. You can decode QR Code images and get the contents as well. The best and complete QR Code API on the cloud. Click here to subscribe

Ahoy matey! We help the landlubbers to get to know about the seamen way! You can generate pirate names, get some real pirate insults and pirate filler text. Oh you can translate to pirate lingo as well. Click here to subscribe

Shakespeare API. Generate random Shakespeare quotes, names, insults, lorem ipsum etc. Translate normal English to Shakespeare English. Click here to subscribe

A full featured Facts API. REST access with json/xml/jsonp result support. On this day birth and death support, random fact, keyword search support etc. Below is the documentation for the Random Facts API calls. You can try them out right here. Click here to subscribe

A full featured, REST based UUID generator with json/xml/jsonp result support. You can try them out right here. Click here to subscribe

Fungenerators name generation API generates random names relevant to the given category. Lots of categories are supported with many variations supported. Click here to subscribe

Below is the documentation for the API calls. You can try them out right here.

Generate random fake identities (name, address, email, phone , credit card info etc). Click here to subscribe

Generate Barcode images for a given barcode number. You can decode Barcode images and get the barcodes in a numberic form as well. Many industry standard barcode types are supported. The best and complete Barcode API on the cloud. Click here to subscribe

Below is the documentation for the API calls. You can try them out right here.

Hyperlocal Demographics, Vehicle Traffic, Economic, Market Signals, and More. Use this API to request IdealSpot hyperlocal geospatial market insight and geometry data.
Detailed Description
Use this API as your local economy microscope by querying IdealSpot hyperlocal market insight and geometry data. We offer the most precise, extensive, and frequently-updated local market data in the US. Our data is available across the entire US and can be queried at geographic scales ranging from the micro (Census block) through the macro (nation).
Better data and analysis leads to a better understanding of local market opportunities and risks. Integrate with your commercial real estate and marketing applications, machine learning workflows, and other investment analytics.
Our goal is to offer the most complete snapshot of the geographically distributed consumer and retail economy. We start with the fundamentals of consumers and business establishments. To connect retailers with consumers, we provide mobility data like vehicle traffic and mobile device data. To describe consumer intent, we provide geolocated digital marketing data.
We believe that accurate capital allocation through reliable local market data is foundational to creating robust, healthy, and livable communities for all. We hope you and your clients find tremendous value in this service.
Features
Query data and GeoJSON geometries at these scales for any US latitude and longitude:
Rings (0.5 km+)
Drive time (1-60 minutes)
Bike time (3-60 minutes)
Walk time (5-60 minutes)
Public transit time (5-60 minutes)
Administrative region (US, states, core-based statistical areas, counties, Census-designated places, Census tracts, zipcodes, Census block groups, opportunity zones)
| Data Feature | Description |
| ------- | ------------------------------|
| Demographics, Housing, Spending | Updated Quarterly. Current and historical market data including population, spending, and housing. Vendor (PopStats) is relied upon by Walgreens, Ulta Beauty, Blackstone, etc |
| Labor, Business Establishments, Economic Conditions | Updated Quarterly. Traditional market data including workforce, business establishment counts, and economic conditions like local GDP, unemployment rates. Vendor (PopStats) is relied upon by Walgreens, Ulta Beauty, Blackstone, etc |
| Consumer segmentation | Updated Annually. Demographics grouped into narrative-oriented segments. |
| Vehicle Traffic | Updated semi-annually. Gold standard in vehicle traffic data from INRIX. Counts by day of week, time of day and side of street. |
| Rings and Travel time polygons | Estimate in Real-time. Rings alongside drive time, walk time, bike time, and public transit time polygons. Request as GeoJSON geometries for mapping or use with data queries |
| Administrative region polygons | Updated Annually. GeoJSON administrative regions from US Census Bureau: block groups, tracts, counties, CBSAs, states, opportunity zones, USPS zipcodes |
| Internet Search Volumes | 30 day rolling averages for geolocated advertising potential across 450 business categories from major search engines |
| Social Media Interest | 30 day rolling average for geolocated advertising potential across 450 business categories from major social networks |
Coming Soon!
This API powers our local market research platform at IdealSpot.com. The functionality exposed so far is only a portion of our current capabilities. We will be exposing additional API features in time so watch this space!
| Data Feature | Description |
| ------- | ------------------------------|
Mobile device visit counts, points of interest, brands | Fresh point of interest data across 3000+ brands, millions of POI, and historical foot traffic counts using mobile data for those points of interest
Origin/destination trips from mobile devices | Map origins and destinations of devices visiting an arbitrary catchment area
Competition search | Search all major point-of-interest aggregators in one query
Environment/climate | Expected weather patterns like temperature and precipitation
Filter search API | Query data for all counties in state, all tracts in MSA, etc
Road segment tiles | Plot road segments on maps in interactive applications
Developer Website
For more detail see https://developer.idealspot.com/

NamSor API v2 : enpoints to process personal names (gender, cultural origin or ethnicity) in all alphabets or languages. By default, enpoints use 1 unit per name (ex. Gender), but Ethnicity classification uses 10 to 20 units per name depending on taxonomy. Use GET methods for small tests, but prefer POST methods for higher throughput (batch processing of up to 100 names at a time). Need something you can't find here? We have many more features coming soon. Let us know, we'll do our best to add it!

Exude API is an Open Source project, It is used for the primary ways for filtering the stopping, stemming words from the text data. This API is in a very basic level of development need to work on for later changes.

The general-purpose API

The powerful Optical Character Recognition (OCR) APIs let you convert scanned images of pages into recognized text.

Below is the documentation for the API calls. You can try them out right here.

Provided by Salesforce � Copyright 2000�2020 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of salesforce.com, inc., as are other names and marks. Other marks appearing herein may be trademarks of their respective owners. Last updated: Aug 17, 2020

DocSpring is a service that helps you fill out and sign PDF templates.

SelectPdf HTML To PDF Online REST API is a professional solution that lets you create PDF from web pages and raw HTML code in your applications. The API is easy to use and the integration takes only a few lines of code.

Expects only running software, real reactions, and beautifully crafted APIs to serve your every desire to transcribe a piece of paper to digital form.

Authentication
For all calls, supply your API key. Sign up to obtain the key .
Our API supports both unencrypted (HTTP) and encrypted (HTTPS) protocols.
However, for security reasons, we strongly encourage using only the encrypted version.
The API key should be supplied as either a request parameter user_key or in Authorization header.
Authorization: user_key
API operations
All API operations can perform analysis on supplied raw text or on text extracted from a given URL.
Optionally, one can supply additional information which can make the result more precise. An example
of such information would be the language of text or a particular text extractor for URL resources.
The supported types of analyses are:
lemmatization ⟶
Finds out lemmata (basic forms) of all the words in the document.
correction ⟶
Performs correction (diacritization) on all the words in the document.
topic detection ⟶
Determines a topic of the document, e.g. finance or sports.
sentiment analysis ⟶
Determines a sentiment of the document, i.e. how positive or negative the document is.
named entity recognition ⟶
Finds named entities (like person, location, date etc.) mentioned the the document.
Encoding
The supplied text is expected to be in UTF-8 encoding, this is especially important for non-english texts.
Returned values
The API calls always return objects in serialized JSON format in UTF-8 encoding.
If any error occurs, the HTTP response code will be in the range 4xx (client-side error) or
5xx (server-side error). In this situation, the body of the response will contain information
about the error in JSON format, with exception and message values.
URL limitations
All the requests are semantically GET. However, for longer texts, you may run into issues
with URL length limit. Therefore, it's possible to always issue a POST request with all
the parameters encoded as a JSON in the request body.
Example:
POST /s1/sentiment
Content-Type: application/json
{"text":"There is no harm in being sometimes wrong - especially if one is promptly found out."}
This is equivalent to GET /s1/sentiment?text=There%20is%20no%20harm...
Request limitations
The API has other limitations concerning the size of the HTTP requests. The maximum allowed size of any
POST request body is 512 KiB. For request with a URL resource, the maximum allowed number of
extracted characters from each such resource is 100,000.
Terms of Service
By using the API, you agree to our
Terms of Service Agreement.
More information
The Interpretor Public Documentation