How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Astronomy API v3

Version 3 of the Astronomy API, published by the provider as a reference draft with a complete OpenAPI 3.1 definition before it ships — "so that the design can be read and argued with". A breaking redesign of the v2 request and response shapes: JSON numbers instead of strings, one representation per value, a declared meta.units block, ISO 8601 instants with an explicit sampling step and timezone, cursor pagination on positions, RFC 9457 problem details, bearer authentication, and apsis events alongside eclipses. Five operations across positions, events, search and the two studio renderers. NOT YET IN PRODUCTION — /api/v2 remains the callable surface.

Astronomy API v3 is one of 6 APIs that Astronomy API publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Astronomy, Positions, Events, and Star Charts. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 5 paths, organized into 3 resource areas, and defines 28 schemas. It is described by OpenAPI 3.1.0, at version 3.0.

Requests are made against a single base URL, https://api.astronomyapi.com/api/v3.

5 operations 5 paths 28 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.0
Base URL
https://api.astronomyapi.com/api/v3
Authentication
HTTP Bearer
Resource Areas
3

Authentication & Security 1

Astronomy API v3 declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (applicationKey). By default, every request must be authenticated.

  • applicationKey — The application key, sent as Authorization: Bearer . Keys are never accepted in the query string, where they would be recorded in logs and browser history.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. They span 3 resource areas: Bodies, Search, Studio. Each is listed below with its method, path, parameters, and response codes.

Bodies 2

Where the Sun, the Moon and the planets are, and what they look like.

GET
/positions
Positions of one or more bodies over a span of time
getPositions 13 params → 200400401422
GET
/events
Eclipses and apsides for the observer's location
getEvents 8 params → 200400401422
Search 1

The catalogue of deep sky objects and stars.

GET
/search
Find deep sky objects and stars
search 7 params → 200400401422
Studio 2

Rendered images of the sky.

POST
/studio/star-chart
Render a star chart
createStarChart body → 200400401422
POST
/studio/moon-phase
Render the Moon's phase
createMoonPhase body → 200400401422

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Sample (11 properties), CatalogueObject (8 properties), EclipseEvent (8 properties), Contacts (6 properties). Each schema is shown below with its type and property counts.

PositionsResponse
object
2 properties 2 required
Meta
object
5 properties 5 required
Observer
object
3 properties 3 required
Sampling
object
5 properties 4 required
BodySamples
object
2 properties 2 required
BodyId
string
Stable lowercase identifier for a body. This is the complete set.
BodyIdentity
object
2 properties 2 required
Sample
object
11 properties 7 required
Distance
object
2 properties 2 required
Constellation
object
2 properties 2 required
Phase
object
Returned for the Moon only.
3 properties 3 required
Formatted
object
Sexagesimal renderings of the angles above, present only when include=formatted is given.
4 properties
Problem
object
An error, as RFC 9457 problem details. v2 returned the raw output of its schema validator, which exposed internal paths such as instance.latitude and had no st…
5 properties 3 required
EventsResponse
object
2 properties 2 required
Event
An event is one of two shapes, told apart by type. Eclipses carry the moments they pass from one stage to the next; apsides carry a distance. Neither has the o…
EclipseEvent
object
8 properties 5 required
ApsisEvent
object
The moment a body's distance from the Earth stops changing direction. Every body has these, and they alternate. For the Moon they are the familiar perigee and…
5 properties 4 required
Contacts
object
The moments the eclipse passes from one stage to the next, each with the altitude of the body at that instant so it is clear how much of the event is above the…
6 properties 2 required
Contact
object
2 properties 2 required
SearchResponse
object
2 properties 2 required
CatalogueObject
object
8 properties 5 required
NamedType
object
2 properties 2 required
StudioRequest
object
What the studio endpoints share. time sits beside observer rather than inside it as v2 had it; a moment is not a property of a place.
3 properties 2 required
StarChartRequest
AreaView
object
A patch of sky centred on a given position.
2 properties 2 required
ConstellationView
object
Framed on a named constellation.
2 properties 2 required
MoonPhaseRequest
ImageResult
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

astronomy-api-v3-openapi.yaml Raw ↑

Other APIs Astronomy API publishes across the network.

Astronomy API
Astronomy API Bodies API
Astronomy API Events API
Astronomy API Search API
Astronomy API Studio API
Where this information came from

This is an independent, third-party profile of Astronomy API v3, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.