CSSkill Public API

Our Public API gives developers access to structured Counter-Strike 2 match data, player statistics, and detailed match breakdowns.

Build dashboards, Discord bots, websites, and community tools using:

  • Player profiles and overall performance
  • Recent matches
  • Match-level statistical breakdowns
  • Event-based gameplay data

To get started you need an API key. Log in or create an account:

📚 API Documentation

Full endpoint reference, schemas, and examples:

View Swagger Documentation →

Usage & Attribution Guidelines

To ensure fair use and clarity for users, applications using the CSSkill API must follow the guidelines below.

Attribution & Branding

Applications displaying CSSkill data must clearly attribute the source.

Required attribution text:

  • “Data provided by CSSkill
  • “Powered by CSSkill

Attribution must be:

  • Clearly visible
  • Legible
  • Not misleading

You must not imply that your application is officially developed, sponsored, or endorsed by CSSkill.

Logos

  • Logos must not be modified, animated, or altered
  • Logos must not be more prominent than your own branding
  • Logos must not be used as your application icon
  • Logos must not suggest official affiliation
  • Logos must remain visually separate from your application branding

Linking Back

When displaying detailed player or match data, we strongly encourage linking back to the original source.

Recommended link text:

View on CSSkill

Links should be:

  • Clearly identifiable as links
  • Legible and accessible

Attribution links should point to: https://CSSkill.com

Use of Our Name

You may reference CSSkill in plain-text descriptions.

You must not:

  • Use our name in your application name
  • Suggest official endorsement or partnership
  • Display our name more prominently than your own

Approved phrasing:

  • “Powered by CSSkill.com”
  • “Data provided by CSSkill.com”

Metrics & Data Integrity

Metrics must be displayed exactly as returned by the API.

  • No rescaling (e.g. 0–100 → percentage)
  • No recalculation or modification
  • No added symbols, units, or labels

Example:

  • Aim: 92
  • 92%, 0.92, 9.2 / 10 ✖

Data Storage & Caching

  • Avoid permanently storing API data
  • Fetch data when needed
  • Short-term caching is acceptable

If data becomes unavailable, all stored copies must be deleted.

Rate Limits & Fair Use

Excessive usage, abuse, or attempts to bypass rate limits may result in API key suspension or revocation.

Changes & Availability

  • Modify the API
  • Update available endpoints
  • Change these guidelines

Whenever possible, changes will be communicated in advance.