Claude Code transcript - page 1/4

[
  {
    "type": "tool_reference",
    "tool_name": "WebFetch"
  }
]

# Edinburgh Festivals Venues API Details

## Base URL
`https://api.edinburghfestivalcity.com/venues`

## Authentication
The documentation page does not specify an authentication scheme for the venues endpoint.

## Request Parameters

**Festival Selection:**
- `festival`: Festival ID (fringe, demofringe, jazz, book, international, tattoo, art, hogmanay, science, imaginate, film, mela, storytelling)
- `code`: Venue number from Fringe list
- `year`: Festival year (e.g., 2015) or `*` for all years

**Search Filters:**
- `name`: Full text search on venue name
- `post_code`: Exact postcode match

**Geographic Search:**
- `lat`: Latitude coordinate
- `lon`: Longitude coordinate
- `distance`: Radius (format: Xmiles or Xkilometers)

**Change Tracking:**
- `modified_from`: Returns venues changed since specified Europe/London time

**Pagination:**
- `size`: Results per response (default 25, max 100)
- `from`: First result index

**Formatting:**
- `pretty`: Set to 1 for human-readable output

## Response Schema

Core fields (guaranteed for all venues):
- `id`: Unique venue identifier
- `name`: Venue name
- `festival`: Festival full name
- `festival_id`: Festival identifier
- `year`: Festival year
- `code`: Internal identifier
- `website`: Venue website
- `address`: Physical address
- `post_code`: Postal code
- `position`: Object containing `lat` and `lon`
- `phone`: Contact phone
- `email`: Contact email
- `description`: Venue description
- `access_description`: Accessibility information
- `performance_spaces`: Array of objects with `name`, `capacity`, `wheelchair_access`, `age_limited`, `age_limit`
- `event_count`: Number of unique events
- `performance_count`: Total performances
- `status`: in-use, not-in-use, or deleted
- `updated`: Last modification timestamp

# Edinburgh Festivals Events API Details

## Base URL
`https://api.edinburghfestivalcity.com/events`

## Endpoints
- `/events` - filterable list of events
- `/events/{UUID}` - specific event by unique identifier

## Authentication
The documentation does not specify an authentication scheme or how API credentials are passed.

## Request Parameters

**Festival & Genre Filters:**
- `festival` - ID values: fringe, demofringe, jazz, book, international, tattoo, art, hogmanay, science, imaginate, film, mela, storytelling
- `genre` - varies by festival/year
- `country` - artist/company origin
- `code` - festival-specific event code
- `year` - defaults to current year

**Text Search:**
- `title`, `description`, `artist` - match words/phrases

**Date Filters:**
- `date_from`, `date_to` - Europe/London timezone

**Price Filters:**
- `price_from`, `price_to` - minimum full price thresholds

**Accessibility:**
- `has_audio_description=1`, `has_captioning=1`, `has_signed=1`, `has_other_accessibility=1`

**Venue Search:**
- `venue_name`, `venue_code`, `post_code`

**Geographic:**
- `lat`, `lon`, `distance` (format: "Xmiles" or "Xkilometers")

**Synchronization:**
- `modified_from` - returns changed/deleted events

**Pagination:**
- `size` (default 25, max 100), `from` (index offset)

**Display:**
- `pretty=1` - human-readable format

## Response Schema

**Core Event Fields:**
- `id` (unique identifier, recommended over `url`)
- `title`, `sub_title`, `description`, `description_teaser`
- `artist`, `artist_type`, `performers_number`
- `festival`, `festival_id`, `genre`, `genre_tags`
- `code` (internal identifier)
- `country`, `age_category`, `non_english`
- `status` (empty/active/cancelled/deleted)
- `year`, `updated`, `url`, `website`

**Location & Venue:**
- `latitude`, `longitude`
- `venue` object containing:
  - `id`, `name`, `address`, `post_code`, `code`
  - `position` (lat/lon)
  - `phone`, `email`, `web_address`, `description`, `disabled_description`
- `performance_space` object:
  - `name`, `age_limit`, `age_limited`, `capacity`, `wheelchair_access`

**Performances Array:**
Each performance object includes:
- `id` (alphanumeric, unique across all events/time)
- `type`, `price_type`, `price`, `concession`, `price_string`
- `start`, `end` (datetimes)
- `duration_minutes`, `is_at_fixed_time` (boolean)
- `title`

**Accessibility:**
- `disabled` object containing:
  - `audio`, `audio_dates`
  - `captioning`, `captioning_dates`
  - `signed`, `signed_dates`
  - `other_services`, `other_services_dates`, `other_services_information`

**Media:**
- `images` object with hash-keyed image entries:
  - `hash`, `type` (thumb/hero), `orientation` (landscape/portrait/square)
  - `versions` with multiple resizes
  - `original` (height, width, mime, url)

**Additional:**
- `warnings`

The server returned HTTP 404 Not Found.

The response body was not retrieved. If this URL requires authentication, use an authenticated tool (e.g. `gh` for GitHub, or an MCP-provided fetch tool) instead of WebFetch.

# Edinburgh Festivals Listings API Authentication

Based on the provided documentation, **specific authentication details are not included** on this page.

The documentation states: "You will need to [register](/login) for an account in order to create an access key for your project" and mentions that "After you have [logged in](/login) to your account you will be able to create an access key from your profile."

However, the page does not specify:
- Whether the API key is passed as a query parameter, HTTP header, or other method
- How the key is used in requests
- Whether signatures or HMAC authentication is required
- The algorithm or parameter names for authentication

To learn the exact authentication mechanism, you would need to consult additional documentation pages like "[Authentication](/documentation/querying#authentication)" or "[Event search](/documentation/querying)" referenced in the navigation, which are not included in the provided content.

# Edinburgh Festivals Listings API Authentication

## Parameter Names
The API uses two parameters for authentication:
- `key` - your access key
- `signature` - the HMAC signature

## HMAC Signature Details

**Hash Algorithm:** SHA1

**What Gets Signed:** The full API request path and query string, including the access key but excluding the server domain. Per the documentation: *"Build the full API request URL, including your access key but excluding the server domain - eg `/events?festival=book&key=12345`"*

**Key:** Your secret token

**Important Note:** *"You should calculate the signature after URL-encoding any parameters"*

## Example Signed Request URL

```
https://api.edinburghfestivalcity.com/events?festival=jazz&key=12345678&signature=e471178c45d33d7a37f99f74f8ff59d97749e7bf
```

## Code Examples

**PHP:**
```php
$api_key    = '12345678';
$secret_key = '135fa25acs33';
$query      = '/events?filter=that&key='.$api_key;
$signature  = hash_hmac('sha1', $query, $secret_key);
$url        = 'https://api.edinburghfestivalcity.com'.$query.'&signature='.$signature;
```

**Python:**
```python
import hmac
import hashlib
api_key     = '12345678'
secret_key  = '135fa25acs33'
query       = '/events?filter=that&key=' + api_key
signature   = hmac.new(secret_key, query, hashlib.sha1).hexdigest()
url         = 'https://api.edinburghfestivalcity.com' + query + '&signature=' + signature
```