California eProcure Contracts Scraper

Scrape active bid events from the California eProcurement Portal (caleprocure.ca.gov). Returns structured data for each bid event: event ID, name, issuing department, bid type, dates, status, and optional detail fields (event type, format, category, location, contact information, and description).

---

What this actor does

The actor loads the California eProcure bid search page and retrieves all active procurement events posted by California state agencies. It:

1. Navigates to the search page and triggers a full search via the InFlight NLX/PeopleSoft interface
2. Extracts listing data for each bid event: event ID, event name, department, start date, end date, status, and detail URL
3. Follows each event's detail page to collect additional fields: event type (IFB/RFP/RFQ), format, description, category, location, and contact information
4. Respects the maxItems limit — stops collecting new events once the cap is reached

---

Input

Field	Type	Default	Description
maxItems	integer	10	Required. Maximum number of bid events to collect

Example input:

{
  "maxItems": 25
}

---

Output

Each output record contains the following fields:

Field	Description
event_id	Unique bid event identifier (e.g. 0000024860)
event_name	Name / title of the bid event
department	Issuing California state department or agency
event_type	Bid type: IFB, RFP, RFQ, etc.
format	Bid format: Standard, Online, etc.
start_date	Date the bid opened / was published
end_date	Bid response due date
status	Current status (Active, Awarded, Cancelled, etc.)
category	UNSPSC commodity category
location	Delivery / project location
contact_name	Procurement contact name
contact_email	Procurement contact email
description	Full event description
detail_url	URL to the bid event detail page
scrapedAt	ISO 8601 timestamp of when the record was scraped

---

Notes

• The portal returns active bid events by default. Closed or awarded bids may not appear.
• The actor uses Playwright (Chromium) to interact with the PeopleSoft-based portal, which requires JavaScript to render search results.
• No proxy or captcha-solving is required — the site uses TLS fingerprinting that Chromium clears automatically.
• The actor runs with 1 concurrent page to respect portal load limits.
• Requires at least 512 MB memory; 1024 MB recommended.