# Equestrian Show Calendar (`gallopdataagency/equestrian-show-calendar`) Actor

- **URL**: https://apify.com/gallopdataagency/equestrian-show-calendar.md
- **Developed by:** [GallopDataAgency](https://apify.com/gallopdataagency) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$30.00 / show calendar export

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

## Equestrian Show Calendar

Export a calendar of **recent and upcoming equestrian shows** as structured data — show jumping, dressage, eventing, endurance, working equitation and more. Each run returns the shows of roughly the past and the next 30 days, with dates, disciplines, country, level and organizer IDs.

No input, no setup: start the Actor and download the calendar as JSON, CSV or Excel, or fetch it via the Apify API.

### What you get

One dataset item per show:

| Field | Description |
|---|---|
| `id` | Unique ID of the show |
| `name`, `display_name` | Name of the show |
| `start_on`, `end_on` | First and last day of the show (`YYYY-MM-DD`) |
| `discipline` | Main discipline, e.g. `show_jumping`, `dressage`, `eventing`, `multi` |
| `disciplines` | All disciplines held at the show |
| `statuses` | Level of the show, e.g. `international`, `national`, `elite` |
| `horse_ponies` | Whether the show is for horses, ponies or both |
| `venue_country` | Country of the venue (IOC code, e.g. `SWE`, `GER`, `GBR`) |
| `team` | `true` if the show includes team competitions |
| `organizer_id` | ID of the organizer |
| `created_at`, `updated_at` | When the show was created and last updated |
| `scrapedAt` | Timestamp of the run (ISO 8601) |

Some shows carry additional IDs and logo references. Fields that don't apply to a show are left out.

Example:

```json
{
  "id": 82158,
  "display_name": "AELEC Tamworth World Cup Show 2026",
  "name": "AELEC Tamworth World Cup Show 2026",
  "start_on": "2026-10-08",
  "end_on": "2026-10-11",
  "discipline": "show_jumping",
  "disciplines": ["show_jumping", "score_summary"],
  "statuses": ["international", "elite"],
  "horse_ponies": ["horse"],
  "venue_country": "AUS",
  "organizer_id": 4438,
  "created_at": "2026-08-29T10:01:51+02:00",
  "updated_at": "2026-09-29T23:40:02+02:00",
  "scrapedAt": "2026-10-01T12:00:00.000Z"
}
```

### Pricing

You pay a fixed price per successful run, no matter how many shows it returns. Failed runs are not charged.

### Good to know

- **Run it daily** to catch newly added shows and updated dates. Use an Apify schedule to automate this.
- **A run only succeeds if the calendar was loaded.** An empty or broken response marks the run as failed.

### Use cases

- Show calendars on websites and apps for riders, trainers and fans
- Event planning for horse transport, vets, farriers and suppliers
- Lead lists of organizers for sponsors and service providers
- Market overviews by discipline, level and country

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

## `shows` (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("gallopdataagency/equestrian-show-calendar").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("gallopdataagency/equestrian-show-calendar").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 gallopdataagency/equestrian-show-calendar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gallopdataagency/equestrian-show-calendar"
        }
    }
}
```

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/h1dgLiWiXJNUNVeYJ/builds/zDAxaBxGPS0DdVe1z/openapi.json