What is included and for whom
Widgets are included with Professional and Enterprise, including eligible confirmed trials, for one registered HTTPS website. There is no separate widget subscription or widget fee. Signed-in customers can design, save and preview widgets without buying an eligible plan first; Developer does not include publishing. Downloads, key creation and live display need an active eligible main plan and a registered website. Subdomains count as separate websites.
Widget traffic has unlimited monthly requests with its own per-second limits and does not consume your REST allowance. That separation goes both ways: a widget key is not a REST key. It cannot call /v1 endpoints or MCP, and a REST key cannot power a widget.
From saved design to live widget
- 1Design and save. Dashboard Widgets: choose content, colours and bookmaker links; save the design.
- 2Register website. Add your public HTTPS site and generate its website-bound widget key. Copy it once.
- 3Install plugin. Download the ZIP, upload through Plugins, Add New, Upload Plugin, then activate.
- 4Verify website. Settings, RacingAPI Widgets: paste the key manually, choose Verify website and connect.
- Save the design in your account. Its ID is public; it grants nothing by itself.
- Register the website and generate the widget key. It is shown once; store it in a password manager.
- Install and activate the plugin ZIP downloaded for that design.
- Enter the key in WordPress Settings, RacingAPI Widgets. A callback proves that the plugin on the registered site holds it.
- Open the plugin's Shortcodes screen, pick the design, content, course and day, and copy the shortcode into a Shortcode block.
Shortcodes
[racingapi_widget id="YOUR-WIDGET-ID"]
[racingapi_racecards id="YOUR-WIDGET-ID" course="Ascot"]
[racingapi_results id="YOUR-WIDGET-ID" date="yesterday"]
[racingapi_tips id="YOUR-WIDGET-ID"]
[racingapi_lucky15 id="YOUR-WIDGET-ID"]
[racingapi_nap id="YOUR-WIDGET-ID"]
[racingapi_treble id="YOUR-WIDGET-ID"]
[racingapi_double id="YOUR-WIDGET-ID"]| Attribute | Accepts |
|---|---|
| id | Your saved design ID. |
| course | A course name or ID. Omit to keep the saved filter, or all courses. |
| date | today, tomorrow, yesterday or YYYY-MM-DD, from five days ago to tomorrow, on the London calendar. Tips are for the current day. |
[racingapi_widget] uses the design's saved content setting. Racecards, results and tips shortcodes open those views directly; racingapi_tips selects the predictions view. Lucky 15, NAP, treble and double each select their named daily tips card. Lucky 15 needs four qualifying legs, treble three and double two, from separate races; a NAP is one selection. These cards require positive model EV and may be unavailable when too few selections qualify. They are widget features, not extra REST endpoints.
Use the plugin's generator rather than typing IDs. The course filter applies to racecards, results and regular predictions. It is deliberately ignored for the four daily-card shortcodes so a course filter cannot cut legs out of a saved card. Those daily cards are for today; changing date does not create future tips. Edit and save the same design to restyle live widgets without reinstalling.
How it renders: HTML with Shadow DOM
The plugin renders racing HTML on your WordPress server into a div with declarative Shadow DOM. It is not an iframe on your published page, so racing content is in the initial HTML; this does not guarantee search-engine indexing or rankings. Shadow DOM isolates internal styling from ordinary theme selectors, but the host page still controls available width and can hide or remove the widget. Refreshes, race details and silks are proxied through WordPress, so browsers never see a key. Visible widgets normally refresh every 30 seconds; keep full-page caches short so old dates do not linger.
The complete guide is Widgets and WordPress; product overview at Widgets.
Reference material
Exact schemas: API reference. First call: Quickstart. Copy-ready helpers: Code examples. Plans: Pricing.