---
title: SpaceX API
url: https://rone.dev/projects/spacex-api
description: Launch statistics, upcoming missions and Dragon tracking behind one REST contract.
language: en-US
updated: 2026-09-27
translations:
  id: https://rone.dev/id/projects/spacex-api
---

# SpaceX API

Launch statistics, upcoming missions and Dragon tracking behind one REST contract.

[Projects](https://rone.dev/projects) / [API](https://rone.dev/projects/category/api)

Live · Started 2025 · 1 GitHub stars · 0 Forks

<Frame>
  ![The SpaceX API root, listing its endpoints](https://rone.dev/projects/spacex-api/home.webp)
</Frame>

A Django REST interface over public SpaceX mission data: cumulative launch, landing and reflight statistics, upcoming and past launches with mission detail, and live Dragon capsule tracking. It is an independent project with no affiliation to SpaceX.

## Numbers

* **9** Endpoints
* **4** Endpoint groups
* **1.0.2** Version

## Project facts

|          |                                                                                           |
| -------- | ----------------------------------------------------------------------------------------- |
| Status   | Live                                                                                      |
| Category | API                                                                                       |
| Started  | 2025                                                                                      |
| Role     | Design, build, and operations                                                             |
| Stack    | Python, Django, Django REST Framework, Vercel                                             |
| Licence  | CC0-1.0                                                                                   |
| Links    | [Live API](https://spacex-api.rone.dev) · [Source](https://github.com/ridwaanhall/SpaceX) |

## Overview

Four groups, each its own Django app with its own serializers, exceptions and health check: statistics, upcoming launches, past launches, and Dragon tracking. The root endpoint is a directory — it names every other endpoint with an absolute URL and a description, so the API is discoverable without opening documentation first.

## Turning the data surface off at the URLconf

When the service needs to shed load, the data routes are not disabled inside each view — they are never registered. A single availability flag decides whether the app URL patterns are appended at all, so an unavailable deployment answers 404 for them rather than running a view that immediately gives up.

The root directory endpoint stays mounted either way, which means a caller can always reach something that explains the state. The alternative, a flag checked at the top of every view, is the same behaviour spread across a dozen places and forgotten in the thirteenth.

<CardGroup cols={2}>
  <Card title="Previous: Follow Dragon" href="https://rone.dev/projects/follow-dragon">
    A WebGL globe tracking SpaceX Dragon and the ISS in real time.
  </Card>

  <Card title="Next: Wilayah Indonesia API" href="https://rone.dev/projects/wilayah-indonesia-api">
    Every Indonesian province, regency, district and village under one URL scheme.
  </Card>
</CardGroup>