
Text Analytics & Sentiment Analysis API | api.text2data.com API
by text2data.org
Overview
<p>The current api version is <b>v3.4</b></p><br><br><p>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).</p><br><br> API endpoint URL: http://{apiName}.text2data.com/v3/ {method}<br><br>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.
Text Analytics & Sentiment Analysis API | api.text2data.com is a text analysis API from text2data.org. Requests are authenticated with an API key. It is served over HTTPS. Its OpenAPI description documents 6 endpoints.
At a glance
- Authentication
- API key
- HTTPS
- Yes
- CORS
- Unknown
- Category
- Text Analysis
- Base URL
http://api.text2data.org- Version
- v3.4
- Endpoints
- 6
- OpenAPI
- Specification ↗
- Spec updated
- 2020-08-19
Make a first request
Replace the placeholders; the documentation says exactly where credentials go.
curl -X GET "http://api.text2data.org/v3/Analyze" \
-H "Accept: application/json" \
-H "X-API-Key: YOUR_API_KEY"const response = await fetch("http://api.text2data.org/v3/Analyze", {
method: "GET",
headers: {
"Accept": "application/json",
"X-API-Key": "YOUR_API_KEY",
},
});
const data = await response.json();
console.log(data);import requests
response = requests.request(
"GET",
"http://api.text2data.org/v3/Analyze",
headers={
"Accept": "application/json",
"X-API-Key": "YOUR_API_KEY",
},
timeout=30,
)
print(response.json())Endpoints
| Method | Path | What it does |
|---|---|---|
| GET | /v3/Analyze | Test api response without api key |
| POST | /v3/Analyze | Sentiment analysis service |
| GET | /v3/Categorize | Test api response without api key |
| POST | /v3/Categorize | Document categorization service |
| GET | /v3/Extract | Test api response without api key |
| POST | /v3/Extract | Document extraction service |
Questions
Does the Text Analytics & Sentiment Analysis API | api.text2data.com API need an API key?
Yes. The Text Analytics & Sentiment Analysis API | api.text2data.com API uses API key authentication; the documentation explains how to get credentials.
Does the Text Analytics & Sentiment Analysis API | api.text2data.com API support HTTPS?
Yes, the Text Analytics & Sentiment Analysis API | api.text2data.com API is served over HTTPS.
How many endpoints does the Text Analytics & Sentiment Analysis API | api.text2data.com API have?
Its OpenAPI description lists 6 endpoints in version v3.4. All of them are shown on this page.
What are alternatives to the Text Analytics & Sentiment Analysis API | api.text2data.com API?
Other Text Analysis APIs include Google Cloud Natural, LanguageTool, Tisane, LibreTranslate, Asynchronous Speech-To-Text API Documentation.
Similar text analysis APIs
Compare alternatives →Google Cloud Natural
Text AnalysisNatural language understanding technology, including sentiment, entity and syntax analysis
LanguageTool
Text AnalysisStyle and Grammar Checker for 25+ Languages
Tisane
Text AnalysisText Analytics with focus on detection of abusive content and law enforcement applications
LibreTranslate
Text AnalysisTranslation tool with 17 available languages
Asynchronous Speech-To-Text API Documentation
Text AnalysisRev.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](/docs/streaming). # 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](https://www.rev.ai/getting_started) ## Get your Access Token You can generate your [access token](#section/Authentication/Access-Token) on the [settings page](https://www.rev.ai/access_token) 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: ``` curl -X POST "https://api.rev.ai/speechtotext/v1/jobs" -H "Authorization: Bearer $REV_ACCESS_TOKEN" -H "Content-Type: application/json" -d "{\"media_url\":\"https://www.rev.ai/FTC_Sample_1.mp3\",\"metadata\":\"This is a sample submit jobs option\"}" ``` You’ll receive a response like this: ~~~ { "id": "Umx5c6F7pH7r", "created_on": "2018-09-15T05:14:38.13", "name": "sample.mp3", "metadata": "This is a sample submit jobs option for multipart", "status": "in_progress" } ~~~ The `id` (in this case `Umx5c6F7pH7r`) will allow you to retrieve your transcript. ## Get Your Transcript Once a transcription job's `status` becomes `transcribed`, you can retrieve the transcript in JSON format by running: ``` curl -X GET "https://api.rev.ai/speechtotext/v1/jobs/{id}/transcript" -H "Authorization: Bearer $REV_ACCESS_TOKEN" -H "Accept: application/vnd.rev.transcript.v1.0+json" ``` Alternatively you can get the plain text version by running: ``` curl -X GET "https://api.rev.ai/speechtotext/v1/jobs/{id}/transcript" -H "Authorization: Bearer $REV_ACCESS_TOKEN" -H "Accept: text/plain" ``` You can poll for the `status` of your job by querying for the job periodically: ``` curl -X GET https://api.rev.ai/speechtotext/v1/jobs/{id} -H "Authorization: Bearer $REV_ACCESS_TOKEN" ``` **Note:** Polling is NOT recommended in a production server. Rather, use [webhooks](#section/Webhooks) to asynchronously receive notifications once the transcription job completes If you have any further questions, contact us at <[email protected]> # Submitting Files Two `POST` request formats can be used to submit a file: `application/json` or `multipart/form-data`. ## JSON This is the preferred method of file submission. Uses the `media_url` property to provide a direct download URL to the Rev.ai server. This method supports the use of pre-signed URLs. Links to videos hosted on platforms like Youtube are not valid because they are not direct download links. **Important note on presigned URLs:** Signed URLs usually have an expiration time which is configurable. To ensure the Rev.ai server can access the link, make sure the expiration time is set to 2 hours or more. In the event you plan on resending the same file, make sure to generate a new presigned URL. ## FormData Used to send a local file to the Rev.ai server. This allows the customer to send the file directly from the host machine. Certain limits apply to this format, see the [Async API Limits section](#section/Async-API-Limits) for more detals. # Turnaround Time and Chunking Often, especially for shorter files, your transcript will be ready in 5 minutes or less. It generally takes no longer than 15 minutes to return longer audios. If you require faster turn around time please contact <[email protected]> Chunking is the act of breaking audio files into smaller segments. Rev.ai uses this method to decrease turnaround time of audios greater than 3 minutes in length. # Webhooks If the optional `callback_url` is provided, the API will make an HTTP POST request to the `callback_url` with the following request body when the job either completes successfull
Detect Language
Text AnalysisDetects text language
Listed from APIs.guru (CC0).