The USA Swimming API Program allows secure integration with the SWIMS platform through a tiered system supporting everything from basic team management to real-time member verification. Built on strict security, legal compliance, and technical validation, the program ensures every integration meets USA Swimming’s standards for data protection and accuracy.
Access is organized into three tiers, each aligning needs and capabilities with appropriate data permissions, testing, and compliance oversight. This progressive model enables vendors to scale responsibly, advancing only after proving technical competency and operational readiness. Each tier adds privileges to the previous level, ranging from read-only functionality to advanced, fee-based services for real-time verification.
Follow these steps to request access, complete onboarding, and begin validating USA Swimming API endpoints.
Submit an API access request and identify the requested access tier, use case, technical contact, and endpoints needed for your integration.
Work with USA Swimming to complete credential setup, API role assignments, onboarding validation, and required documentation.
Use the Stage environment and Postman collections to validate authentication, request payloads, and endpoint responses before production use.
The USA Swimming API uses OAuth client credentials flow for authentication. Vendors must obtain an access token from the USA Swimming identity platform and include the token in the Authorization header for all protected API requests.
To obtain an access token, submit a POST request using your assigned username and password credentials.
| Environment | Token Endpoint |
|---|---|
| Stage | POST https://stg-security-api.swimsmember.org/security/Identity/GetAccesTokenForUser |
| Production | POST https://security-api.usaswimming.org/security/Identity/GetAccesTokenForUser |
{
"username": "test",
"password": "1234"
}{
"access_token": "eyJhbGciOiJSUzI1..."
}Access tokens expire after approximately 24 hours. Applications should request a new token shortly before the current token expires to avoid authentication interruptions.
Use the appropriate API environment for testing or production integrations.
| Environment | Base URL |
|---|---|
| Stage | https://stg-usaswimming-api.swimsmember.org |
| Production | https://usaswimming-api.usaswimming.org |
Note: The Stage environment is intended for testing and validation purposes only and may not reflect live production data.
API access is organized into multiple tiers based on integration complexity, operational readiness, compliance requirements, and access to protected member data.
Provides access to GET endpoints (read-only) including club rosters, membership lookups, and approved USA Swimming reference data.
Provides access to POST endpoints and write-enabled operations requiring additional onboarding validation and compliance review.
Provides access to Member Verification APIs and Times Verification APIs for real-time eligibility validation and performance checks.
Read-only and foundational access for core team management: clubs, rosters, and vendor event logs.
Write-enabled and higher-value team management operations, including offerings, bulk registrations, registration status, event logs, and Webhooks.
Webhooks provide real-time notifications from SWIMS to registered webhook endpoints when membership or club data changes occur.
Verification-focused endpoints for membership eligibility, compliance checks, and time standard validation.
Restricted endpoints supporting NCAA-specific integrations for teams and rosters for approved vendors.
Use Postman to validate authentication, request payloads, and API responses before integrating USA Swimming endpoints into production systems.
Download the appropriate Postman collection to test authentication, endpoint access, and request payloads for your assigned API tier.
| Tier | API Collections & Testing Resources |
|---|---|
| Team Management – Base Access | Download Team Management Base Access Collection (.json) |
| Team Management – Premium Access | Download Team Management Premium Access Collection (.json) |
| Times and Member Verification Access | Download Times and Member Verification Collection (.json) |
| NCAA Access | Download NCAA Access Collection (.json) |
Note: Access to API collections and endpoints is controlled by assigned API roles and approved access tiers.
Reference definitions for common SWIMS data fields and event terminology used throughout this API documentation.
| Term | Definition |
|---|---|
| competitionCategory | Stated as male or female for the purpose of athlete swimming eligibility, competition, selection and records. |
| contactRelationship | Denotes the relationship between the member and their primary contact. |
| emailAddress | Denotes a valid email address. |
| isUsCitizen | Indicates whether the member is a United States citizen. |
| memberId | A unique 14-character alphanumeric identifier assigned to a USA Swimming member. |
| oldUsasId | Legacy USA Swimming member identifier based on name and birthdate conventions. |
| clubId | Unique alphanumeric identifier assigned to a club. |
| clubCode | Short code representing the club. |
| clubName | Official name of the swim club. |
| vendorId | Unique identifier assigned to an approved API vendor. |
| vendorRecordId | Optional vendor-supplied identifier used for reconciliation and tracking. |
| registrationDate | Date the member registration became active. |
| expirationDate | Date the member registration expires. |
| registrationType | Human-readable descriptor of the membership type. |
| registrationTypeId | Internal identifier representing the membership type. |
| transactionType | Type of membership transaction such as New, Renew, Upgrade, or Cancel. |
| lscCode | Alphabetic code representing a Local Swimming Committee (LSC). |
| isAttached | Indicates whether the member is attached to a club. |
| memberGoodStandingExpirationDate | Date through which the member remains in good standing. |
| Term | Definition |
|---|---|
| eventSequence | Sequential identifier used to track event ordering for a vendor. |
| eventTypeId | Internal identifier representing the type of event generated. |
| eventType | Human-readable name describing the event. |
| eventData | JSON object containing event-specific payload data. |
| Member Registration Complete | Event generated when a member successfully completes registration. |
| Member Updated | Event generated when member demographic or registration information changes. |
| Member Merge | Event generated when duplicate member records are merged in SWIMS. |
| Member Transfer | Event generated when a member transfers from one club to another. |
| Club Activates Vendor | Event generated when a club enables an approved vendor integration. |
| Club Details Updated | Event generated when a club updates identifying or metadata information. |
API access is structured into three defined tiers that align each vendor’s technical capability with appropriate levels of data access, testing, and compliance oversight. This tiered model ensures that integrations scale responsibly, allowing vendors to progress only after demonstrating technical competency, adherence to data protection standards, and operational readiness.
Each tier grants a distinct set of permissions and responsibilities, from basic read-only functionality to advanced, fee-based services enabling real-time member verification and results submission. Each higher tier includes the privileges of the preceding level, ensuring a controlled and progressive path toward deeper system integration.
The USA Swimming API Access Program provides access to organizations and individuals who serve our members, clubs, coaches, and athletes. API access is granted through an application and onboarding process.
Ready to Apply?
Need Help?
For questions about onboarding, access tiers, or specific endpoints, contact Mitch Gold at mgold@usaswimming.org or submit a ticket through the USA Swimming Third-Party Vendor API portal.
Important: USA Swimming reserves the right to approve or deny access based on alignment with our mission, compliance with data governance standards, and technical security.