Fortune Teller API
Overview
To use Fortune Teller, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/fortunetellerExample
How to call the Fortune Teller API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/fortuneteller?category=general&question=What%20does%20the%20future%20hold%20for%20me%3F" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/fortuneteller?category=general&question=What%20does%20the%20future%20hold%20for%20me%3F', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/fortuneteller?category=general&question=What%20does%20the%20future%20hold%20for%20me%3F', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/fortuneteller?category=general&question=What%20does%20the%20future%20hold%20for%20me%3F", nil)
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))
}{
"status": "ok",
"error": null,
"data": {
"fortune": "The threads of destiny are weaving a tapestry of unexpected joy; embrace the unknown, for within its depths lie blossoms of serendipity. A golden opportunity awaits, carried upon the wings of synchronicity.",
"insight": "Trust in the whispers of your intuition; it shall guide you through the maze of life.",
"timeframe": "in the coming weeks",
"category": "general",
"question": null,
"luckyNumbers": [
87,
10,
16,
83,
99,
34
],
"luckyElement": "Wood",
"luckyColor": "Purple",
"luckyDay": "Tuesday",
"timestamp": "2025-12-16T22:23:31.796Z"
}
}Authentication
The Fortune Teller API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Fortune Teller API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Fortune Teller API:
Get AI Fortune Prediction
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
category | string | optional | Fortune category Supported values: generallovecareerhealthwealth | ||
question | string | optional | Optional question for personalized fortune (max 500 characters) Length: max: 500 chars | - |
Response
The Fortune Teller API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<fortune>The threads of destiny are weaving a tapestry of unexpected joy; embrace the unknown, for within its depths lie blossoms of serendipity. A golden opportunity awaits, carried upon the wings of synchronicity.</fortune>
<insight>Trust in the whispers of your intuition; it shall guide you through the maze of life.</insight>
<timeframe>in the coming weeks</timeframe>
<category>general</category>
<question xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<luckyNumbers>
<luckyNumber>87</luckyNumber>
<luckyNumber>10</luckyNumber>
<luckyNumber>16</luckyNumber>
<luckyNumber>83</luckyNumber>
<luckyNumber>99</luckyNumber>
<luckyNumber>34</luckyNumber>
</luckyNumbers>
<luckyElement>Wood</luckyElement>
<luckyColor>Purple</luckyColor>
<luckyDay>Tuesday</luckyDay>
<timestamp>2025-12-16T22:23:31.796Z</timestamp>
</data>
</response>
status: ok
error: null
data:
fortune: >-
The threads of destiny are weaving a tapestry of unexpected joy; embrace the
unknown, for within its depths lie blossoms of serendipity. A golden
opportunity awaits, carried upon the wings of synchronicity.
insight: >-
Trust in the whispers of your intuition; it shall guide you through the maze
of life.
timeframe: in the coming weeks
category: general
question: null
luckyNumbers:
- 87
- 10
- 16
- 83
- 99
- 34
luckyElement: Wood
luckyColor: Purple
luckyDay: Tuesday
timestamp: '2025-12-16T22:23:31.796Z'
| key | value |
|---|---|
| fortune | The threads of destiny are weaving a tapestry of unexpected joy; embrace the unknown, for within its depths lie blossoms of serendipity. A golden opportunity awaits, carried upon the wings of synchronicity. |
| insight | Trust in the whispers of your intuition; it shall guide you through the maze of life. |
| timeframe | in the coming weeks |
| category | general |
| question | |
| luckyNumbers | [87,10,16,83,99,34] |
| luckyElement | Wood |
| luckyColor | Purple |
| luckyDay | Tuesday |
| timestamp | 2025-12-16T22:23:31.796Z |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
fortune | string | - | |
insight | string | - | |
timeframe | string | - | |
category | string | - | |
question | object | - | |
luckyNumbers | array | - | |
luckyElement | string | - | |
luckyColor | string | - | |
luckyDay | string | - | |
timestamp | string | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Fortune Teller through GraphQL to combine it with other API calls in a single request. Query only the fortune teller data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
fortuneteller(
input: {
category: "general"
question: "What does the future hold for me?"
}
) {
fortune
insight
timeframe
category
question
luckyNumbers
luckyElement
luckyColor
luckyDay
timestamp
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Fortune Teller API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Fortune Teller requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Fortune Teller API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Fortune Teller
Official Fortune Teller packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Fortune Teller works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Fortune Teller?
How many credits does Fortune Teller cost?
Each successful Fortune Teller API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful fortune teller lookups.
Can I use Fortune Teller in production?
The free plan is for testing and development only. For production use of Fortune Teller, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Fortune Teller from a browser?
What happens if I exceed my Fortune Teller credit limit?
When you reach your monthly credit limit, Fortune Teller API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








