Tech Events Calendar API | Conferences + CFP

Aggregate tech conferences and CFPs across multiple sources into a deduplicated event calendar for DevRel and recruiting workflows.

Store Quickstart

• Start with store-input.example.json for a cheap single-topic first run.
• If that matches your workflow, switch to store-input.templates.json and pick one of:
• Quickstart (Dataset) for one-topic discovery
• Multi-topic Scan for a broader calendar build
• Webhook Alert for downstream event routing

Key Features

• 📅 Multi-topic search — Search across JavaScript, Python, AI, DevOps, and 20+ topics
• 🔄 Automatic deduplication — Events appearing in multiple topics are merged
• 🌍 Global coverage — Conferences from all countries, including online events
• 📝 CFP tracking — Call-for-papers URLs and deadlines included
• 📊 Sorted by date — Clean chronological listing
• 🏷️ Topic tagging — Each event tagged with all relevant topics

Use Cases

Who	Why
Developer advocates	Find conferences to speak at or sponsor
DevRel teams	Plan conference attendance calendar
Recruiters	Discover events where target developers gather
Community managers	Track events in their technology ecosystem

Input

Field	Type	Default	Description
topics	array	prefilled	Topics to search for (e.g. ['javascript','ai','devops']).
year	integer	2026	Year to search for events.
delivery	string	"dataset"	How to deliver results. 'dataset' saves to Apify Dataset (recommended), 'webhook' sends to a URL.
webhookUrl	string	—	Webhook URL to send results to (only used when delivery is 'webhook'). Works with Slack, Discord, or any HTTP endpoint.
dryRun	boolean	false	If true, runs without saving results or sending webhooks. Useful for testing.

Input Example

{
  "topics": ["javascript", "python", "ai"],
  "year": 2026
}

Output

Field	Type	Description
meta	object
results	array
results[].name	string
results[].url	string (url)
results[].startDate	string
results[].endDate	string
results[].city	string
results[].country	string
results[].online	boolean
results[].cfpUrl	string (url)
results[].cfpEndDate	string
results[].twitter	string
results[].topics	array
results[].source	string

Output Example

{
  "name": "PyCon US 2026",
  "url": "https://us.pycon.org/2026/",
  "startDate": "2026-05-15",
  "endDate": "2026-05-23",
  "city": "Long Beach",
  "country": "US",
  "online": false,
  "cfpUrl": "https://us.pycon.org/2026/speaking/",
  "cfpEndDate": "2025-12-18",
  "topics": ["python"],
  "source": "confs.tech"
}

API Usage

Run this actor programmatically using the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Settings → Integrations.

cURL

curl -X POST "https://api.apify.com/v2/acts/taroyamada~tech-events-intelligence/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "topics": ["javascript", "python", "ai"], "year": 2026 }'

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("taroyamada/tech-events-intelligence").call(run_input={
  "topics": ["javascript", "python", "ai"],
  "year": 2026
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('taroyamada/tech-events-intelligence').call({
  "topics": ["javascript", "python", "ai"],
  "year": 2026
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Tips & Limitations

• Run nightly as part of your supply-chain monitoring to catch new vulnerabilities early.
• Pair with oss-vulnerability-monitor for CVE coverage layered on top of version tracking.
• For monorepos, run per-package rather than recursing — easier to triage alerts by team owner.
• Use snapshotKey to persist between runs and only alert on diffs.
• Webhook delivery supports JSON payloads — pipe into your existing on-call routing.

FAQ

Is my build slowed down?

This actor runs on Apify infrastructure, not your CI runners. No impact on build times.

What's the freshness of data?

Depends on the source registry — typically 5–60 minutes behind upstream.

Can I filter by package ecosystem?

Yes — most DevOps actors accept an ecosystem or package-manager filter in their input schema.

Does this work with private registries?

No — this actor targets public registries (npm, PyPI, crates.io, etc.). Private registries require credential handling that's out of scope.

Can I integrate with GitHub Actions?

Yes — call this actor via Apify API inside a workflow job, parse the JSON output, and fail the build on threshold violations.

Related Actors

DevOps & Tech Intel cluster — explore related Apify tools:

• 🌐 DNS Propagation Checker — Check DNS propagation across 8 global resolvers (Google, Cloudflare, Quad9, OpenDNS).
• 🔍 Subdomain Finder — Discover subdomains for any domain using Certificate Transparency logs (crt.
• 🧹 CSV Data Cleaner — Clean CSV data: trim whitespace, remove empty rows, deduplicate by columns, sort.
• 📦 NPM Package Analyzer — Analyze npm packages: download stats, dependencies, licenses, deprecation status.
• 💬 Reddit Scraper — Scrape Reddit posts and comments from any subreddit via official JSON API.
• GitHub Release & Changelog Monitor API — Track GitHub releases, tags, release notes, and changelog drift over time with one summary-first repository row per repo.
• Docs & Changelog Drift Monitor API — Monitor release notes, changelog pages, migration guides, and key docs pages with one summary-first target row per monitored repo, SDK, or product.
• 🔒 OSS Vulnerability Monitor — Monitor open-source packages for known security vulnerabilities using OSV and GitHub Security Advisories.

Cost

Pay Per Event:

• actor-start: $0.01 (flat fee per run)
• dataset-item: $0.003 per output item

Example: 1,000 items = $0.01 + (1,000 × $0.003) = $3.01

No subscription required — you only pay for what you use.