⚽
API 3.0
⌘Ctrlk
OddsCoreFootball APIAPI 2 (Deprecated)WidgetsContact
⚽
API 3.0
    • πŸ›¬Welcome
    • πŸ™‹β€β™‚οΈGetting Started
    • ▢️Quick Start Guide
    • πŸ’―Most important docs pages
    • πŸ€“What can you do with Sportmonks' data?
    • πŸ†•Differences between API 2 and API 3
    • πŸ”Authentication
    • πŸ‘ΆMaking your first request
    • πŸ”§Best practices
  • ✨ Sportmonks AI Docs
  • API Quick Nav
  • API Coach
    • πŸ“„Changelog
    • πŸ“Changelog (BETA)
    • πŸ”€Syntax
    • πŸ’‘Request options
    • ♾️Rate limit
    • πŸ‘€Meta description
    • πŸ“”Error codes
    • πŸ“šCode libraries
    • Translations (beta)
    • Demo response files
    • Data corrections
    • API 2.0 (Deprecated)
    • Endpoints
    • Entities
    • πŸ†How-to build your World Cup application
    • Live matches, livescores & events
    • Hydration breaks
    • Tutorials
    • Guides
    • Programming languages
      • A developers guide: Unleashing the power of the football API with JSON
      • A developers guide: Unleashing the power of the football API with PHP
      • A developers guide: Unleashing the power of the football API with Python
    • Integrations
    • πŸ“”Response Codes
    • πŸ›°οΈStates
    • ⌨️Types
    • Definition of Common Football Terms
    • Endpoint vs Entity
    • API 3.0
    • Odds
    • Integration
    • Sportmonks
    • Postman
    • ID Finder
    • Sportmonks
    • MySportmonks
    • Football widgets
    • Plans and Pricing
    • Developer FAQ
  • API FAQ
Powered by GitBook
  1. Tutorials and Guides

Programming languages

A developers guide: Unleashing the power of the football API with JSONA developers guide: Unleashing the power of the football API with PHPA developers guide: Unleashing the power of the football API with Python
PreviousHow-to use TOTW - betaNextIntegrations

Was this helpful?

Was this helpful?