California New Grant Opportunity Watch avatar

California New Grant Opportunity Watch

Pricing

from $67.00 / 1,000 new-opportunity deltas

Go to Apify Store
California New Grant Opportunity Watch

California New Grant Opportunity Watch

New grant opportunities as the California Grants Portal publishes them - the portal's own id, the funding agency, who may apply, the deadline exactly as stated, and a link to the listing.

Pricing

from $67.00 / 1,000 new-opportunity deltas

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

🎓 California New Grant Opportunity Watch

New grant opportunities as the California Grants Portal publishes them - the portal's own id, the funding agency, who may apply, the deadline exactly as stated, and a link to the listing.

Output is one ca_grant_record row per result; billing is pay-per-event, the value event being one new-opportunity delta (a $0.02 start fee per run, then $0.10 per new-opportunity delta plus one $0.10 source check per run that reads the source). Source: data.ca.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

California New Grant Opportunity Watch sample output — a table of real new-opportunity delta rows (title, agency_dept, applicant_type, categories) from run yPN6SMpBBmQyB6ZSp on build 0.1.12

Real rows from run yPN6SMpBBmQyB6ZSp on build 0.1.12 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

titleagency_deptapplicant_typecategoriesopen_dateapplication_deadline
Scaling Dyadic Care Grant ProgramDepartment of Health Care ServicesBusiness; Nonprofit; Other Legal Entity; Public Agency; Tribal GovernmDisadvantaged Communities; Education; Health & Human Services; Housing2026-09-16 19:01:002026-10-26 17:00:00
Division of Boating and Waterways 2026 Boating Infrastructure GrantDepartment of Parks and RecreationBusiness; Nonprofit; Other Legal Entity; Public Agency; Tribal GovernmEnvironment & Water; Parks & Recreation2026-09-15 20:00:002026-09-29 10:00:00
LA County TECH (CEA-LAT) Grant – Round 3Public Utilities CommissionNonprofitEducation; Energy2026-09-15 15:00:002026-10-15 11:59:00
Illegal Disposal Site Abatement Grant ProgramDepartment of Resources Recycling and RecoveryPublic AgencyDisadvantaged Communities; Environment & Water; Health & Human Service2026-09-09 17:07:002026-10-16 23:59:00
Recycled Glass Processing Incentive Grant Program (FY 2026-27)Department of Resources Recycling and RecoveryBusiness; NonprofitEnvironment & Water2026-09-08 18:59:002026-10-22 11:59:00
Forest Legacy Program Capacity and Project Development 2026Department of Forestry and Fire ProtectionNonprofit; Other Legal EntityEnvironment & Water2026-09-08 17:30:002026-09-30 23:59:00
Farmworkers Advancement Program (FAP) Grant for Program Year 2026-27 (Employment Development DepartmentNonprofit; Public Agency; Tribal GovernmentAgriculture; Disadvantaged Communities; Employment, Labor & Training2026-09-03 22:00:002026-10-12 23:59:00
Lunch at the Library Summer 2027CA State LibraryNonprofit; Public AgencyDisadvantaged Communities; Food & Nutrition; Libraries and Arts2026-09-01 14:54:00Ongoing

The run finished with the status message: NORMAL: emitted 10 item(s)

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_key (string/null) — e.g. ca-grant:191499
  • portal_id — e.g. 191499
  • grant_id — e.g. SWC 108
  • title — e.g. Scaling Dyadic Care Grant Program
  • agency_dept — e.g. Department of Health Care Services
  • status — e.g. active
  • applicant_type — e.g. Business; Nonprofit; Other Legal Entity; Public Agency; Tribal Government
  • categories — e.g. Disadvantaged Communities; Education; Health & Human Services; Housing, Communit
  • open_date — e.g. 2026-09-16 19:01:00
  • application_deadline — e.g. 2026-10-26 17:00:00
  • application_deadline_iso — e.g. 2026-10-26
  • deadline_is_a_date — e.g. True
  • est_available_funds — e.g. $17,000,000
  • last_updated — e.g. 2026-09-16 22:44:12
  • change_notes — e.g. Updated grant data.
  • grant_url — e.g. https://www.dhcs.ca.gov/providers-partners/dyadic-services-as-a-medi-cal-benefit
  • portal_url — e.g. https://www.grants.ca.gov/grants/191499/
  • record_type (string) — e.g. ca_grant_record
  • delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"statuses": [
"active"
],
"applicant_types": [],
"max_items": 10,
"watch_mode": false,
"baseline_id": "default"
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.10 ca-grant-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
"statuses": [
"active"
],
"applicant_types": [],
"max_items": 5,
"watch_mode": false,
"baseline_id": "default"
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
"statuses": [
"active"
],
"applicant_types": [],
"max_items": 10,
"watch_mode": true,
"baseline_id": "default"
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.10 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run yPN6SMpBBmQyB6ZSp, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_key": "ca-grant:191499",
"portal_id": "191499",
"grant_id": null,
"title": "Scaling Dyadic Care Grant Program",
"agency_dept": "Department of Health Care Services",
"status": "active",
"applicant_type": "Business; Nonprofit; Other Legal Entity; Public Agency; Tribal Government",
"categories": "Disadvantaged Communities; Education; Health & Human Services; Housing, Community and Economic Development",
"open_date": "2026-09-16 19:01:00",
"application_deadline": "2026-10-26 17:00:00",
"application_deadline_iso": "2026-10-26",
"deadline_is_a_date": true,
"est_available_funds": "$17,000,000",
"last_updated": "2026-09-16 22:44:12",
"change_notes": null,
"grant_url": "https://www.dhcs.ca.gov/providers-partners/dyadic-services-as-a-medi-cal-benefit/",
"portal_url": "https://www.grants.ca.gov/grants/191499/",
"record_type": "ca_grant_record",
"schema_version": "1.0",
"output_mode": "preview",
"preview_cap": 25,
"preview_truncated": 0
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each new-opportunity delta is charged at the moment it is pushed (ca-grant-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

California Grants Portal, published as a daily CSV on data.ca.gov (public, logged-out)

  • https://data.ca.gov/dataset/california-grants-portal

Measured 2026-07-28: 1,973 rows, 36 columns, resource last updated 2026-07-27 08:01. PortalID is the source-native key and is unique — 1,973 distinct of 1,973. The whole file is read every run, so a listing that disappears really has gone; there is no sliding window.

The deadline is not always a date

ApplicationDeadline carries three shapes, measured on the live file:

shaperows
a timestamp, 2026-09-01 23:59:001,845
the literal string Ongoing127 — every one an active grant
empty1

So the deadline is signed as the source's own string, and a separate application_deadline_iso field is populated only when the source actually gave a date — null for Ongoing. A grant moving from Ongoing to a real date therefore reports as acquiring a deadline, not as a date change and not as a parse failure.

The small-business slice is a filter, not another Actor

applicant_types: ["Business"] — 477 of 1,973 rows on 2026-07-28. The source lists several types per row separated by ;, so matching is substring and case-insensitive. Other tokens: Public Agency 1,557, Nonprofit 1,309, Tribal Government 959, Individual 375, Other Legal Entity 146.

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code, labelled output_mode: "preview". This Actor sells change detection, not bulk export.

Watch semantics

The first watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED keyed on PortalID, with before / after and changed_fields. Billed deltas are capped at 500 per run; the overflow is a named PARTIAL withholding, never billed, and re-detected on the next run.

One delta type per Actor

This Actor emits new-opportunity and nothing else. Its sibling reads the same file for the other slice, each with its own baseline and its own price.

Terminal states

NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

A file that arrives and does not parse BLOCKS. It is never reported as an empty source. The portal serves this CSV with a UTF-8 byte-order mark; on build 0.1.2 that made every PortalID lookup miss, so a 6,401,507-byte read parsed to zero rows and the run announced GENUINE_EMPTY about a file holding 1,973 live grants. Since 0.1.3 the mark is stripped, the key column is checked by name, and a large body that yields no rows fails the run loudly naming what arrived. An outage you can see beats an emptiness you cannot.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → SchedulesCreate new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

  • Daily0 7 * * * (07:00 UTC): catch changes within a day.
  • Weekly0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Source check (source-check)$0.10$0.09$0.08$0.07
New-opportunity delta (ca-grant-delta)$0.10$0.09$0.08$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

  • 8 new-opportunity deltas: $0.02 start + $0.10 source check + 8 × $0.10 = $0.92
  • 25 new-opportunity deltas: $0.02 start + $0.10 source check + 25 × $0.10 = $2.62
  • 5000 new-opportunity deltas: $0.02 start + $0.10 source check + 5000 × $0.10 = $500.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: emitted 10 item(s). max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

This actor reads public, logged-out pages and feeds published by data.ca.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.ca.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 5000); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other grant and research-funding watches actors?
A: Same output shape and billing model; this one covers data.ca.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (max_items) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.