Troyen Website — User Guide

Document set version: 0.2.0

Date: 2026-09-05

Status: This guide describes the verified current public experience. It will be revised as the Python replacement website is implemented.

Homepage

The homepage introduces Troyen Data and explains how its structured racing data can support applications, analytics pipelines, and operational systems.

Visitors can review:

• International coverage.
• RESTful API architecture.
• JSON delivery format.
• Developer documentation approach.
• Scalable infrastructure and access controls.
• Subscription and pricing principles.

Requesting API Access

Use a Get API Keys button to open the enquiry form. The current form requests:

• Email address.
• Company name.
• Company URL.
• A comment describing the intended use.

After a successful request, the site displays a confirmation that the Troyen Data team will follow up.

API credentials are issued after a subscription is confirmed. Credentials are client-specific and must be kept confidential.

FAQ and Support

The FAQ provides guidance on:

• API credentials and access enquiries.
• Request limits.
• Regional and discipline coverage.
• Data refresh timing.
• Subscription changes and cancellations.
• Monthly billing.

The current basic API limit is stated as 2 calls per second. Higher-throughput integrations may require a different access arrangement or ingestion into the customer's own database.

API Documentation

The API Documentation page explains the race-card response and related meeting and race-list data. It provides:

• A race-card endpoint pattern using a race identifier.
• A meeting-card endpoint pattern using a meeting identifier.
• Root, distance, runner, carrying-weight, performance-statistics, form-line, and race-result field guidance.
• A sample JSON payload.
• Notes on using meeting race lists for navigation while retrieving full racecards from the dedicated endpoint.

The published endpoint hosts shown in examples are placeholders and must not be treated as production connection details.

Integration Notes

The Integration Notes page describes expectations for clients consuming Troyen Data JSON. Topics include:

• Contract scope and JSON hierarchy.
• Additive schema evolution and forward-compatible parsing.
• Multiple representations and discipline-neutral structures.
• Performance statistics.
• Nullable fields and time values.
• Parsing requirements and stability policy.

Clients should ignore unknown fields, handle nullable values safely, and avoid relying on undocumented property order.

Data Timing

The current FAQ describes several update patterns:

• Core datasets such as racecards follow confirmed final acceptances.
• Comments and derived content are produced before the event.
• Scratchings are updated as received.
• Forward datasets refresh on a schedule that increases closer to the event.

Odds, where supplied, are indicative morning or pre-post values and are not real-time prices.

Pricing and Subscriptions

Pricing is handled by enquiry and depends on coverage, data scope, delivery pattern, access volume, and bespoke requirements.

Subscription changes are handled through Troyen Data support. The current FAQ states that processing may take 24–48 hours, downgrades apply from the next billing period, and cancellations remain active until the current billing period ends.

Current Limitation

The replacement website currently has a Python foundation and a verified reference capture only. No public replacement site is available yet, so continue using the current Troyen Data website until a new release is implemented, verified, and formally deployed.