NewAPIVerve Academy: free courses and certifications anyone can verify.Explore the Academy →

Stars Lookup API

GET

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

Request
GETapi.apiverve.com/v1/starslookup?name=Sirius
Query parameters
Verification
Format

No key required to try it. Get a key to use it in your app.

Example
{
  "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
Beta
GraphQL
Query language
New
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.

Questions.

Common questions about the Stars Lookup API.

Read the docs →
Is it cheap enough to look up star data for every search query in my app?
Yes. Each lookup costs 2 credits, which works out to about $0.0003 per call on the Starter plan, or $0.30 per 1,000 lookups. The Starter plan covers up to 100,000 lookups each month, while the Free plan gives you 100 calls monthly for testing.
Are star diameter, temperature, and coordinates included on the Free plan?
No. The diameter, surface temperature, hex color, and galactic X, Y, and Z coordinates are premium fields. On the Free plan, lookups return core data like mass, distance, and stellar classification. Upgrading to any paid plan unlocks all premium fields.
Can I search for stars by classification instead of a specific name?
Yes. The API provides two separate lookup methods: you can query by a specific star name like Sirius, or search by star classification type such as Supergiant.
What units of measurement are used for the returned values?
Star mass is returned in kilograms and distance is in light-years on every plan; on paid plans, diameter is in kilometers and surface temperature is provided in Kelvin. On paid plans, positional data is given as galactic X, Y, and Z coordinates, alongside a hex code for star color.
Where do the temperatures and diameters come from?
They are derived from measurements in the HYG star database (by David Nash / astronexus, CC BY-SA 4.0), which combines the Hipparcos, Yale Bright Star and Gliese catalogues. Temperature comes from each star's measured B-V colour, and diameter from its luminosity and temperature via the Stefan-Boltzmann law, so they are estimates rather than direct measurements: typically within 15% for bright main-sequence stars, and less accurate for red dwarfs and supergiants. The data is checked against HYG monthly. If you display the temperatures or diameters, credit the HYG database (astronexus, CC BY-SA 4.0).
Can I use this star data inside a commercial stargazing app?
Yes, provided you are on a paid plan. Commercial use is permitted across all paid tiers, and you may display the data directly to your users. You cannot resell or redistribute the catalog as a standalone dataset. The exception is the `temp` and `diameter` values, which are derived from the HYG star database and licensed CC BY-SA 4.0: you may reuse those under the same licence, crediting "HYG database (astronexus), CC BY-SA 4.0".

Ready to build with Stars Lookup? Start with 200 free credits — one key unlocks all 404+ APIs.

Explore the catalog

404+ APIs on the same key and the same response shape.

Browse all APIs