API access in LIGR Live allows your Organisation to connect external systems and services to your LIGR data through secure authentication keys managed from your profile.
What API Access Is Used For
API access is typically used by Organisations that want to integrate LIGR Live with their own platforms, websites, or data systems. Common use cases include:
• Pulling match data, fixtures, or results into an external website
• Syncing Competition, Club, Team, or Player information with another system
• Feeding live Match Facts into custom dashboards or apps
• Automating asset creation or updates from an external source
Because API access exposes Organisation data, it should only be managed by users with the appropriate permission level.
Who Can Manage API Access
API access is an Organisation-level setting. Only the following roles can view or manage API credentials:
• Owner — full access to API settings
• Admin — can manage API access depending on Organisation configuration
Standard Users, Gameday Operators, Live Scorers, and Media Viewers do not have access to API settings.
[ Image placeholder: Profile menu showing the Permissions and API section highlighted ]
Accessing the API Settings
To find your API settings:
1. Log in to LIGR Live as an Owner or Admin.
2. Click your profile icon in the top-right corner.
3. Select Profile from the dropdown.
4. Navigate to the Permissions and API section.
From here you can view existing API credentials tied to your Organisation and manage their status.
[ Image placeholder: Permissions and API page within the Profile area ]
Generating and Managing API Credentials
Requesting API Access
API access for your Organisation is typically enabled by the LIGR team. If you do not see API credentials in your Profile:
1. Contact LIGR support to request API access for your Organisation.
2. Confirm the use case and which data you intend to access.
3. Once enabled, your API credentials will appear under Permissions and API.
Viewing Your API Key
Once API access is active, you will see:
• Your unique API key or token
• The Organisation the key is associated with
• Any relevant scope or permission information
Rotating or Revoking a Key
If a key is ever exposed or no longer needed:
1. Open the Permissions and API section of your Profile.
2. Locate the key you want to replace or remove.
3. Use the option to rotate (regenerate) or revoke the key.
4. Update any external systems with the new key immediately to avoid service interruption.
[ Image placeholder: API key row with rotate and revoke options ]
Tips
• Treat your API key like a password — never share it publicly or commit it to code repositories.
• Rotate keys periodically as part of good security practice.
• Keep a record of which external systems use the key so you can update them quickly after a rotation.
• Only grant API access to team members who genuinely need it for integration work.
Common Issues
• I can't see the Permissions and API section — Your role may not have access. Only Owners and Admins can view this area.
• My API key isn't working — Confirm the key has not been rotated or revoked, and that you are using the correct Organisation's credentials.
• I need API access but it isn't enabled — Contact LIGR support to enable API access for your Organisation.
• External system stopped syncing after a key change — Update the external integration with the new key; old keys stop working immediately after rotation or revocation.