Text Tagging API

The Text Tagging API provides an easy and efficient way to analyze text by identifying the parts of speech, grouping them into meaningful phrases, and recognizing named entities. With this API, developers can automate tasks such as content categorization, sentiment analysis, and entity recognition, improving the accuracy and efficiency of text-processing workflows.

About the API: 

The Text Tagging API is a powerful tool for developers who need to analyze and process text data. This API provides several useful features such as part-of-speech tagging, phrase chunking, and named entity recognition.

Part-of-speech tagging is the process of identifying the parts of speech in a sentence, such as nouns, verbs, adjectives, and adverbs. This information can be used to identify the grammatical structure of a sentence, which is useful for tasks such as text classification, sentiment analysis, and information retrieval. By identifying the parts of speech, developers can more easily extract meaningful information from large text datasets.

Phrase chunking is the process of grouping words together into meaningful phrases. This can be used to identify phrases such as noun phrases, verb phrases, and prepositional phrases. By identifying these phrases, developers can more easily extract meaningful information from text datasets. For example, in a news article about a political event, identifying noun phrases such as "president", "election", and "opposition party" can help in identifying the main topics of the article.

Named entity recognition (NER) is the process of identifying and categorizing named entities in text. This includes identifying names of people, organizations, locations, and other entities. By identifying these named entities, developers can extract information about the entities mentioned in text, which can be useful for tasks such as information retrieval, sentiment analysis, and content categorization. For example, in a news article about a company acquisition, identifying the names of the companies involved and the location of the acquisition can help in categorizing the article as a business news story.

The Text Tagging API is easy to use, with simple REST API calls that return JSON formatted results. Developers can use this API to automate tasks such as content categorization, sentiment analysis, and entity recognition. This can improve the accuracy and efficiency of text processing workflows, making it easier for developers to work with large text datasets. The API can also be used to build intelligent applications such as chatbots, virtual assistants, and search engines that can understand natural language text input.

Overall, the Text Tagging API is a powerful tool for developers who need to analyze and process text data. With its part-of-speech tagging, phrase chunking, and named entity recognition features, this API can help developers extract meaningful information from large text datasets, improving the accuracy and efficiency of text processing workflows.

 

What this API receives and what your API provides (input/output)?

Pass the text that you want to analyze and receive its tagging and part of speech analysis.  

 

What are the most common uses cases of this API?

  1. Sentiment analysis: The Text Tagging API can be used to identify the parts of speech, phrases, and named entities in customer reviews or social media posts, which can be used to perform sentiment analysis. This can help businesses understand customer sentiment and feedback about their products or services, and improve their offerings accordingly.

  2. Content categorization: The Text Tagging API can be used to analyze the text of news articles or social media posts, and categorize them into topics such as sports, politics, or entertainment. This can help news organizations or social media platforms better organize and present content to users, improving user engagement and satisfaction.

  3. Virtual assistants and chatbots: The Text Tagging API can be used to help virtual assistants or chatbots better understand and respond to natural language input from users. By identifying the parts of speech and named entities in user input, these intelligent systems can provide more accurate and helpful responses to user queries.

  4. Search engines: The Text Tagging API can be used to improve the accuracy of search results in search engines. By identifying the parts of speech and named entities in user search queries, search engines can better understand the intent behind the query and provide more relevant search results.

  5. Data mining: The Text Tagging API can be used to extract valuable information from large text datasets such as academic papers, legal documents, or social media posts. By identifying the parts of speech, phrases, and named entities in these texts, researchers or analysts can uncover new insights or trends, and make data-driven decisions based on their findings.

 

Are there any limitations to your plans?

Besides the number of API calls, there is no other limitation

API Documentation

Endpoints


Part-of-speech tagging, phrase chunking, and named entity recognition of text.

Available Languages:

english. 

spanish.

dutch. 

portuguese. 



                                                                            
POST https://zylalabs.com/api/1818/text+tagging+api/1479/text+tagging
                                                                            
                                                                        

Text Tagging - Endpoint Features

Object Description
text [Required] Text to tag and chunk, must be no more than 2000 characters.
language [Required] The default language is english, which along with dutch, portuguese, and spanish supports phrase chunking and named entity recognition. T
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"text": "The/DT word/NN logorrhoea/NN is/VBZ often/RB used/VBN pejoratively/RB to/TO describe/VB prose/NN that/WDT is/VBZ highly/RB abstract/JJ and/CC contains/VBZ little/JJ concrete/JJ language/NN ./.. Since/IN abstract/NN writing/VBG is/VBZ hard/JJ to/TO visualize/VB ,/, it/PRP often/RB seems/VBZ as/IN though/IN it/PRP makes/VBZ no/DT sense/NN and/CC all/DT the/DT words/NNS are/VBP excessive/JJ ./.. Writers/NNS in/IN academic/JJ fields/NNS that/WDT concern/NN themselves/VBZ mostly/RB with/IN the/DT abstract/NN ,/, such/JJ as/IN philosophy/NN and/CC especially/RB postmodernism/NN ,/, often/RB fail/VBP to/TO include/VB extensive/JJ concrete/JJ examples/NNS of/IN their/PRP$ ideas/NNS ,/, and/CC so/RB a/DT superficial/JJ examination/NN of/IN their/PRP$ work/NN might/MD lead/VB one/CD to/TO believe/VB that/IN it/PRP is/VBZ all/DT nonsense/NN ./."}
                                                                                                                                                                                                                    
                                                                                                    

Text Tagging - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/1818/text+tagging+api/1479/text+tagging?text=The word logorrhoea is often used pejoratively  to describe prose that is highly abstract and  contains little concrete language. Since abstract  writing is hard to visualize, it often seems as though  it makes no sense and all the words are excessive.  Writers in academic fields that concern themselves mostly  with the abstract, such as philosophy and especially  postmodernism, often fail to include extensive concrete  examples of their ideas, and so a superficial examination  of their work might lead one to believe that it is all nonsense.&language=english' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Text Tagging API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
441ms

Category:

NLP

Related APIs