Put accurate mass, distance, and classification behind any star name.
Stars Lookup retrieves physical and positional stellar data by star name or astronomical classification. Query individual stars or filter by spectral class to obtain mass in kilograms, distance in light-years, and stellar type.
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": {
"starName": "Sirius",
"mass": 4.674385e+30,
"diameter": 2825760,
"galX": -5.895,
"galY": -6.152,
"galZ": -1.167,
"dist": 8.6,
"starType": "A1(V)",
"temp": 9500,
"color": "0xbaccff"
}
}
About the Stars Lookup API
A star lookup API for physical and positional data on named stars. Requests accept a specific star name such as Sirius or Betelgeuse, or an astronomical classification, such as spectral codes, spectral classes, or categories like red dwarf and supergiant. Classification queries return up to ten matching entries. Each record supplies mass in kilograms, distance in light-years, and stellar classification.
Education apps, planetarium and stargazing tools, games with real star maps and science content sites use it to show facts about a star without maintaining their own catalogue. Searching by type makes it easy to list example main sequence stars or white dwarfs for a lesson or quiz.
The Free plan returns the star name, mass, distance and spectral type. Paid plans add surface temperature, diameter, hex color codes for drawing the star in its true tint, 3D galactic coordinates for plotting positions, and the HYG catalogue fields: apparent and absolute magnitude, right ascension and declination, constellation, Hipparcos and HD numbers, and Bayer, Flamsteed and IAU proper names.
How it works
A name query matches the whole star name, ignoring case, accents, spacing and the degree sign, and treating Gliese, GJ and Gl as the same prefix, so Xi Bootis finds Xi Boötis and Gliese 618 B finds Gl 618 B. Partial names are not matched, and an unknown name returns 404.
A type query is matched in three steps, and the first step with results wins. First, an exact spectral code, with or without brackets and spaces, so A1V matches A1(V). Second, a class name mapped to the luminosity suffix stored in the data: supergiant (I), bright giant (II), giant (III), subgiant (IV), main sequence or dwarf (V), red dwarf (M-type V) and white dwarf (wd); spaces, hyphens and a trailing star or stars are ignored. Third, a spectral class prefix such as G, K5 or DA. Stars without a recorded type are skipped. For a type query, the first match is returned at the top level and stars lists up to the first 10 matches in catalogue order; count is the length of that list, not the total number of matches.
mass is in kilograms and dist in light-years. starType is the spectral code with the luminosity class in brackets, such as A1(V). temp is the effective surface temperature in Kelvin and diameter the diameter in kilometres (see below), color a hex colour written as 0xRRGGBB, and galX, galY and galZ are galactic coordinates whose combined length matches dist. diameter, temp, color and the three coordinates are null on the Free plan.
The catalogue is a list of about 2,600 nearby and named stars. Each month it is cross-matched against the HYG star database (v4.x, by David Nash / astronexus, codeberg.org/astronexus/hyg, licensed CC BY-SA 4.0), which combines the Hipparcos, Yale Bright Star and Gliese catalogues. A star is matched by its proper name or by its Bayer, Flamsteed, variable-star or Gliese designation, and only when HYG's distance agrees with the stored one. For matched stars, temp is derived from the measured B-V colour index with the Ballesteros (2012) formula; for O and B stars, whose B-V colour barely changes with temperature, the temperature that goes with the spectral type is kept. diameter is then derived from HYG's luminosity, converted from visual to bolometric with the Flower (1996) bolometric correction, and the temperature, using the Stefan-Boltzmann law (D = 2 R☉ × √L × (5772 K / T)²). The Sun keeps its measured values (1,392,000 km, 5772 K).
Derived diameters are estimates. Checked against measured sizes, Sirius, Vega, Procyon, Rigel and Arcturus land within 15%; red dwarfs such as Proxima Centauri and Barnard's Star come out at about half their true size, and distant giants and supergiants (Betelgeuse, Antares, Deneb, Aldebaran, Polaris) can be off by 30-70%, because their colours and distances are the least certain. Stars that cannot be matched keep their catalogue values, and diameter is null where no diameter is known. mass is null for stars with no recorded mass, which includes Polaris, Canopus and most white dwarfs. Mass, distance, coordinates, spectral type and colour are not taken from HYG.
What people use it for
- Planetarium Display Systems
- Stargazing apps query star names to show visitors distance from Earth, stellar classification, and real celestial mass during live sky tours.
- Sci-Fi Worldbuilding
- To build believable galaxy maps, game developers pull spectral classes like red dwarf or main sequence to seed star systems with authentic physics.
- Astronomy Curriculum Portals
- When students compare celestial bodies, digital textbooks pull mass in kilograms and stellar types to demonstrate the Hertzsprung-Russell relationship.
- Telescope Calibration Software
- Align optical tracking mounts by looking up known reference stars to verify catalog identity and light-year distance against visual field observations.
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 Stars Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
Is it cheap enough to look up star data for every search query in my app?
Are star diameter, temperature, and coordinates included on the Free plan?
Can I search for stars by classification instead of a specific name?
What units of measurement are used for the returned values?
Where do the temperatures and diameters come from?
Can I use this star data inside a commercial stargazing app?
Request parameters — GET /v1/starslookup
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 |
|---|---|---|---|
nameRequired | string | Sirius | The name of the star (e.g., Sirius). IAU proper names (Rigil Kentaurus), Bayer designations (Alpha Orionis or alf Ori), Flamsteed numbers (58 Ori), HD and HIP numbers (HD 48915) and common names (Sun, North Star) are also accepted |
curl "https://api.apiverve.com/v1/starslookup?name=Sirius" \
-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/starslookup
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": {
"starName": "Sirius",
"mass": 4.674385e+30,
"diameter": 2825760,
"galX": -5.895,
"galY": -6.152,
"galZ": -1.167,
"dist": 8.6,
"starType": "A1(V)",
"temp": 9500,
"color": "0xbaccff"
}
}
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 |
|---|---|---|---|
starName | string | "Sirius" | The name of the star |
mass | number | 4.674385e+30 | Mass of the star in kilograms; null when no mass is recorded |
diameterPremium | number | 2825760 | Diameter of the star in kilometers |
galXPremium | number | -5.895 | Galactic X coordinate position |
galYPremium | number | -6.152 | Galactic Y coordinate position |
galZPremium | number | -1.167 | Galactic Z coordinate position |
dist | number | 8.6 | Distance to star in light-years |
starType | string | "A1(V)" | Stellar classification type (e.g., A1V) |
tempPremium | number | 9500 | Surface temperature of the star in Kelvin |
colorPremium | string | "0xbaccff" | Color representation as hex code |
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 | Stars Lookup 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/starslookup
No SDK to install — this is a plain HTTPS call to /v1/starslookup 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/starslookup" \
-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/starslookup
Install the Node.js SDK, then call the Stars Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/starslookupconst res = await fetch("https://api.apiverve.com/v1/starslookup", {
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/starslookup
Install the Python SDK, then call the Stars Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-starslookupimport requests
res = requests.get(
"https://api.apiverve.com/v1/starslookup",
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/starslookup
Install the C# / .NET SDK, then call the Stars Lookup 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.StarsLookupusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/starslookup");
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/starslookup
No SDK to install — this is a plain HTTPS call to /v1/starslookup 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/starslookup", 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/starslookup
No SDK to install — this is a plain HTTPS call to /v1/starslookup 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/starslookup");
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/starslookup
No SDK to install — this is a plain HTTPS call to /v1/starslookup 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/starslookup")
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 Stars Lookup 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 — Stars Lookup 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 Stars Lookup API.
Science
Related articles
All articles →
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
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read