Part-Of-Speech Tagging API

This API will help you tag different parts of any speech provided. Tags the provided text with parts of speech (such as nouns, verbs, adjectives, adverbs, etc.)

About the API:

In corpus linguistics, part-of-speech tagging (POS tagging or PoS tagging or POST), also called grammatical tagging is the process of marking up a word in a text (corpus) as corresponding to a particular part of speech,[1] based on both its definition and its context. A simplified form of this is commonly taught to school-age children, in the identification of words as nounsverbsadjectivesadverbs, etc.

 

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

Pass any text to this API as a JSON, and receive all the possible tags for the different parts of the speech.  

 

What are the most common uses cases of this API?

 

Use this API to retrieve semantic information from given texts. 

Great API for Machine Learning training. Use the data to train your models so they can easily recognize different parts of the speech as well. 

 

Are there any limitations to your plans?

Besides API call limitations per month, there are no other limitations.

API Documentation

Endpoints


Tags the provided text with parts of speech (such as nouns, verbs, adjectives, adverbs, etc.).

Part-of-Speech Labels:
CC - Coordinating conjunction
CD - Cardinal number
DT - Determiner
EX - Existential there
FW - Foreign word
HYPH - Hyphen
IN - Preposition or subordinating conjunction
JJ - Adjective
JJR - Adjective, comparative
JJS - Adjective, superlative
LS - List item marker
MD - Modal
NFP - Superfluous punctuation
NN - Noun, singular or mass
NNP - Proper noun, singular
NNPS - Proper noun, plural
NNS - Noun, plural
PDT - Predeterminer
POS - Possessive ending
PRP - Personal pronoun
PRP$ - Possessive pronoun
RB - Adverb
RBR - Adverb, comparative
RBS - Adverb, superlative
RP - Particle
SYM - Symbol
TO - to
UH - Interjection
VB - Verb, base form
VBD - Verb, past tense
VBG - Verb, gerund or present participle
VBN - Verb, past participle
VBP - Verb, non-3rd person singular present
VBZ - Verb, 3rd person singular present
WDT - Wh-determiner
WP - Wh-pronoun
WP$ - Possessive wh-pronoun
WRB - Wh-adverb
XX - Unknown
ADD - Email
AFX - Affix



                                                                            
POST https://zylalabs.com/api/821/part-of-speech+tagging+api/580/pos+tagging
                                                                            
                                                                        

POS Tagging - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"badRequest": false, "creditsUsed": 1, "errors": [], "forbidden": false, "invalidSession": false, "noSessionFound": false, "notAuthorized": false, "sentences": [{"tokens": [{"labels": [{"label": "EX", "score": 0.9999990463256836}], "text": "There"}, {"labels": [{"label": "VBZ", "score": 0.9999969005584717}], "text": "is"}, {"labels": [{"label": "DT", "score": 0.9999946355819702}], "text": "a"}, {"labels": [{"label": "NN", "score": 0.999990701675415}], "text": "house"}, {"labels": [{"label": "IN", "score": 0.9999613761901855}], "text": "by"}, {"labels": [{"label": "DT", "score": 0.9999933242797852}], "text": "the"}, {"labels": [{"label": "NN", "score": 0.9998831748962402}], "text": "lake"}, {"labels": [{"label": "WDT", "score": 0.993063747882843}], "text": "that"}, {"labels": [{"label": "PRP", "score": 1.0}], "text": "we"}, {"labels": [{"label": "MD", "score": 0.9999997615814209}], "text": "could"}, {"labels": [{"label": "VB", "score": 0.9998855590820312}], "text": "use"}, {"labels": [{"label": "DT", "score": 0.999998927116394}], "text": "this"}, {"labels": [{"label": "NN", "score": 0.9999990463256836}], "text": "summer"}, {"labels": [{"label": ".", "score": 0.9999368190765381}], "text": "."}]}], "statusCode": 200, "tooManyRequests": false}
                                                                                                                                                                                                                    
                                                                                                    

POS Tagging - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/821/part-of-speech+tagging+api/580/pos+tagging' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
    "text": "There is a house by the lake that we could use this summer."
}'

    

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 Part-Of-Speech 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]

 Service Level
100%
 Response Time
882ms

Category:

NLP

Related APIs