Mock sample for your project: EasyPDFServer API

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

Datumbox offers a Machine Learning platform composed of 14 classifiers and Natural Language processing functions. Functions include sentiment analysis, topic classification, readability assessment, language detection, and much more.

Rev.ai provides quality speech-text recognition via a RESTful API. All public methods and objects are documented here for developer reference.
For a real-time speech to text solution, use Rev.ai's Streaming API.
Base Endpoint
The base url for this version of the API is
> https://api.rev.ai/speechtotext/v1
All endpoints described in this documentation are relative to this base url.
Quick Start
Follow the getting started checklist
Get your Access Token
You can generate your access token on the settings page of your account. This access token only needs to be generated once and never expires. You can re-generate your token, however this will invalidate the previous token.
Submit a File
To submit an audio file for transcription to Rev.ai:
Retrying Failed Requests
Some errors can be resolved simply by retrying the request. The following error codes are likely to be resolved with successive retries.
| Status Code | Error |
|---|:---|
| 429 | Too Many Requests |
| 502 | Bad Gateway |
| 503 | Service Unavailable |
| 504 | Gateway Timeout |
Note: With the exception of the 429 status code, it is recommended that the maximum number of retries be limited to 5 attempts per request. The number of retries can be higher
for 429 errors but if you notice consistent throttling please contact us at.

This is the Handwrytten API for sending cards written in the handwriting of your choice.
Using this api, you can send cards to users. You can also customize cards with logos, which
can be saved and then used like any other card in the system.
For a "sandbox" account, please contact [email protected]
To move from credit card per-transaction to monthly invoicing, also contact us.
https://www.handwrytten.com

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

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.

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

The current api version is v3.4 The api methods listed below can be called directly from this page to test the output. You might set the api_key to pre-authenticate all requests on this page (this will work if your secret is blank). API endpoint URL: http://{apiName}.text2data.com/v3/ {method} The api can be consumed directly or using our SDK. Our Excel Add-In and Google Sheets Add-on are also using this api to process the data.

Use MotaWord API to post and track your translation projects.

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!

Fungenerators taunt generation API generates random taunts / insults, relevant to the given category. Many categories are supported and new ones are added very frequently. Click here to subscribe