Birthstones API

About the Birthstones API

A birthstone API that returns birthstone data for any month, zodiac sign or gemstone name. Ask for May, or Taurus, or emerald, and you get back the matching month records with the primary stone, its traditional color and the zodiac signs that fall in that month. Ask for the full list and you get all twelve months in one response.

It is built for jewelry applications, astrology tools, gift recommendation engines and birthday features: a product page that suggests the right ring for a birth month, a horoscope app that shows a sign's stones, or a gift finder that works backwards from a gem a customer already likes.

The Free plan returns the month number and name, the primary stone, its color and the zodiac signs for each match. Paid plans add the alternate stones for each month, the stone's traditional meaning, its Mohs hardness, its mineral family and the wedding anniversary year it is associated with, which is enough to fill a full gemstone profile card.

How it works

Birthstones answers from a fixed twelve-row table, one row per month, so responses are instant and identical on every call. Each lookup returns a birthstones array and a count.

The parameters are checked in a fixed order: list=all first, then month, then zodiac, then stone. A call with none of them also returns the full table. month accepts a number from 1 to 12 or an English month name in any case; anything else returns a 404. zodiac is matched case-insensitively against each month's zodiacSigns, and because every sign straddles two months, a sign returns two rows. The response echoes the sign, capitalised, as zodiacSign. stone is an exact, case-insensitive name match against both primaryStone and alternateStones, so citrine finds November even though it is not November's primary stone. isPrimaryStone tells you which case you hit, and stone echoes your input.

hardness is the Mohs scale value (pearl is 2.5, diamond 10). mineralFamily is a classification such as Beryl, Corundum or Organic. anniversaryYear is the wedding anniversary traditionally tied to the stone, for example 55 for emerald.

On the Free plan, alternateStones, meaning, hardness, mineralFamily and anniversaryYear are removed from each row. A stone search still matches alternate stones on the Free plan; only the field listing them is hidden.

What people use it for

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

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

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/birthstones

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

1
2

curl "https://api.apiverve.com/v1/birthstones?month=5" \
  -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.

Response — GET /v1/birthstones

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

{
  "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.

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.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 1 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.

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.

Zero-code embed — one snippet, no backend

Drop an interactive Birthstones 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 — Birthstones 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.

Currently v1