Mock sample for your project: Wordnik API

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

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.

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.

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

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

Automatic language detection for any texts. Supports over 150 languages.

Introduction
PDF Generator API allows you easily generate transactional PDF documents and reduce the development and support costs by enabling your users to create and manage their document templates using a browser-based drag-and-drop document editor.
The PDF Generator API features a web API architecture, allowing you to code in the language of your choice. This API supports the JSON media type, and uses UTF-8 character encoding.
You can find our previous API documentation page with references to Simple and Signature authentication here.
Base URL
The base URL for all the API endpoints is https://us1.pdfgeneratorapi.com/api/v3
For example
https://us1.pdfgeneratorapi.com/api/v3/templates
https://us1.pdfgeneratorapi.com/api/v3/workspaces
https://us1.pdfgeneratorapi.com/api/v3/templates/123123
Editor
PDF Generator API comes with a powerful drag & drop editor that allows to create any kind of document templates, from barcode labels to invoices, quotes and reports. You can find tutorials and videos from our Support Portal.
Component specification
Expression Language documentation
Frequently asked questions and answers
Definitions
Organization
Organization is a group of workspaces owned by your account.
Workspace
Workspace contains templates. Each workspace has access to their own templates and organization default templates.
Master Workspace
Master Workspace is the main/default workspace of your Organization. The Master Workspace identifier is the email you signed up with.
Default Template
Default template is a template that is available for all workspaces by default. You can set the template access type under Page Setup. If template has "Organization" access then your users can use them from the "New" menu in the Editor.
Data Field
Data Field is a placeholder for the specific data in your JSON data set. In this example JSON you can access the buyer name using Data Field {paymentDetails::buyerName}. The separator between depth levels is :: (two colons). When designing the template you don’t have to know every Data Field, our editor automatically extracts all the available fields from your data set and provides an easy way to insert them into the template.
Testing with JWTs
You can create a temporary token in Account Settings page after you login to PDF Generator API. The generated token uses your email address as the subject (sub) value and is valid for 5 minutes.
You can also use jwt.io to generate test tokens for your API calls. These test tokens should never be used in production applications.
Libraries and SDKs
Postman Collection
We have created a Postman Collection so you can easily test all the API endpoints wihtout developing and code. You can download the collection here or just click the button below.
Run in Postman
Client Libraries
All our Client Libraries are auto-generated using OpenAPI Generator which uses the OpenAPI v3 specification to automatically generate a client library in specific programming language.
PHP Client
Java Client
Ruby Client
Python Client
Javascript Client
We have validated the generated libraries, but let us know if you find any anomalies in the client code.
Error codes
| Code | Description |
|--------|--------------------------------|
| 401 | Unauthorized |
| 403 | Forbidden |
| 404 | Not Found |
| 422 | Unprocessable Entity |
| 500 | Internal Server Error |
401 - Unauthorized
| Description |
|-------------------------------------------------------------------------|
| Authentication failed: request expired |
| Authentication failed: workspace missing |
| Authentication failed: key missing |
| Authentication failed: property 'iss' (issuer) missing in JWT |
| Authentication failed: property 'sub' (subject) missing in JWT |
| Authentication failed: property 'exp' (expiration time) missing in JWT |
| Authentication failed: incorrect signature |
403 - Forbidden
| Description |
|-------------------------------------------------------------------------|
| Your account has exceeded the monthly document generation limit. |
| Access not granted: You cannot delete master workspace via API |
| Access not granted: Template is not accessible by this organization |
| Your session has expired, please close and reopen the editor. |
404 Entity not found
| Description |
|-------------------------------------------------------------------------|
| Entity not found |
| Resource not found |
| None of the templates is available for the workspace. |
422 Unprocessable Entity
| Description |
|-------------------------------------------------------------------------|
| Unable to parse JSON, please check formatting |
| Required parameter missing |
| Required parameter missing: template definition not defined |
| Required parameter missing: template not defined |

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/

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