> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/api/code-libraries.md).

# Code libraries

### Community libraries

To help developers integrate the Sportmonks Football API more efficiently, the community has contributed various SDKs and packages across different programming languages. Below is a collection of available resources:

#### Laravel

* **sportmonks-fpicosm** ([GitHub Repository](https://github.com/fpicosm/sportmonks))\
  A Laravel package for interacting with the Sportmonks Football API, making it easier to fetch and process football data.

### Contribute your own library

We encourage developers to build and share their own libraries, SDKs, and integrations for the Sportmonks Football API. If you've created a package in any programming language, feel free to submit it for inclusion in this list.

To contribute:

1. Publish your package on GitHub or a relevant package registry (e.g., PyPI, npm, Maven).
2. Share the repository link with us by [contacting our support team](https://www.sportmonks.com/contact-support/).
3. Ensure that your library is well-documented and adheres to best practices for API integration.

By contributing, you help expand the ecosystem and make it easier for other developers to integrate football data into their projects!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportmonks.com/v3/api/code-libraries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.