# SpaceX Launches – Missions, Vehicles & Timelines (`abotapi/spacex-com`) Actor

Pull the full SpaceX launch catalog from spacex.com in clean JSON. Filter by vehicle, mission type, status, launch site, or date range. Returns vehicle, mission status, sites, date/time, images, mission links, and optional write-ups, webcasts, timelines, and carousel imagery.

- **URL**: https://apify.com/abotapi/spacex-com.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** Other, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SpaceX Launches Scraper

Pull the full SpaceX launch catalog from spacex.com in clean JSON. Every Falcon 1, Falcon 9, Falcon Heavy, and Starship launch comes through with its vehicle, mission type, status, launch and return site, date and time, hero images, and a direct link to the mission page. Filter by vehicle, mission type, status, launch site, or date range, then optionally enrich each launch with the full mission write-up, webcasts, pre and post launch timelines, and carousel imagery.

### Why this scraper

- Covers the entire launch history plus upcoming and in-progress missions, roughly 680 launches, in a single fast run.
- Pulls structured fields straight from the site's own content feed, so the data matches what you see on the page.
- Two modes: search the whole catalog with filters, or fetch specific mission pages by URL.
- Optional mission detail adds long-form descriptions, webcasts, timelines, astronauts, and image carousels.
- Runs on Apify datacenter proxy, no special plan required.
- Client-side filters for vehicle, mission type, status, launch site, and date range, with date sorting.

### Data you get

> Sample values from a real launch (Starlink mission sl-10-22).

| Field | Example |
| --- | --- |
| missionId | `sl-10-22` |
| title | `Starlink Mission` |
| url | `https://www.spacex.com/launches/sl-10-22` |
| vehicle | `Falcon 9` |
| missionType | `starlink` |
| missionStatus | `final` |
| launchSite | `SLC-40, Florida` |
| returnSite | `Droneship` |
| launchDate | `2025-09-03` |
| launchTime | `07:56:00` |
| launchDateTime | `2025-09-03T07:56:00` |
| callToAction | `WATCH` |
| directToCell | `false` |
| imageDesktopUrl | `https://sxcontent9668.azureedge.us/cms-assets/assets/Star10_22_090325_DSC_5054_desktop_880fa69c3c.jpg` |
| imageMobileUrl | `https://sxcontent9668.azureedge.us/cms-assets/assets/Star10_22_090325_DSC_5058_mobile_cdcdcdbda6.jpg` |
| description | `On Wednesday, September 3 at 7:56 a.m. ET, Falcon 9 launched 28 Starlink satellites to low-Earth orbit...` (detail only) |
| webcasts | full objects: videoId, streamingVideoType, title, date, **+ thumbnails** (detail only) |
| webcastVideoIds | `["1961181999567368275"]` (detail only) |
| webcastVideoUrls | `["https://x.com/i/status/1961181999567368275"]` (detail only) |
| primaryVideoUrl / videoUrls | first available video URL + all mission, webcast, and carousel video URLs |
| carousel | full items: imageDesktop, imageMobile, videoDesktop, videoMobile, caption (detail only) |
| carouselImageUrls / carouselMobileImageUrls / carouselVideoUrls | flat URL lists pulled from the carousel (detail only) |
| astronauts | full objects: name, bioLink, description, portrait (detail only) |
| astronautPortraitUrls | `["https://sxcontent9668.azureedge.us/cms-assets/assets/...jpg"]` (detail only) |
| videoDesktop / videoDesktopUrl | mission-level video object + `.mp4` URL when present (rare; detail only) |
| ongoingMissionImageDesktopUrl / ongoingMissionImageMobileUrl | live-mission image URLs when present |
| infographicDesktopUrl / infographicMobileUrl | infographic image URLs (detail only) |
| preLaunchTimeline / postLaunchTimeline | full countdown + deployment timelines (detail only) |
| media | raw media block, passed through verbatim (detail only) |

### How to use

Search the whole catalog (newest first, 20 launches):

```json
{
  "mode": "search",
  "maxListings": 20,
  "sortBy": "date-desc",
  "proxy": { "useApifyProxy": true }
}
```

Only Starship launches, with full mission detail:

```json
{
  "mode": "search",
  "vehicle": "Starship",
  "fetchDetails": true,
  "maxListings": 0,
  "proxy": { "useApifyProxy": true }
}
```

Resupply missions to a specific site in a date window:

```json
{
  "mode": "search",
  "missionType": "resupply",
  "launchSiteContains": "Florida",
  "dateFrom": "2023-01-01",
  "dateTo": "2023-12-31",
  "proxy": { "useApifyProxy": true }
}
```

Fetch specific mission pages by URL:

```json
{
  "mode": "url",
  "urls": [
    "https://www.spacex.com/launches/sl-10-22",
    "https://www.spacex.com/launches/starship-flight-12"
  ],
  "proxy": { "useApifyProxy": true }
}
```

