Overview
Tense Converter works by analyzing the text provided and converting it to the past or future tense. It uses advanced algorithms to convert the text to the specified tense and returns the converted text.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/tenseconverter \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "I am walking down the street, and I can see a dog",
"tense": "past"
}'const res = await fetch('https://api.apiverve.com/v1/tenseconverter', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "I am walking down the street, and I can see a dog",
"tense": "past"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/tenseconverter",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "I am walking down the street, and I can see a dog",
"tense": "past"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "I am walking down the street, and I can see a dog",
"tense": "past"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/tenseconverter", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
textRequired | string | The text to convert to past or future tense |
tenseRequired | string | The tense to convert the text topastfuturedefault past |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"tense": "past",
"result": "I was walking down the street, and I could see a dog",
"changed": true
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
tense | string | "past" | The target tense conversion applied (past or future) |
result | string | "I was walking down the street, and I could see a dog" | Converted text with applied tense transformation |
changed | boolean | true | Whether the text was modified during conversion |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Content Generation
- Use the Tense Converter API to convert text to past or future tense for content generation. Use the data to create variations, improve readability, and enhance engagement
- Language Processing
- Convert text to past or future tense by using the Tense Converter API for language processing. Use the data to analyze text, extract meaning, and enhance understanding
- Text Analysis
- Use the Tense Converter API to convert text to past or future tense for text analysis. Use the data to analyze language, extract insights, and improve comprehension
- Writing Assistance
- Convert text to past or future tense by using the Tense Converter API for writing assistance. Use the data to improve grammar, enhance style, and refine language
Other ways to use Tense Converter
Set up Tense Converter on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Text Processing: