# Bonfire / Euna Procurement - Open Opportunities (`j0401/bonfire-procurement`) Actor

Open procurement opportunities across 80+ public-sector and institutional procurement portals running Bonfire / Euna. Public RSS feeds, no login: reference number, title, department, description, posting and closing dates, and the official notice link. Filter by portal, keyword or closing date.

- **URL**: https://apify.com/j0401/bonfire-procurement.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.03 / 1,000 bonfire opportunity records

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

## Bonfire / Euna Procurement - Open Opportunities

Open procurement opportunities from **80+ public-sector and institutional procurement portals**
running Bonfire / Euna (formerly Bonfire). The platform publishes each
portal's opportunities as a public RSS feed, no login and no key: this actor
scans them in one pass and returns the **currently open** opportunities -
reference number, title, department, description, posting date, closing date
and the official notice link.

Some portals aggregate many agencies. `utah` carries the Utah state
procurement place, `pennbid` the Pennsylvania co-op, and county, city, school
district and transit portals sit alongside them.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the
records you actually receive.

### Search it

- **Portal** - `org="utah"`, `"pennbid"`, `"u-46"`.
  `mode=orgs` lists every supported portal with its live count.
- **Keyword** - `keyword="construction"` (substring over title and
  description, case-insensitive).
- **Department** - `department="Purchasing"` (where the feed carries one).
- **Dates** - `postedFrom` / `postedTo` and `closingFrom` / `closingTo`.
- **Still open** - `openOnly=true` keeps opportunities whose parsed closing
  date is today or later.

### Example inputs

**Open construction opportunities, statewide portals included**

```json
{ "keyword": "construction", "openOnly": true, "maxResults": 25 }
```

**One portal** - the Utah procurement place (state + local agencies)

```json
{ "org": "utah", "maxResults": 25 }
```

**Closing in a date window**

```json
{ "closingFrom": "2026-10-18", "closingTo": "2026-11-30", "maxResults": 50 }
```

**Where the opportunities are** - `mode=aggregate`

```json
{ "mode": "aggregate", "groupBy": "org" }
```

**List the supported portals and their live counts**

```json
{ "mode": "orgs" }
```

### Example output

**One opportunity** - `mode=search`:

```json
{
 "org": "actransit",
 "reference": "2027-1697",
 "title": "Tire Mileage and Leasing Program",
 "department": "",
 "description": "AC Transit is seeking proposals from qualified vendors to provide a Tire Mileage and Leasing Program primarily consisting of leasing radial tires and providing comprehensive tire maintenance services for the District fleet of buses. Project closes Nov 05, 2026 2:00 PM PST.",
 "postedDate": "2026-10-15",
 "closeDate": "2026-11-05",
 "link": "https://actransit.bonfirehub.com/opportunities/247475",
 "sourceUrl": "https://actransit.bonfirehub.com/opportunities/rss",
 "refreshedDate": "2026-10-18",
 "mode": "search"
}
```

### Or roll it up

`mode=monitor` returns only opportunities **posted after your last run**, and advances a per-user watermark in the actor's key-value store. The feed carries open opportunities only, so monitor is a new-posting alert, not a history. Owner runs do not advance the watermark unless `sinceLastRun=true`.

```json
{ "mode": "monitor", "maxResults": 100 }
```

`mode=aggregate` returns one count row per group - **portal**, **posting
month** or **department**. The default (empty) run returns the live count by
portal.

### Notes on the data, from the source

- **Open opportunities only.** The RSS feed lists what each portal is
  currently advertising; it is a monitoring surface, not a historical
  archive. A small share of rows (measured 2026-10-24: 23 of 821) still carry
  a closing date already in the past - the portal has not removed them. Use
  `openOnly=true` to drop those.
- **One row = one opportunity.** The `link` opens the official notice on the
  agency's own portal, where documents and submission details live.
- **Closing dates are parsed from the feed text.** Where the feed states a
  closing date, it is normalized to `YYYY-MM-DD`; where it does not, the
  field is blank and `openOnly=true` will exclude that row.
- **Supported portals, not an exhaustive directory.** Bonfire/Euna publishes
  no public customer directory; the included list was assembled from public
  indexes and verified live. Portals that are not included can be added.
- **A portal that is temporarily unreachable is omitted from that run.** The
  run still succeeds as long as the register as a whole looks healthy; a run
  where more than a quarter of the portals fail stops with an error instead of
  returning a silently incomplete list.
- The example output above is trimmed to the record fields; aggregate rows
  additionally carry `groupKey` / `groupCount` / `groupBy` / `totalMatched`.

# Actor input Schema

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

search = filter open opportunities. aggregate = one row per group. orgs = the supported portals and their live counts. monitor = only opportunities posted after your last run (per-user watermark). Leave blank to auto-route: filters -> search, no filters -> aggregate.

## `org` (type: `string`):

Bonfire subdomain, e.g. "utah", "pennbid", "u-46". Run mode=orgs for the supported list.

## `keyword` (type: `string`):

Substring over the opportunity title and description, case-insensitive (e.g. "construction", "software", "janitorial").

## `department` (type: `string`):

Department / issuing-office substring, case-insensitive (e.g. "Purchasing", "Public Works").

## `postedFrom` (type: `string`):

Earliest posting date (YYYY-MM-DD), inclusive.

## `postedTo` (type: `string`):

Latest posting date (YYYY-MM-DD), inclusive.

## `closingFrom` (type: `string`):

Earliest closing date (YYYY-MM-DD), inclusive.

## `closingTo` (type: `string`):

Latest closing date (YYYY-MM-DD), inclusive.

## `openOnly` (type: `boolean`):

When on, keeps opportunities whose parsed closing date is today or later. Rows with no parsed closing date are excluded.

## `aggregate` (type: `boolean`):

When on, returns one summary record per group with count.

## `groupBy` (type: `string`):

org -> opportunities per portal; postedMonth -> posting volume by month; department -> issuing-department mix (where the feed carries one).

## `maxResults` (type: `integer`):

Cap the number of search records pushed (0 = the default ceiling of 100, maximum 2000). Aggregate returns every group; mode=orgs caps the portal list.

## `sinceLastRun` (type: `boolean`):

Owner runs only: read and advance the monitor watermark. User runs in monitor mode always do.

## Actor input object example

```json
{
  "openOnly": false,
  "aggregate": false,
  "groupBy": "org",
  "maxResults": 100,
  "sinceLastRun": false
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

Open procurement opportunities or aggregate rows - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("j0401/bonfire-procurement").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("j0401/bonfire-procurement").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 '{}' |
apify call j0401/bonfire-procurement --silent --output-dataset

```

## MCP server setup

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

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/UuAlybA0Kl0xk667X/builds/fWWXooqaOYJSCmaN8/openapi.json