### Input parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| mode | string | `search` | `search` filters the full catalog; `url` fetches the mission pages you paste. |
| vehicle | string | (any) | Limit to one vehicle: Falcon 9, Falcon Heavy, Falcon 1, Starship. |
| missionType | string | (any) | Limit to one mission type, e.g. starlink, resupply, nssl, hsf. |
| statusFilter | string | `all` | `past`, `upcoming`, `in-progress`, or `all`. |
| launchSiteContains | string | (none) | Case-insensitive substring match on the launch site. |
| dateFrom | string | (none) | Keep launches on or after this date (YYYY-MM-DD). |
| dateTo | string | (none) | Keep launches on or before this date (YYYY-MM-DD). |
| sortBy | string | `date-desc` | `date-desc` (newest first) or `date-asc` (oldest first). |
| urls | array | (none) | Mission page URLs, used only in url mode. |
| fetchDetails | boolean | `false` | Add the mission write-up, webcasts, timelines, and carousel per launch. |
| maxListings | integer | `20` | Max launches to return. `0` means no limit. |
| proxy | object | Apify datacenter | Proxy configuration. Datacenter is sufficient. |

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape — the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record — not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Output example

> Real record from a search-mode run (detail fields appear when fetchDetails is on).

```json
{
  "id": 2997,
  "documentId": "et9uhh0s8y7yv1novosnx0lj",
  "missionId": "sl-10-22",
  "url": "https://www.spacex.com/launches/sl-10-22",
  "title": "Starlink Mission",
  "shortTitle": null,
  "vehicle": "Falcon 9",
  "missionType": "starlink",
  "missionStatus": "final",
  "launchSite": "SLC-40, Florida",
  "returnSite": "Droneship",
  "launchDate": "2025-09-03",
  "launchTime": "07:56:00",
  "launchDateTime": "2025-09-03T07:56:00",
  "callToAction": "WATCH",
  "directToCell": false,
  "isLive": false,
  "imageDesktopUrl": "https://sxcontent9668.azureedge.us/cms-assets/assets/Star10_22_090325_DSC_5054_desktop_880fa69c3c.jpg",
  "imageMobileUrl": "https://sxcontent9668.azureedge.us/cms-assets/assets/Star10_22_090325_DSC_5058_mobile_cdcdcdbda6.jpg",
  "hasDetails": false
}
```

### Plan requirement

This actor runs on the Apify free plan with the default datacenter proxy. The data source is an open content feed with no geographic restriction, so residential proxy is optional and only useful if you want extra IP rotation. Set `maxListings` to `0` to pull the entire catalog in one run.

# Actor input Schema

## `mode` (type: `string`):

Choose 'search' to pull the full launch catalog with filters, or 'url' to fetch specific mission pages you paste below.

## `vehicle` (type: `string`):

Limit results to a single launch vehicle. Leave as 'Any' for all vehicles.

## `missionType` (type: `string`):

Limit results to a single mission type.

## `statusFilter` (type: `string`):

Past = completed launches, Upcoming = scheduled, In progress = currently live. 'All' returns every status.

## `launchSiteContains` (type: `string`):

Optional text match against the launch site, e.g. 'Florida', 'California', 'SLC-40', 'Starbase'. Case-insensitive substring.

## `dateFrom` (type: `string`):

Only keep launches on or after this date (YYYY-MM-DD). Applies to launches that have a known date.

## `dateTo` (type: `string`):

Only keep launches on or before this date (YYYY-MM-DD). Applies to launches that have a known date.

## `sortBy` (type: `string`):

Order of the returned launches.

## `urls` (type: `array`):

Paste one or more mission page URLs, e.g. https://www.spacex.com/launches/sl-10-22. Used only when mode is 'url'. Detail is always fetched for these.

## `fetchDetails` (type: `boolean`):

When on, each launch is enriched with an extra mission-page request that adds the write-up paragraphs, webcasts, pre/post-launch timelines, carousel images, and astronauts. Adds time and cost per launch.

## `maxListings` (type: `integer`):

Maximum number of launches to return. Set 0 for no limit (the full catalog is ~680 launches).

## `proxy` (type: `object`):

Apify datacenter proxy is enough; the data source is an open JSON API with no geo restriction. Residential is optional.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON — the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "vehicle": "",
  "missionType": "",
  "statusFilter": "all",
  "sortBy": "date-desc",
  "urls": [
    "https://www.spacex.com/launches/sl-10-22"
  ],
  "fetchDetails": false,
  "maxListings": 20,
  "proxy": {
    "useApifyProxy": true
  },
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "urls": [
        "https://www.spacex.com/launches/sl-10-22"
    ],
    "proxy": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/spacex-com").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "urls": ["https://www.spacex.com/launches/sl-10-22"],
    "proxy": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/spacex-com").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "urls": [
    "https://www.spacex.com/launches/sl-10-22"
  ],
  "proxy": {
    "useApifyProxy": true
  }
}' |
apify call abotapi/spacex-com --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/spacex-com"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/O4TkivYpmcjSZ0dFf/builds/Kg77vYwGAneYMNGsJ/openapi.json