In short
- SwimNexus does not currently offer a general public developer API or a marketplace of third-party integrations.
- What exists today is: (1) club-issued MCP access credentials for SwimClubOS, (2) organisation-issued MCP credentials for SwimMeetOS, and (3) a read-only public data feed for a club's published website content. Club-owned provider connections (for example GoCardless) are separate arrangements.
- These terms are published for information. They apply to a customer only where its agreement or an accepted amendment incorporates them. They do not change a signed agreement by themselves.
1. What is covered
| Interface | What it is | Who controls access |
|---|---|---|
| SwimClubOS MCP credentials | A bearer credential created by a club administrator for one club and one endpoint. Read-oriented capabilities plus controlled draft changes to website content. | The club administrator who creates it, limited by their own permissions. |
| SwimMeetOS MCP credentials | A bearer credential bound to one organisation. Read-only meet summaries, programme and publication status, plus a proposal tool that a signed-in person must approve. | An organisation owner/administrator or platform administrator with meet view permission. |
| Public club website data | Read-only data for information a club has explicitly published, which fails closed if not published. | The club, through publication settings. |
Internal and administrative interfaces, the first-party mobile app interface, and platform administration are not customer-facing services and are not offered under these terms.
2. Authorised use
Use credentials only for the club or organisation they were issued to, for its own swimming administration, with software you trust. Do not use them to build a competing service, to resell access, or to bulk-collect personal data.
3. Authentication and credentials
- A credential is shown once, stored by SwimNexus only as a hash, tied to one endpoint, and must have an expiry. Treat it like a password.
- Do not share it, commit it to source control, or place it in a public tool. If it may have been exposed, revoke it immediately; revocation takes effect at once.
- A credential stops working if its creator is removed, loses the relevant permission, or the organisation's access ends.
4. Permission scopes
Each credential carries selected scopes. A request needs both the scope and the creator's current permission, and never gains more than either allows. A credential cannot select another club or organisation.
5. Your responsibilities
You are responsible for what is done with your credentials and for any personal data you retrieve. You remain the controller of that data. Do not send children's, medical or safeguarding information to a third-party tool you have not assessed, and do not use credentials to send personal data to artificial-intelligence services unless your club has decided that is appropriate.
6. Rate limits
Credential requests are limited to 60 requests per 60 seconds per credential, with size and page limits. Requests beyond the limit are refused until the window passes. These limits protect all customers and may change.
7. Prohibited activity
Do not attempt to reach another customer's data, bypass limits or permissions, probe or load-test the service, use automation to harvest member or competitor data, or use an interface in a way that could harm the service or others.
8. Data protection and security
Use of an interface is processing under the Data Processing Agreement and your instructions. Every request is attributed to a credential and recorded without the contents of the request. SwimNexus can disable a credential that is behaving unsafely.
9. Changes, suspension, revocation and termination
Interfaces are provided as they stand and may be changed, narrowed or withdrawn. SwimNexus gives reasonable notice of a change that would break existing use, unless security requires immediate action. SwimNexus may suspend or revoke a credential for misuse or risk. Credentials stop when the agreement ends. No uptime or compatibility guarantee is given.
10. Questions
Email [email protected]. If a future agreement offers a wider API, it will have its own terms and this page will be updated.
SwimNexus is the trading name of Lewis Plume, a UK sole trader, 20 Talbot Close, Highbridge, Somerset, TA9 3AX, United Kingdom. Contact [email protected]. Customers' signed agreements prevail over this page.