Overview
Perfect for jewelry applications, astrology tools, gift recommendation engines, or any application that needs accurate birthstone data. Returns both traditional and modern birthstone options for each month.
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 "https://api.apiverve.com/v1/birthstones?month=5" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/birthstones?month=5', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/birthstones?month=5",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/birthstones?month=5", nil)
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 in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
monthRequired | string | The month number (1-12) or name12345678+16 |
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": {
"count": 1,
"birthstones": [
{
"month": 5,
"monthName": "May",
"primaryStone": "Emerald",
"alternateStones": [
"Chrysoprase",
"Agate"
],
"color": "Green",
"meaning": "Rebirth, love, fertility",
"zodiacSigns": [
"Taurus",
"Gemini"
],
"hardness": 7.5,
"mineralFamily": "Beryl",
"anniversaryYear": 55
}
]
}
}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 |
|---|---|---|---|
count | number | 1 | Number of months returned |
birthstones | array[1] | The birthstones for each month requested | |
month | number | 5 | Birth month number from 1 to 12 |
monthName | string | "May" | Full name of the birth month |
primaryStone | string | "Emerald" | Primary gemstone for the month |
alternateStonesPremium | array | [Chrysoprase, ...] | Alternate gemstones associated with month |
color | string | "Green" | Traditional color associated with stone |
meaningPremium | string | "Rebirth, love, fertility" | Symbolism and meaning of the birthstone |
zodiacSigns | array | [Taurus, ...] | Zodiac signs associated with month |
hardnessPremium | number | 7.5 | Mohs hardness rating of gemstone |
mineralFamilyPremium | string | "Beryl" | Mineral classification family |
anniversaryYearPremium | number | 55 | Anniversary year associated with stone |
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
- Jewelry E-commerce
- Display relevant birthstone options for gift recommendations
- Astrology Applications
- Show birthstones associated with zodiac signs
- Gift Finder Tools
- Suggest personalized gemstone gifts based on birth month
- Educational Content
- Provide gemstone information for learning applications
Other ways to use Birthstones
Set up Birthstones 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 Reference Data: