API — UPSA Object Registry

Public API

v1 · JSON · no key

Read-only, unauthenticated, rate limited by common sense. Everything the pages show is available as JSON. If you build on it, keep the archive attribution described on Sources — the underlying CDS material is ODbL.

Endpoint	Does
GET /api/v1/stats	Holdings: object, measurement and identifier counts, breakdown by class.
GET /api/v1/search?q=	Resolve a name or identifier against the register.
GET /api/v1/suggest?q=	Type-ahead: up to eight matches on the name prefix.
GET /api/v1/object/{slug}	The whole card: identifiers, summary values, orbit or planet block, every published measurement with unit, uncertainty, source and citation, and the provenance list.
GET /api/v1/cone?ra=&dec=&r=	Everything held within a cone. Degrees, ICRS. Radius capped at 5°.
GET /api/v1/ephemeris/{slug}	Where a Solar System body is right now — geocentric RA/Dec, apparent magnitude, distance from Sun and Earth, solar elongation. Computed by JPL Horizons on request, because a position is not a stored property.
GET /api/v1/skymap	Counts of held objects on a coarse RA/Dec grid — the data behind the map on the front page.
POST /api/v1/harvest/{slug}	Ask the registry to re-read the archives for one object now.

Shape of a measurement

{
  "parameter": "parallax",
  "value": 6.55,
  "unit": "mas",
  "err_plus": 0.83,
  "err_minus": 0.83,
  "band": null,
  "method": null,
  "source": "simbad",
  "reference": "2008AJ....135.1430H",
  "ref_year": 2008
}

A parameter usually carries several rows. That is the point: the register does not decide which published value is correct.