Topic Tagging

FREEMIUM
Verified
By Twinword API | Updated 2 месяца назад | Text Analysis
Popularity

9.1 / 10

Latency

821ms

Service Level

100%

Health Check

N/A

Followers: 170
Resources:
Product Website Terms of use
API Creator:
Rapid account: Twinword API
Twinword API
twinword
Log In to Rate API
Rating: 5 - Votes: 1

README

Topic Tagging

What are the topics and keywords? Automatically generate topics and keywords for articles and blogs.

DEMO:
Topic Tagging - Free Tool & API Demo

The Possibilities

Topic generation and tagging may be a common task for us, but it is a huge challenge for computers, mainly because computers do not understand languages. How many applications will benefit if computers start to understand text like humans?

With this tool, news feeders can easily classify their contents and advertisers can also place ads on the web in a more relevant way, matching the content of web pages to the advertiser’s industry. Twinword Topic Tagging API does more than just extract keywords from the given text. Based on contextual language understanding, the Topic Tagging API is able to generate human-like topics even without the presence of that particular word in the context.

API Limitations

Max input size

  • 14,336 Unicode characters.
  • It includes whitespace characters and any markup characters such as HTML or XML tags.

Rate limitations

  • There is no rate limit except Keyword Suggestion API, which is 2 requests per 10 seconds.
  • If you exceed the rate limit, you will get “Too many requests. Try again in a few seconds.” error messages.

Server capacity

  • Normally our server can handle 6 requests per second. In case of more traffic, our server automatically scales up to more than 300 requests per second.
  • However, the scaling happens periodically. This means, if you send 100 requests per second immediately, many requests will fail. Instead, we recommend to start out at 6 requests per second, and to increase the amount of requests per second every 3 minutes by 6 requests. For example, going from 6 to 12 requests per second after 3 minutes have passed. In this case, you will consume 6 requests per second * 60 seconds * 3 minutes = 1,080 requests.
  • Please keep in mind that in case you stop sending requests, the server will go back to the original capacity of 6 requests per second.

Security and privacy

  • We fully understand the importance of privacy and security. We do not store any content on our server side. We just keep logging transactions. To make sure, we advise you to use POST rather than GET method.
  • We keep PCI compliance annually, which is done by 3rd party security quality accessor.