Parkour Design can connect with competition-management systems, platforms managing Events and Competitions, document workflows, and other tools used by organizers and course designers. An integration can securely transfer data and documents between systems without manually re-entering information or sending files outside the normal workflow.
Using established standards such as OAuth 2.0 and OpenID Connect makes implementation predictable and secure without requiring a partner to build the entire authorization mechanism from scratch. The final scope is adapted to the partner’s system and the approved user journey.
Benefits of an integration
A well-designed integration can provide:
- faster transfer of course designs and Competition data;
- less manual data entry and fewer avoidable errors;
- one consistent workflow for the user;
- secure access without sharing account passwords;
- compatibility with the partner’s existing tools and processes;
- user control over access to their data.
Parkour Design supports technology integrations in two directions. Parkour Design can connect to a partner’s identity provider and API, or a partner can connect to Parkour Design identity and data services. These directions are designed and approved separately, even when one product needs both.
This page describes the onboarding process. It is not self-service client registration or a complete API reference. Contact Parkour Design before building against a production service.
Continue with the implementation documents:
- Authentication for registration, authorization code, token validation, and refresh rotation;
- Data exchange for current resources, schemas, limits, and partner-specific exports;
- Testing and launch for executable checks, acceptance scenarios, and production approval.
Choose the integration direction
Parkour Design connects to the partner
Use this direction when a Parkour Design user needs to send a course design to a partner system or select a destination managed by that partner.
- The signed-in user starts the connection in Parkour Design.
- The Parkour Design backend creates a short-lived authorization transaction.
- The browser opens the partner’s authorization endpoint.
- The partner returns an authorization code to the registered Parkour Design callback.
- The Parkour Design backend exchanges and validates the code.
- Parkour Design stores the partner access token on the server, never in browser storage.
- Parkour Design calls the agreed partner API on behalf of that user.
The partner provides its OpenID Connect or OAuth metadata, client registration, identity claims, API contract, and test environment.
The partner connects to Parkour Design
Use this direction when a partner application needs the Parkour Design user to grant access to Parkour Design data.
- The partner redirects the user to the Parkour Design authorization endpoint.
- Parkour Design authenticates the user and asks for consent.
- Parkour Design returns a short-lived authorization code to the partner’s registered callback.
- The partner backend exchanges the code for tokens.
- The partner validates the returned identity and uses the access token only for the approved Parkour Design resources.
Parkour Design currently operates an authorization-code OIDC provider and a user-scoped resource service. Client registration and production access are coordinated with Parkour Design.
Engagement and environments
Start with a short technical discovery. Both teams should name one engineering owner and one operational contact.
Prepare a technical brief covering:
- integration direction and expected user outcome;
- test and production environments, including exact redirect URIs;
- authentication method, required identity claims, and approved permissions;
- exchanged data, requested resources, and the source of truth;
- expected volume, limits, and reliability requirements;
- technical, security, support, and launch owners.
Never send production secrets in tickets, chat messages, source files, screenshots, or public documentation. Agree on a secure credential channel and a rotation procedure before credentials are issued.
Start an integration
Send the technical brief to Parkour Design to begin the review.
Client registration, credentials, scopes, and production access are provided only after technical and security review.