# Soccer API

> Soccer API (soccer-api.com) markets live football data — fixtures, live scores, match events,
> standings, teams, players, statistics, head-to-head, odds, predictions, historical data and a
> WebSocket stream. As of 2026-08-27 the product is ANNOUNCED BUT NOT SHIPPED: the site publishes
> no callable API, no machine-readable contract, no prices and no sign-up. Its own documentation,
> pricing and coverage pages each carry a notice stating that their contents are placeholders
> awaiting a production specification.

Generated by API Evangelist from the provider's public site. The provider does not publish an
llms.txt of its own — https://soccer-api.com/llms.txt returns HTTP 404.

## What an agent can and cannot do here

- There is NO callable endpoint. The base URL printed in the documentation is
  `https://api.example.com/v1` and the stream URL is `wss://stream.example.com/v1/soccer`; both are
  example.com placeholders. `api.soccer-api.com` and `stream.soccer-api.com` do not resolve in DNS.
- There is NO machine-readable contract. No OpenAPI, AsyncAPI, GraphQL SDL, JSON Schema, Postman
  collection, apis.json or llms.txt is published; every `/.well-known/*` path returns 404.
- There is NO price. Starter, Growth and Pro are all listed at "$XX / month".
- There is NO sign-up, console or key issuance. Access is requested by WhatsApp or email.
- Every endpoint path, field name, identifier and response body shown in the documentation is
  illustrative sample data ("Example Premier League", "match_74021", "North City"). Do NOT treat
  any of it as a description of a live API.

## Documentation (human-readable, placeholder content)

- [API Documentation](https://soccer-api.com/api-documentation/): Endpoint walkthrough for
  competitions, fixtures, live scores, events, standings, teams, players, line-ups, statistics,
  head-to-head, odds, predictions, historical data, WebSocket, pagination, rate limits and errors.
  Carries an "Implementation notice" stating the base URL, authentication method, endpoint paths,
  field names, request quotas, WebSocket protocol and response examples are placeholders.
- [API Coverage](https://soccer-api.com/api-coverage/): Data-category and coverage-level model.
  Names no real competition — the coverage matrix rows read "Competition A" through "Competition D"
  with every cell set to "Confirm". Carries a "Coverage notice" stating the labels are structural
  placeholders.
- [API Pricing](https://soccer-api.com/api-pricing/): Five tiers with placeholder prices and quotas.
  Carries a "Pricing notice" stating the prices and inclusions are implementation placeholders.

## Product pages

- [Live Soccer Scores API](https://soccer-api.com/live-soccer-scores-api/)
- [Soccer Statistics API](https://soccer-api.com/soccer-statistics-api/)
- [Soccer Odds API](https://soccer-api.com/soccer-odds-api/)
- [Soccer Head-to-Head API](https://soccer-api.com/soccer-head-to-head-api/)
- [Soccer WebSocket API](https://soccer-api.com/soccer-websocket-api/)

Note: the site's own navigation links a Soccer Predictions API page at
https://soccer-api.com/soccer-predictions-api/ which returns HTTP 404 and is absent from the
sitemap. It is omitted above rather than advertised.

## Editorial

- [API News](https://soccer-api.com/api-news/): Blog index. RSS at https://soccer-api.com/feed/
- [How to Choose the Right Soccer API for Your Project](https://soccer-api.com/soccer-api-tutorials/how-to-choose-right-soccer-api-for-your-project/)
- [Best Soccer APIs Compared (2026)](https://soccer-api.com/soccer-api-tutorials/best-soccer-apis-compared-2026/)
- [How to Build a Soccer Prediction Model Using Historical Match Data](https://soccer-api.com/soccer-api-tutorials/how-to-build-soccer-prediction-model-historical-data/)
- [How Soccer Odds APIs Work (With Real Examples)](https://soccer-api.com/soccer-api-tutorials/how-soccer-odds-apis-work/)
- [REST vs WebSocket APIs for Live Soccer Data](https://soccer-api.com/soccer-api-tutorials/rest-vs-websocket-apis-live-soccer-data/)
- [How to Build a Live Soccer Scores App Using a Soccer API](https://soccer-api.com/soccer-api-tutorials/how-to-build-live-soccer-scores-app-using-api/)

## Contact

- Email: info@soccer-api.com
- WhatsApp: https://wa.me/34675372893 (the destination of every "Get API Access" button)

## Optional

- [WordPress REST API](https://soccer-api.com/wp-json/): The only machine-readable JSON the domain
  serves. It is WordPress core content routing for the marketing site, not the soccer data product.
  Its own site metadata reads `"description":"Real-Time Cricket API"`, indicating the site was
  built from a template used for a different sport and the tagline was never changed.