Your app. Your players. More opponents.
Everything an independent darts app developer needs to understand how joining DartXchange will work, in plain language. Your app, your branding, your accounts and your scoring engine stay yours.
Status labels used below: Built, local testing only In development Planned Not open yet
- 1. What DartXchange does
- 2. Register an app
- 3. App references and credentials
- 4. Player identity
- 5. Scoring compatibility
- 6. Lobbies
- 7. Join requests
- 8. Match communication
- 9. Testing and approval
- 10. Going live
- How to join
1. What DartXchange does
DartXchange is a shared online network for darts apps. It is not a scoring app and it does not replace yours. It connects the apps that join so their players can find each other and play together.
Your app keeps
- Its brand and interface
- Its players and logins
- Its scoring engine and cameras
- Control over your users
DartXchange provides In development
- A permanent shared identity for each player
- A shared lobby and join requests
- Compatible scoring rules
- Later: match communication, friends, shared video
2. Register an application Not open yet
Registering tells DartXchange your app exists. The process:
- Create a developer account (name, email and password), verify your email, and wait for DartXchange to approve the account.
- Register your application: name, short description, website and an optional logo. DartXchange reviews it; registration alone does not make you a featured partner.
- On approval your application gets a permanent app reference, and you create your credentials in your dashboard. The secret is shown once.
The account and application system is built and being tested, but public registration is not open yet. Already registered? Sign in.
3. App references and developer credentials
Built, local testing only- App reference: a short code (2–4 letters or digits, such as
AB) assigned by DartXchange. It is unique, never changes and can never be chosen or typed by a player. It is shown next to your players’ names. - Credentials: a key ID and a secret for your app. Your server uses them to sign its requests to DartXchange. They must never be placed in a web page or in a mobile app.
- Keys can be replaced and withdrawn: an app can hold more than one key at a time so a key can be rotated without downtime, and a key can be revoked at once.
- Environments: test and live credentials are separate and do not work in each other’s place.
Credentials are not available to the public yet.
4. Player identity and authentication
Built, local testing onlyYou authenticate your own players. They log in to your app exactly as they do now. Your server then tells DartXchange which of your players is online. DartXchange never sees your players’ passwords and players do not create a separate DartXchange account.
- DartXchange creates a permanent player ID for each of your players. All shared features use that ID, never the username.
- Players are shown as
username-REF, for example180King-AB. Your players’ username casing is preserved. - Usernames must be unique within your app (ignoring upper/lower case). The same username can exist in different apps.
- Each sign-in produces a short-lived session (10 minutes). Your server refreshes it about every 8 minutes, re-checking that the player is still allowed to play.
Example flow (illustrative)
Player logs in to YOUR app (as today)
|
Your server confirms who they are
| signed request: "player 1234, username 180King, automatic scoring"
v
DartXchange --> permanent player ID, display name "180King-AB",
short-lived player session token
|
Your app uses that token to show the shared lobby
This is how the integration works. Exact details are in the API reference and may change before launch.
5. Automatic and manual scoring compatibility
In development- Automatic scoring: your app itself detects and calculates the score (for example from a camera), even if the player can correct mistakes.
- Manual scoring: the player enters the score.
- When a lobby is created, the host chooses what they accept: automatic only, manual only or either. A player can join only if their method fits. DartXchange checks this on its server for both the host and the player who joins.
- Your app tells DartXchange which method a player is using. DartXchange cannot verify that; it relies on your app being honest, and the method is recorded.
6. Lobby creation and discovery
In development- A player creates a lobby: game (for example 501), best-of or first-to legs, and the accepted scoring methods. Apps can attach optional extra settings (for example bull-up) that other apps may ignore.
- Your app lists lobbies from all participating apps inside your own interface, with filters.
- One active lobby per host. A lobby ends when the game finishes, is cancelled or times out, and then the host can host again.
The data model is built and tested locally. There are no public lobby endpoints yet, and none are documented here. The lobby demo is a picture, not a working lobby.
7. Join requests and acceptance
In development- A player creates a lobby.
- Another player, from any participating app, asks to join.
- The host accepts or rejects.
- If accepted, both players receive the details they need to start the match.
This mirrors how many apps already work, so it fits alongside your existing lobby. DartXchange is an additional online option; it does not replace yours.
8. Match communication
Planned- First: hand both players a shared room so they can find each other.
- Later: a shared way to report visits, busts, checkouts, legs and results, so apps with different scoring engines can play one match. Disconnect and reconnect handling is part of this.
- Later still: shared video of each player’s board, with each app supplying its own camera feed, and spectators.
Nothing here exists yet and no protocol is published.
9. Testing and integration approval
Planned- You integrate against a test environment with test credentials, using fake players.
- Simple checks confirm your app signs requests correctly, handles errors and refreshes sessions on time.
- When the checks pass you become an Integrated Partner (see the Partner Programme).
10. Going live
Planned- Live credentials are issued after approval, and separately from test credentials.
- You switch your app over when you are ready. Joining is your choice, and you can stop at any time.
- Being listed on this website is optional and needs separate approval.
How to join
Right now: read this page and the API reference and integration guide. Registration opens when the hosted test environment has been proven; until then the sign-up page says so honestly. The contact form is still a preview and sends nothing.
