Grants.gov Opportunities Scraper

Export public U.S. federal funding opportunities from Grants.gov to structured datasets. Receive one row per unique opportunity, with optional public descriptions, contacts, funding amounts, eligibility text and attachment metadata. Attachment files are not downloaded.

Quick start

Use a small climate search with explicit opportunity and detail caps, then open the dataset to inspect or export the rows:

{
  "keyword": "climate",
  "statuses": ["posted", "forecasted"],
  "includeDetails": true,
  "includeContacts": true,
  "includeAttachments": true,
  "maxItems": 10,
  "maxDetailRequests": 10
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to inspect its settings before running:

• Find nonprofit eligibility grants
• Watch public grant deadlines
• Monitor Commerce agency grants
• Export climate funding opportunities

What you get

One saved opportunity row with its stable ID, public notice number, title, agency and source URL. Search data can be supplemented by descriptions, funding amounts, eligibility text and requested public contacts or attachment metadata. Missing raw values and unparseable normalized dates remain unknown rather than being inferred.

Who is it for?

• Grant writers and consultants assembling source-backed opportunity shortlists for review.
• Nonprofit and university research teams checking public funding notices before evaluating fit themselves.
• Public-sector market researchers reviewing agency and program signals.
• Civic-tech and data teams connecting public opportunity records to their own reporting systems.

How you can use the data

• Prepare a climate-opportunity sheet. Use the existing posted/forecasted climate recipe with ten opportunity and detail requests. Keep opportunity IDs, agency, source links and available funding fields together, then check the current notice rather than treating a title match as grant-fit advice.
• Build a lighter Commerce research list. Use the existing DOC research recipe with details, contacts and attachment metadata off and no detail requests. Retain search-level agency and identity fields without expecting fields that require detail data.
• Review education deadlines with source context. Use the existing education recipe, retain raw and normalized date values, and open each source notice to confirm requirements. Missing or unparsable closing dates do not establish that a grant is open indefinitely.
• Compare your own repeat exports. Join stable opportunity IDs in your spreadsheet or CRM and inspect changed notice fields yourself. Scheduling, notifications, eligibility decisions and any RAG system are separate downstream work. Attachment metadata supplies references rather than downloaded or parsed files.

Input settings

Setting	JSON key	Use it for	Example
Keyword	keyword	Main Grants.gov search phrase.	climate
Additional keywords	keywords	Extra search terms.	["resilience"]
Agency filters	agencies	Narrow to agency codes/names when compatible with the source API.	["DOC"]
Statuses	statuses	Source status filter for posted, forecasted, closed or archived workflows.	["posted", "forecasted"]
Funding categories	fundingCategories	Optional source-compatible category filters.	["Environment"]
Funding instruments	fundingInstruments	Optional source-compatible funding instrument filters.	["Grant"]
Eligibilities	eligibilities	Optional source-compatible eligibility filters.	["Nonprofits"]
Date from	dateFrom	Optional date filter start, YYYY-MM-DD recommended.	2026-01-01
Date to	dateTo	Optional date filter end, YYYY-MM-DD recommended.	2026-12-31
Include details	includeDetails	Fetch descriptions, contacts, funding fields, eligibility, and attachment metadata.	true
Include contacts	includeContacts	Save public contact fields when detail data exposes them.	true
Include attachments	includeAttachments	Save public attachment metadata only.	false
Maximum opportunities	maxItems	Cap saved rows and control spend.	10
Maximum detail requests	maxDetailRequests	Limit enrichment calls.	10

Provide at least one keyword, additional keyword, agency, opportunity number or Assistance Listing filter. Status, category, eligibility or date settings alone do not satisfy that requirement. Set explicit row and detail-request caps in API calls. Form/schema values and the runtime fallback differ when a cap is omitted.

The maintained input also accepts opportunityNumbers for exact opportunity-number searches and assistanceListings for Assistance Listing/CFDA searches. Multiple selector values are searched separately and duplicate opportunity IDs are combined. Date range construction uses dateFrom, optionally paired with dateTo. A dateTo value alone does not create a date range.

Existing input recipes

Climate funding opportunities

{
  "keyword": "climate",
  "statuses": ["posted", "forecasted"],
  "includeDetails": true,
  "includeContacts": true,
  "includeAttachments": true,
  "maxItems": 10,
  "maxDetailRequests": 10
}

Agency pipeline monitor

{
  "keyword": "research",
  "agencies": ["DOC"],
  "includeDetails": false,
  "includeContacts": false,
  "includeAttachments": false,
  "maxItems": 10,
  "maxDetailRequests": 0
}

Deadline watch

{
  "keyword": "education",
  "includeDetails": true,
  "includeContacts": true,
  "includeAttachments": false,
  "maxItems": 10,
  "maxDetailRequests": 10
}

Output data

Field	Description
opportunityId	Stable Grants.gov opportunity ID used for dedupe.
opportunityNumber	Public opportunity number.
title	Opportunity title.
agencyCode, agencyName	Agency identifiers/names from search or detail data.
status, docType, category	Source status/type/category fields.
cfdaList	Assistance listing / CFDA numbers.
openDate, openDateIso, closeDate, closeDateIso	Raw and normalized dates when parseable.
fundingInstrument, fundingCategory, eligibility	Public detail classifications when available.
awardCeiling, awardFloor, estimatedTotalFunding	Funding amount fields when Grants.gov exposes them.
description	Public synopsis or forecast description.
contactName, contactEmail, contactPhone	Public opportunity contact fields when requested and available.
attachments	Public attachment metadata only. Files are not downloaded.
sourceUrl, fetchedAt, warnings	Source link, scrape timestamp, and row-level warnings.

Example output

{
  "opportunityId": "103313",
  "opportunityNumber": "NOAA-OAR-CPO-2012-2003041",
  "title": "Climate Program Office for FY 2012",
  "agencyCode": "DOC",
  "agencyName": "Department of Commerce",
  "status": "posted",
  "docType": "synopsis",
  "cfdaList": ["11.431"],
  "openDate": "07/06/2011",
  "openDateIso": "2011-07-06",
  "closeDate": "",
  "closeDateIso": null,
  "description": "Changing climate confronts society with significant economic...",
  "contactEmail": "steve.j.drescher@noaa.gov",
  "sourceUrl": "https://www.grants.gov/search-results-detail/103313",
  "fetchedAt": "2026-07-28T00:00:00.000Z",
  "warnings": []
}

Optional fields can be null or empty. Public detail lookups are bounded by the detail-request cap. A failed requested detail lookup leaves the search opportunity row intact with warnings, but the run fails so incomplete enrichment is visible. Review dates, contacts and eligibility text against the source notice before relying on them.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges item for each opportunity row saved to the dataset, including a search row retained after optional detail enrichment fails. Failed detail requests, empty searches and summary metadata do not create separate paid items. Attachment files are not downloaded, so there is no attachment-download result event.

Extraction stops when the item budget is exhausted. Keep saved-row and detail-request caps small while reviewing an export. See the live Pricing tab for current rates and discounts.

Tips for best results

• Use a real search selector before adding refinements. Supply a keyword, agency, exact opportunity number or Assistance Listing filter.
• Set both saved-row and detail caps explicitly. Turning detail requests off produces lighter search rows rather than complete detail records.
• Keep raw dates beside normalized values. Check the source when a deadline is missing or cannot be parsed.
• Review optional-detail warnings before importing a row. A useful search result can remain when its detail request fails.
• Compare stable IDs in your own monitoring workflow. Repeated runs do not automatically create alerts or assess whether an organization qualifies.

Limits and caveats

Only public Grants.gov opportunity notices are in scope. Private applications, workspace data and applicant-specific materials are not collected. The Actor does not score eligibility, recommend applying or certify funding availability. Verify requirements, dates and amounts against the source notice.

Filters are passed to the public source and depend on its supported semantics. Completed searches with no matching opportunities succeed with an empty dataset. Source errors, malformed responses and incomplete requested extraction still fail.

Detail requests are limited separately. Requested detail failures preserve useful search rows with warnings and fail the run. Search, storage or billing failures can also interrupt work after earlier rows were saved. Contacts depend on requested detail coverage, and attachment output is metadata only. No files are downloaded or parsed. Unavailable fields remain null or empty, and normalized dates are nullable.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

The Node.js and Python examples wait for completion and print the default dataset identifier. Retrieve that dataset to read the saved rows. The cURL example starts an asynchronous run: wait for it to finish before using its returned defaultDatasetId.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~grants-gov-opportunities-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keyword":"climate","includeDetails":true,"maxItems":10,"maxDetailRequests":10}'

Node.js

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("fetch_cat/grants-gov-opportunities-scraper").call({
  keyword: "climate",
  includeDetails: true,
  maxItems: 10,
  maxDetailRequests: 10
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/grants-gov-opportunities-scraper").call(run_input={
    "keyword": "climate",
    "includeDetails": True,
    "maxItems": 10,
    "maxDetailRequests": 10,
})
print(run["defaultDatasetId"])

MCP and AI agents

You can ask your AI assistant to collect data with Grants.gov Opportunities Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Grants.gov Opportunities Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/grants-gov-opportunities-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Grants.gov Opportunities Scraper by Fetch Cat, or give it the identifier fetch_cat/grants-gov-opportunities-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Grants.gov Opportunities Scraper to collect up to 5 climate opportunities with posted and forecasted statuses, details and public contacts enabled, attachment metadata off, and at most 5 detail requests. Keep source links and unknown deadlines visible without assessing eligibility.”
• “Collect up to 5 research opportunities using agency DOC with details, contacts and attachments off and zero detail requests. Show available opportunity IDs, titles and agency information for a manual shortlist.”
• “Retrieve up to 5 education opportunities with details and contacts enabled, attachment metadata off and at most 5 detail requests. Keep raw and normalized dates with source links for my own deadline review, without treating missing dates as open-ended funding.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export results?

Yes. Apify datasets support JSON, CSV, Excel, XML, RSS, and API access.

Does this scrape private grant applications?

No. It only exports public Grants.gov opportunity notice data.

Why are some fields empty?

Grants.gov does not expose every field for every opportunity. The Actor preserves raw values where available and leaves unavailable fields empty instead of guessing.

Related Actors

• Google Maps Places Scraper — Collect public place and business listings for organization and location research.
• Bing Search Results Scraper — Collect ranked public web results, titles and snippets for supporting funding or organization research.
• GLEIF LEI Records Scraper — Collect public legal-entity reference records for organizations that have an LEI. This does not establish grant eligibility.
• Website Content Crawler Lite — Collect text and links from public program or organization pages for funding-research context.
• Website Contact Finder — Collect contact details published on known organization websites for separate contact research.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