Keyword ExtractorKeyword Extractor

Token Usage:5 per call

Keyword Extractor is a simple tool for extracting keywords from a web page. It returns the keywords and the frequency of each keyword.

This API provides reliable and fast access to keyword extractor data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use this API, you need an API key. You can get one by creating a free account and visiting your dashboard.

View API in Directory

Endpoint

POST Request
POST https://api.apiverve.com/v1/keywordextractor

Code Examples

Here are examples of how to call this API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/keywordextractor" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://en.wikipedia.org/wiki/Email_address"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/keywordextractor', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "url": "https://en.wikipedia.org/wiki/Email_address"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "url": "https://en.wikipedia.org/wiki/Email_address"
}

response = requests.post('https://api.apiverve.com/v1/keywordextractor', headers=headers, json=payload)

data = response.json()
print(data)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const postData = JSON.stringify({
  "url": "https://en.wikipedia.org/wiki/Email_address"
});

const req = https.request('https://api.apiverve.com/v1/keywordextractor', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.write(postData);
req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/keywordextractor');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
    'url': 'https://en.wikipedia.org/wiki/Email_address'
}));

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "url": "https://en.wikipedia.org/wiki/Email_address"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/keywordextractor", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/keywordextractor')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

payload = {
  "url": "https://en.wikipedia.org/wiki/Email_address"
}

request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

request.body = payload.to_json

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))

Authentication

This API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Parameters

The following parameters are available for this API endpoint:

ParameterTypeRequiredLocationDescriptionExample
textstringYesbodyThe text to extract keywords from-

Response

The API returns responses in JSON, XML, and YAML formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "url": "https://en.wikipedia.org/wiki/Email_address",
    "keywords": {
      "email": 91,
      "address": 61,
      "mail": 53,
      "domain": 34,
      "addresses": 34,
      "characters": 27,
      "retrieved": 27,
      "internet": 17,
      "message": 15,
      "validation": 12,
      "mailbox": 12,
      "errata": 12,
      "allowed": 12,
      "messages": 11,
      "systems": 10,
      "ietf": 10,
      "names": 10,
      "user": 10,
      "protocol": 10,
      "internationalized": 9,
      "solid": 9,
      "account": 8,
      "addressing": 8,
      "host": 8,
      "simple": 8,
      "transfer": 8,
      "mailboxes": 8,
      "character": 8,
      "quoted": 8,
      "additional": 7,
      "syntax": 7,
      "verification": 7,
      "form": 7,
      "format": 7,
      "klensin": 7,
      "july": 6,
      "tools": 6,
      "valid": 6,
      "internationalization": 6,
      "group": 6,
      "system": 6,
      "services": 6,
      "case": 6,
      "smtp": 6,
      "ascii": 6,
      "backslash": 6,
      "servers": 6,
      "server": 6,
      "original": 6,
      "archived": 6
    }
  }
}
XML Response
200 OK
<Root>
  <status>ok</status>
  <error />
  <data>
    <url>https://en.wikipedia.org/wiki/Email_address</url>
    <keywords>
      <email>91</email>
      <address>61</address>
      <mail>53</mail>
      <domain>34</domain>
      <addresses>34</addresses>
      <characters>27</characters>
      <retrieved>27</retrieved>
      <internet>17</internet>
      <message>15</message>
      <validation>12</validation>
      <mailbox>12</mailbox>
      <errata>12</errata>
      <allowed>12</allowed>
      <messages>11</messages>
      <systems>10</systems>
      <ietf>10</ietf>
      <names>10</names>
      <user>10</user>
      <protocol>10</protocol>
      <internationalized>9</internationalized>
      <solid>9</solid>
      <account>8</account>
      <addressing>8</addressing>
      <host>8</host>
      <simple>8</simple>
      <transfer>8</transfer>
      <mailboxes>8</mailboxes>
      <character>8</character>
      <quoted>8</quoted>
      <additional>7</additional>
      <syntax>7</syntax>
      <verification>7</verification>
      <form>7</form>
      <format>7</format>
      <klensin>7</klensin>
      <july>6</july>
      <tools>6</tools>
      <valid>6</valid>
      <internationalization>6</internationalization>
      <group>6</group>
      <system>6</system>
      <services>6</services>
      <case>6</case>
      <smtp>6</smtp>
      <ascii>6</ascii>
      <backslash>6</backslash>
      <servers>6</servers>
      <server>6</server>
      <original>6</original>
      <archived>6</archived>
    </keywords>
  </data>
</Root>
YAML Response
200 OK
status: ok
error: 
data:
  url: https://en.wikipedia.org/wiki/Email_address
  keywords:
    email: 91
    address: 61
    mail: 53
    domain: 34
    addresses: 34
    characters: 27
    retrieved: 27
    internet: 17
    message: 15
    validation: 12
    mailbox: 12
    errata: 12
    allowed: 12
    messages: 11
    systems: 10
    ietf: 10
    names: 10
    user: 10
    protocol: 10
    internationalized: 9
    solid: 9
    account: 8
    addressing: 8
    host: 8
    simple: 8
    transfer: 8
    mailboxes: 8
    character: 8
    quoted: 8
    additional: 7
    syntax: 7
    verification: 7
    form: 7
    format: 7
    klensin: 7
    july: 6
    tools: 6
    valid: 6
    internationalization: 6
    group: 6
    system: 6
    services: 6
    case: 6
    smtp: 6
    ascii: 6
    backslash: 6
    servers: 6
    server: 6
    original: 6
    archived: 6

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Response Data Fields

When the request is successful, the data object contains the following fields:

FieldTypeSample Value
urlstring"https://en.wikipedia.org/wiki/Email_address"
keywordsobject{...}
keywords.emailnumber91
keywords.addressnumber61
keywords.mailnumber53
keywords.domainnumber34
keywords.addressesnumber34
keywords.charactersnumber27
keywords.retrievednumber27
keywords.internetnumber17
keywords.messagenumber15
keywords.validationnumber12
keywords.mailboxnumber12
keywords.erratanumber12
keywords.allowednumber12
keywords.messagesnumber11
keywords.systemsnumber10
keywords.ietfnumber10
keywords.namesnumber10
keywords.usernumber10

Headers

Required and optional headers for API requests:

Header NameRequiredExample ValueDescription
X-API-KeyYesyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
AcceptNoapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentNoMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDNoreq_123456789Custom request identifier for tracking and debugging requests
Cache-ControlNono-cacheControl caching behavior for the request and response

Client Libraries

To get started with minimal code, most of our APIs are available through client libraries and clients:

Run in PostmanNPMPyPINuGetSwagger

Error Codes

The API uses standard HTTP status codes to indicate success or failure:

Status CodeMessageDescription
200OKRequest successful, data returned
400Bad RequestInvalid request parameters or malformed request
401UnauthorizedMissing or invalid API key
403ForbiddenAPI key does not have permission for this endpoint
429Too Many RequestsRate limit exceeded, please slow down requests
500Internal Server ErrorServer error, please try again later

What's Next?

Continue your journey with these recommended resources

Was this page helpful?

Help us improve our documentation