Horoscope is a simple tool for getting horoscope data. It returns the horoscope for the day.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Horoscope response payload
}
}
About the Horoscope API
Horoscope works by generating horoscope data based on the zodiac sign or birthdate provided. It returns the horoscope for the day in a structured format.
What people use it for
- Personal Guidance
- Use the Horoscope API to get personal guidance based on your zodiac sign. Use the data to gain insights into your day and make informed decisions
- Astrology Enthusiasts
- Explore astrology by using the Horoscope API to get horoscope data. Use the data to learn about zodiac signs, planetary influences, and astrological predictions
- Entertainment Apps
- Build entertainment apps by using the Horoscope API to get horoscope data. Use the data to provide users with fun and engaging content
- Daily Rituals
- Incorporate horoscopes into daily rituals by using the Horoscope API to get horoscope data. Use the data to help users start their day with positive energy and focus
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Horoscope
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Horoscope API do?
How do I authenticate Horoscope API requests?
How much does the Horoscope API cost?
How fast is the Horoscope API?
What response formats does the Horoscope API support?
What HTTP method does the Horoscope API use?
Request parameters — GET /v1/horoscope
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
signRequired | string | aries | The zodiac sign for which you want to get the horoscopeariestaurusgeminicancerleovirgolibrascorpio+4 |
curl "https://api.apiverve.com/v1/horoscope?sign=aries" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Response — GET /v1/horoscope
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"color": "green",
"compatibility": [
"leo",
"sagittarius"
],
"horoscope": "Today, the celestial alignment initiates a deep dive into your emotional landscapes, prompting you to analyze your hidden sentiments to strengthen existing links and navigate difficulties with loved ones more successfully. Open communication becomes essential, allowing you to gracefully balance individual desires. Financially, shrewd judgments keep a cautious route, reducing unnecessary risks and consolidating existing assets. Pay concentrated consideration not to let minor grievances cloud your judgement, strive to discover common understanding and resolve internal clashes diplomatically to facilitate individual advancement, reinforcing your bonds through vulnerability while navigating the ups and downs of interpersonal relationships cautiously keeping everything in balance.",
"luckyNumber": 12,
"luckyTime": "8:00 AM",
"mood": "excited",
"sign": "aries",
"zodiac": {
"element": "fire",
"name": "Aries",
"stone": "bloodstone",
"symbol": "♈"
}
}
}
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 |
|---|---|---|---|
colorPremium | string | "green" | Lucky color associated with zodiac sign today |
compatibilityPremium | array | [leo, ...] | Array of compatible zodiac signs for relationships |
horoscope | string | "Today, the celestial alignment initiates a deep dive into your emotional landscapes, prompting you to analyze your hidden sentiments to str… | Detailed horoscope prediction and guidance text |
luckyNumberPremium | number | 12 | Lucky number for today based on zodiac |
luckyTimePremium | string | "8:00 AM" | Auspicious time of day for activities (HH:MM AM/PM) |
moodPremium | string | "excited" | Predicted emotional mood for the day |
sign | string | "aries" | Zodiac sign name for the horoscope reading |
zodiac | object | {...} | |
elementPremium | string | "fire" | Element associated with zodiac sign (fire, earth, air, water) |
name | string | "Aries" | Full name of the zodiac sign with proper capitalization |
stonePremium | string | "bloodstone" | Birthstone or lucky gemstone for zodiac sign |
symbolPremium | string | "♈" | Astrological symbol glyph representing zodiac sign |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Horoscope calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/horoscope
No SDK to install — this is a plain HTTPS call to /v1/horoscope with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/horoscope" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/horoscope
Install the Node.js SDK, then call the Horoscope API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/horoscopeconst res = await fetch("https://api.apiverve.com/v1/horoscope", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/horoscope
Install the Python SDK, then call the Horoscope API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-horoscopeimport requests
res = requests.get(
"https://api.apiverve.com/v1/horoscope",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/horoscope
Install the C# / .NET SDK, then call the Horoscope API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.Horoscopeusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/horoscope");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/horoscope
No SDK to install — this is a plain HTTPS call to /v1/horoscope with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/horoscope", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/horoscope
No SDK to install — this is a plain HTTPS call to /v1/horoscope with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/horoscope");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/horoscope
No SDK to install — this is a plain HTTPS call to /v1/horoscope with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/horoscope")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Horoscope form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Horoscope API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Horoscope API.
Astrology
Related articles
All articles →
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read