# Doorkeeper Events (`stone_jadex/doorkeeper-events`) Actor

- **URL**: https://apify.com/stone_jadex/doorkeeper-events.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 event items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Doorkeeper Events

Build a public Doorkeeper event calendar for community editors, event researchers and partnership teams. Collect events from the main or recently published event list, then optionally add venue and attendance details.

### What you gain

- Bring event titles, communities, date text and venues together for calendar curation.
- Add start/end timestamps, address, capacity and participant count when the public detail provides them.
- Use the community and event links to check the original announcement before publishing.
- Include optional descriptions with email addresses masked.

### Ways to use the data

- A newsletter editor can assemble a weekly list of community meetups with dates and venues.
- A sponsorship researcher can compare communities and published event capacity before reviewing partnership opportunities.

### Delivery preview

These fictional rows are **illustrative**, not captured results. Fields may be missing in actual records.

| Event | Community | Date / time | Venue | Capacity |
|---|---|---|---|---|
| Example meetup | Example Developers | 10 Nov 2026, 09:00 +09:00 | Example Hall | 80 |
| Data workshop | Example Data Group | 12 Nov 2026, 18:00 +09:00 | Online | — |
| Design evening | Example Designers | 15 Nov 2026, 19:00 +09:00 | Community Room | 40 |

### Why choose this Actor

- Choose lightweight list records or add event details; descriptions require detail fetching.
- The event URL identifies the public announcement, while community, capacity and participant counts offer context for calendar and sponsorship research.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| Event | $1.5 per 1,000 results |

For example, 1,000 results at the event rate incur $1.5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Use the default events list or a supported main or recently published Doorkeeper list URL.
2. Set `maxItems`; enable `fetchDetails` for event details and optionally `includeDescription` for masked descriptions.
3. Run the Actor, review the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** Only the main events and recently published event-list URLs are supported. Detail failures can leave incomplete records; no attendee names are collected.

**Is this a live feed or an alert service?** Each run captures data available at that time. Repeated collection and any comparison, alerting or decisions require your own workflow.

**Will every field be populated?** No. The source may omit values, change a page or restrict access; check the original record before relying on it. A configured maximum does not guarantee that many results.

# Actor input Schema

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

Doorkeeper event list URL: https://www.doorkeeper.jp/events or https://www.doorkeeper.jp/events/recently_published. Pagination is followed automatically.

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

Maximum number of events to collect, from 1 to 10000.

## `fetchDetails` (type: `boolean`):

Add public event times, full address, capacity and participant count from the event API. Description fetching or API failures also fetch community HTML for tickets/prices, images and other available fields.

## `includeDescription` (type: `boolean`):

Include plain-text event descriptions with email addresses masked. Requires fetchDetails to be enabled.

## `useProxy` (type: `boolean`):

Send requests through the Apify datacenter proxy.

## Actor input object example

```json
{
  "startUrl": "https://www.doorkeeper.jp/events",
  "maxItems": 50,
  "fetchDetails": false,
  "includeDescription": false,
  "useProxy": false
}
```

# Actor output Schema

## `results` (type: `string`):

Public Doorkeeper events saved in the default dataset. Optional details depend on the input and source availability.

## `summary` (type: `string`):

Saved event count, request and error statistics, timings, and the reason the crawl stopped.

# 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("stone_jadex/doorkeeper-events").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("stone_jadex/doorkeeper-events").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 stone_jadex/doorkeeper-events --silent --output-dataset

```

## MCP server setup

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

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/zzXrNVn870DZr9COH/builds/HZ9zfBAfBNgN77H8b/openapi.json