S4 provides various REST APIs for processing individual documents in real time and for querying Linked Open Datasets (Freebase, GeoNames and DBpedia) via SPARQL.
The S4 REST services support the following HTTP request methods:
All S4 REST APIs as well as the S4 Management Console utilise a transport level encryption via SSL. Unencrypted HTTP access is not supported.
All S4 services support gzip compression of the service response for better performance. It is recommended that you enable the compression by setting an Accept-Encoding: gzip HTTP header.
In case of a problem with the correct execution of the request, an error response is returned with an HTTP status code, specifying the type of the error (as described below), as well as a human readable error message.
If the user has exceeded his free quota, the error response will be: 429 "Too Many Requests"
The access to the S4 REST API requires a private API key, which consists of two randomly generated parts, the "key ID" and "password". Each customer account can generate an unlimited number of API keys (for different applications or users) and each API key can be enabled/disabled or deleted as necessary.
Note: You must store the key ID and password at a secure location. If you lose your API key password, you will not be able to recover it. You will need to delete your existing key and generate a new one.
Currently, S4 provides the following free quotas:
You can find code samples showing how you to access the service from various programming languages at https://github.com/Ontotext-AD/S4
Sample code is available in the following programming languages:
The Swagger documentation for the REST APIs is available at http://swagger.s4.ontotext.com/
Skip to end of metadata Go to start of metadata