Your platform
The course plan arrives in the right Event, Competition and arena, without extra emails or manual uploads by the show office.
For equestrian platforms and technology partners
Bring the approved course plan into your show workflow
Building a show-management, timing or results platform? Let’s explore a connection with Parkour Design so users can deliver course plans to the right Events and Competitions in your system.
Each integration is scoped, tested and agreed together with your team.
What each side gains
Show office and timing
You know who approved the plan and which version riders should see, including after a late correction.
Course designer
Decides what becomes public: riders get the approved plan, while the masterplan and working versions stay private.
Riders and spectators see the approved plan next to start lists and results.
Start with one publication flow
A proposed first proof of concept: the course designer sends the current plan to one Competition in your system.
- 01
Prepare
The course designer prepares a design in Parkour Design.
- 02
Choose a destination
Select the Event and Competition in the partner system.
- 03
Confirm the upload
The course designer confirms sending the current design.
- 04
See the result
The course designer sees that the plan was published, or an error that can be fixed and retried.
Available today, and what we agree together
Available today
- Uploading a design to a connected partner platform: Event and Competition selection, PDF and course parameters, and the upload result.
- OAuth / OIDC authorization for approved confidential backend clients.
- Read-only Event and design summaries owned by the authenticated user.
- A documented test environment, onboarding and launch-review process.
Agreed with each partner
- Connecting the upload to your API: listing your Events and Competitions and receiving the PDF and parameters.
- From your platform to Parkour Design: starting a design with Event and Competition context.
- Reading complete project geometry and obstacle data through the API.
- Delegated roles, version replacement and synchronization.
Uploading to a partner platform already works in the application; for your platform we connect it to your API within the scope we agree. Data can also flow the other way: your platform can start a design in Parkour Design with the Event and Competition already filled in. Design summaries from the read API are not printable course plans. Client registration, permissions and production access are reviewed with each partner.
How we work together
- 01
Define the use case
One user problem, clear roles and a specific outcome.
- 02
Agree the contract
Data, files, permissions, versions, responsibilities and commercial terms.
- 03
Test a PoC
Test accounts, a sample Competition, errors, retries and republishing.
- 04
Approve launch
Security review, monitoring, support and an integration-disable procedure.
Commercial model
Users can work with their own Parkour Design subscriptions, or we agree partner access. Together we also decide who maintains the integration and who supports shared customers.
Tell us about your platform
Send a short description and we will reply to arrange a call. It helps if you include:
- Company name and platform URL.
- Contact person, role and work email.
- Disciplines, market and the proposed user workflow.
- A link to public API documentation, if available.
Please do not send API keys, tokens, customer data or production files in the first message.
support@parkour.design · Read: Integration onboarding →
Your questions, answered
Which platforms is this for?
Show-management systems, timing and results services, federation platforms and rider portals with a show jumping workflow. We start with one specific user need and one agreed flow.
Do users need a Parkour Design account?
Yes. Users sign in to Parkour Design and approve access through the documented OAuth 2.0 / OpenID Connect flow. Accounts are linked by identity, not email alone. Linking accounts does not grant a subscription; access and licensing are agreed separately.
Can we start with PDF publication only?
Yes. Each upload contains the PDF and the course parameters, and your platform can start by using only the PDF. We agree how your system receives the file and how a successful upload is confirmed.
Can a show office publish on behalf of the course designer?
Only with roles and delegated permissions agreed in both systems. The current API returns only the authenticated owner’s Events and design summaries, and a matching email address is not authorization to act for someone else.
Does the integration include 3D videos or obstacle statistics?
Not in the first proof of concept. A route video beside Competition information or obstacle-level statistics are possible follow-on projects, each with its own agreement, once the plan handoff works reliably.
How are scope, costs and launch dates agreed?
We start with a short product and technical call, then agree one user journey, the data contract, a test environment, responsibilities and the commercial model before implementation. Costs and dates follow from the agreed scope.
How do we test the integration before launch?
We coordinate test access, credentials and permissions after technical and security review; registration is not self-service. In the agreed test environment, both teams verify sign-in, access only to the right user’s data, the agreed data exchange and failure handling. Test and production credentials stay separate, and launch requires approval from both teams. The documentation lists the checks and acceptance scenarios.
Where can we ask technical questions or report a problem?
Email support@parkour.design with the integration direction, test or production environment, the affected operation, steps to reproduce, and the expected and actual result. Include a sanitized error message or HTTP status if available. Do not send passwords, authorization codes, tokens, client secrets, personal data or customer files. Credential exchange and incident contacts are agreed separately during onboarding.