# NASA Technical Reports Scraper (`parseforge/nasa-reports-scraper`) Actor

Scrapes NASA NTRS for technical reports by search query, author, center, or document type. Returns each report's title, abstract, date, and download link as a flat row.

- **URL**: https://apify.com/parseforge/nasa-reports-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Education, Automation, News
- **Features:** Limited permissions
- **Stats:** 10 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner-v4.webp)](https://apify.com/parseforge?fpr=vmoqkp)

### NASA Technical Reports Scraper

**Scrape NASA technical reports by keyword, author, center, or document type, up to a million per run.** Each report returns with its title, abstract, publication date, and download links. No API key required. Export to CSV, JSON, Excel, or XML.

NASA's public technical reports server holds decades of aerospace research, but its web interface is built for manual browsing, not bulk retrieval. This Actor queries the NTRS API directly, letting you filter by author, organization, date range, or subject category and collect the matching records in one structured dataset.

| Who uses it | What they scrape NASA Technical Reports Server for |
|---|---|
| Aerospace engineers | Gathering all technical memoranda from a specific NASA center for a literature review. |
| Academic researchers | Building a corpus of conference papers on a narrow topic like aerodynamics or astrophysics. |
| Data analysts | Tracking publication trends across NASA centers over a multi-year period. |
| Science journalists | Finding the latest technical publications on a breaking space mission. |

### What it does

This Actor collects NASA technical report metadata by search query or API filters and returns each report as a flat row.

- **Keyword and title search:** Find reports by any term, from mission names to technical jargon.
- **Date range filters:** Narrow results by publication date or the date NASA acquired the document.
- **Center and organization filters:** Limit results to a single NASA center like JPL or Langley.
- **Document type selection:** Target only Technical Memoranda, Conference Papers, Contractor Reports, and more.
- **Author and report number lookup:** Retrieve all work by a specific researcher or a single known report.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with NASA Technical Reports Server data

**Build a research bibliography.**

A graduate student enters a subject category and date range to export every relevant NASA report into a reference manager.

**Audit a center's output.**

An R\&D analyst filters by the Glenn Research Center and the last five years to chart its publication volume by document type.

**Find a specific technical specification.**

An engineer searches by report number to locate a single NASA Technical Memorandum and its linked PDF.

**Track emerging research areas.**

A market researcher runs a keyword search for a new propulsion technology every month to spot new conference papers and patents.

### Why choose this scraper

|  | What you get |
|---|---|
| **No API registration** | Query the NASA NTRS API without signing up for a key or managing rate limits. |
| **Full metadata** | Get the title, abstract, author list, publication date, document type, and download URL for every report. |
| **Bulk export** | Save up to a million records to CSV, JSON, Excel, or XML for offline analysis. |
| **Precise filtering** | Combine search terms with center, document type, and date range to zero in on the exact research you need. |

### How it compares

No other Store actor targets NASA Technical Reports Server the same way, so the honest comparison is with the alternatives teams actually weigh.

| | NASA Technical Reports Scraper | Build it in-house | By hand |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When NASA Technical Reports Server changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |

### Configure the run

Drive the Actor with a search query, author name, or a combination of filters like center, document type, and date range, and filtering happens as each report is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

```json
{
  "maxItems": 10
}
```

A larger pull:

```json
{
  "maxItems": 200
}
```

### Pricing

Pay-per-result: **$0.006 per result** collected. You pay only for the results written to your dataset.

| Results collected | Approximate cost |
|---|---|
| 100 results | $0.60 |
| 1,000 results | $6.00 |
| 10,000 results | $60.00 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [NASA Technical Reports Scraper](https://apify.com/parseforge/nasa-reports-scraper?fpr=vmoqkp).
3. Set your inputs and any filters, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to NASA Technical Reports Server through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/nasa-reports-scraper"
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**I am getting no results.**

Check that your filters are not too restrictive. Try running with only a broad searchQuery first, then add filters one by one. Also confirm you are not mixing a startUrl with API filters.

**The date filter is not working.**

Date filters only apply when you use the search filter inputs. They are ignored if you provide a startUrl. Use the YYYY-MM-DD format.

**My run stopped before reaching maxItems.**

The Actor stops when it has read all available results matching your query. If the total matches are fewer than your maxItems setting, the run ends early.

**The download link does not open a PDF.**

Some records point to abstract pages or external publisher sites rather than direct PDFs. The link returned is the one NASA provides in the metadata.

**I entered a startUrl but the run failed.**

Direct URL scraping is not fully supported because NTRS uses a POST-based API. Remove the startUrl and use the search filters instead for a stable run.

### FAQ

| Question | Answer |
|---|---|
| Can I scrape a list of NASA report URLs I already have? | The Actor is designed for search-based collection using the NTRS API. Direct URL scraping is not fully supported because the server uses POST requests. Use the search filters for the most reliable results. |
| How do I download the full-text PDF of a report? | Each result row includes a download URL. You can pass that list of URLs to a generic file downloader Actor on Apify to fetch the PDFs in bulk. |
| What is the difference between publication date and date acquired? | Publication date is when the report was officially issued. Date acquired is when NASA added the record to the NTRS database. Use the one that fits your research timeline. |
| Can I search by NASA center? | Yes. The Center filter lets you pick from all major locations, including JPL, Goddard, Johnson, and Ames. |
| Is there a limit on how many reports I can get? | You set the maximum in the input, up to one million reports per run. The actual number returned depends on how many match your filters. |
| What document types are available? | You can filter by Technical Publications, Conference Papers, Contractor Reports, Technical Memoranda, Patents, Presentations, and several others. |
| Can I search for a specific author? | Yes. Use the Author filter with the format 'Smith, John' to find all reports by that person. |
| Does this Actor require a NASA API key? | No. It queries the public NTRS search endpoint and does not need any authentication. |
| Can I combine multiple filters in one run? | Yes. You can mix a search query with a center, a document type, and a date range to create a highly targeted collection. |
| What output formats are supported? | You can export your dataset in CSV, JSON, Excel, or XML from the Apify platform. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by NASA. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

## `startUrl` (type: `string`):

Direct URL to scrape (not fully supported - NASA NTRS uses POST API). Use API filters instead for better results.

## `maxItems` (type: `integer`):

How many reports to collect per run.

## `searchQuery` (type: `string`):

General search query to find reports. Use this OR startUrl above, not both.

## `title` (type: `string`):

Filter by report title

## `author` (type: `string`):

Filter by author name (e.g., 'Smith, John')

## `organization` (type: `string`):

Filter by organization (e.g., 'NASA Ames Research Center')

## `publicationDateFrom` (type: `string`):

Start date for publication date range (YYYY-MM-DD format). Only works when using search filters (not with startUrl).

## `publicationDateTo` (type: `string`):

End date for publication date range (YYYY-MM-DD format). Only works when using search filters (not with startUrl).

## `dateAcquiredFrom` (type: `string`):

Start date for date acquired range (YYYY-MM-DD format). Only works when using search filters (not with startUrl).

## `dateAcquiredTo` (type: `string`):

End date for date acquired range (YYYY-MM-DD format). Only works when using search filters (not with startUrl).

## `documentType` (type: `string`):

Filter by document type. Only works when using search filters (not with startUrl).

## `center` (type: `string`):

Filter by NASA center. Only works when using search filters (not with startUrl).

## `subjectCategory` (type: `string`):

Filter by subject category (e.g., 'Astrophysics', 'Aerodynamics')

## `reportNumbers` (type: `string`):

Filter by report number (e.g., 'NASA-TM-2023-123456')

## `fundingNumbers` (type: `string`):

Filter by funding number (e.g., 'NNX07AD99G')

## `keywords` (type: `string`):

Filter by keywords (comma-separated)

## `sort` (type: `string`):

Sort order for search results. Only works when using search filters (not with startUrl).

## Actor input object example

```json
{
  "maxItems": 10,
  "sort": "Best Match"
}
```

# Actor output Schema

## `citations` (type: `string`):

Complete dataset with all scraped NASA technical report citations including full details

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

Overview view of citations with key fields displayed in a table format

# 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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/nasa-reports-scraper").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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parseforge/nasa-reports-scraper").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 '{
  "maxItems": 10
}' |
apify call parseforge/nasa-reports-scraper --silent --output-dataset

```

## MCP server setup

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

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/xTqdIFw80nqyWepTN/builds/Vlgh6p9upBpJQ6VgF/openapi.json